Database Info

8.1 developer system image

Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?

Horgar said:
Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Click to expand...
Click to collapse
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.

mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?

Horgar said:
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Click to expand...
Click to collapse
I'm not bothered with twrp recovery so did not flash the zip, but like I said I booted into twrp.img, flashed supersu and suhide and that's it. All working for me including SafetyNet. I used USB OTG for this process.

I did the same as the poster above.

just curious;
but how is Android 8.1? ?
I've found 8.0 to not be as good on battery life as 7.x.x, although I think I have mostly worked that out on my custom kernel...
any other notable goodies?
(ps: I don't care for the pixel launcher or the ambient services stuff..)

mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
I flashed factory image and I have error.

Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
Move the entire folder to a drive other than C drive. I think that might fix it.

NoobInToto said:
Move the entire folder to a drive other than C drive. I think that might fix it.
Click to expand...
Click to collapse
I did. But the error exit

Myo Thu Htet said:
I did. But the error exit
Click to expand...
Click to collapse
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.

NoobInToto said:
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
Click to expand...
Click to collapse
I did all u did ?
Yes I checked G+
Only few can install.

Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5

mannunikhil said:
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
Click to expand...
Click to collapse
Nope. It looks like Google's fault this time.

NoobInToto said:
Nope. It looks like Google's fault this time.
Click to expand...
Click to collapse
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.

mannunikhil said:
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
Click to expand...
Click to collapse
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...

NoobInToto said:
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
Click to expand...
Click to collapse
Mine was the fair test just to check if OTA zips are corrupt or not. I provided suggestions for factory image not for OTA, no point in extracting the OTA anyway. And if you had gone through all the threads you would see I mentioned I had similar issue sideload'ing OTA over 8.0.0, so that means we are sailing in same boat. OTAs had compatibility issue with 8.0.0, glad google listened and taken them off.
I still have little lag in app drawer hoping that would be fixed too in republished OTA.

Just signed up for Android beta program and got the 8.1 update for my project fi carrier unlocked Google pixel XL. The update seems to be running smoothly and everything is working so far on my device... I didn't have any issues with installation it installed just fine... Can't wait for Nov security patch supposed to be a good network feature in there in Dev settings.

I am not sure if this may help anyone trying to look at why the issues are present when trying to install:
Android 8.1 beta OTA upgrade on OG Pixel
I, just like many of you, have been experiencing OTA "installation problem" when trying to upgrade to the 8.1 beta. After reviewing comments and what worked for who, I decided to give this a shot and it worked. I am not sure if this will work for other devices (nexus or XLs) and keep in mind that you WILL lose all your data stored on the device, so back up prior to this method.
1. Be sure you are enrolled in the beta program.
2. Wait for the OTA to notify you that it's available.
3. Select "Download and Install".
4. After it has done its duty, DO NOT select "Restart and Install"
5. Go to "Factory Reset" and pull the trigger.
6. Your phone will factory reset, stating it's wiping everything, then it will install the update successfully.
NOTE: this is what worked for me. I'm unsure if it will solve all the "Installation problem" reports which have been made.
It's weird cause when I tried to factory reset, then download and install, it didn't work. Yet, downloading but NOT installing, then factory resetting worked.
After doing this I posted it here: https://plus.google.com/+ChristopherLeeMurray/posts/KDCZXbfAxLJ

You don’t need to sign up to the beta program. Just go to the Google website and download the latest 8.1 factory image. That's what I did and had no problem with flashing it. You can also delete the - w and keep your data. It's getting past the TWRP password to decrypt that I cant do. So can't flash root or recovery. Anyone managed this?

I'd prefer to be in the beta program since I'm a Android apps beta tester. I beta test everything and when it was installing it said on the screen that it's a beta version of the original software version of 8.1 which is what I believe is on Googles page and mine may have errors and defects.. the beta program gets different software than what Google usually posts. Different features and such which isn't in the official version which makes it a beta version.

How to get 8.1 when already rooted?

So i just got a Pixel 2 and got it rooted last night and moved all my stuff over before realizing i can get 8.1. I tried to get the latest stock from google but when i tried to run the .bat file (after removing the -w to prevent wiping) it started then failed saying something about needing something with a 59 in the file and the one i was using had 69.
Is there another way to do it? like unrooting, taking the OTA then rerooting? right now it says "couldnt update, installation problem". Is this from usign magisk? i know in the past id have to freeze the ota with TiBu.
mainly just looking for a way to get 8.1 without loosing all my stuff and having to copy it all back again.

Are you trying to skip some of the monthly updates?
Some believe the updates to be incremental, others do not. Update to the next month's update from the one you're on, until you're to the current June update.
Sent from my Pixel 2 using Tapatalk

Diesel_Jeremiah said:
Are you trying to skip some of the monthly updates?
Some believe the updates to be incremental, others do not. Update to the next month's update from the one you're on, until you're to the current June update.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
oh ****, theres no better way? thats over 10gb of files

So I just went through this. I bought my pixel 2 and updated from the September to November builds via flash. Then I got lazy and got a little behind on my updates.
There was something about the transition to 8.1 (December) that got a little wonky with regard to successfully flashing the bootloader.
What I did was I downloaded the December OTA update 8.1.0 (OPM1.171019.011, Dec 2017) and flashed that directly through "Apply Update through ADB"
Once that OTA has been flashed factory images such as the most recent one you were trying to flash should work. I successfully went directly from December to May. Just remember to remove the "-w" flag from the .bat file to avoid the wipe.
You won't lose all your stuff but you will need to re-root by flashing and installing Magisk.
The instructions from this thread are good:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Hope this helps.
Best,

JasonVaritekMVP said:
So I just went through this. I bought my pixel 2 and updated from the September to November builds via flash. Then I got lazy and got a little behind on my updates.
There was something about the transition to 8.1 (December) that got a little wonky with regard to successfully flashing the bootloader.
What I did was I downloaded the December OTA update 8.1.0 (OPM1.171019.011, Dec 2017) and flashed that directly through "Apply Update through ADB"
Once that OTA has been flashed factory images such as the most recent one you were trying to flash should work. I successfully went directly from December to May. Just remember to remove the "-w" flag from the .bat file to avoid the wipe.
You won't lose all your stuff but you will need to re-root by flashing and installing Magisk.
The instructions from this thread are good:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Hope this helps.
Best,
Click to expand...
Click to collapse
awesome, thanks! ill check it out
also, off topic, how do you get into twrp? doing the volume down and power just takes you to the bootloader screen and going to recovery ends up just leading to the stock recovery. I had to fastboot into twrp to get back. It also wouldnt let me backup which is an whole different issue.

Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
vaeevictiss said:
awesome, thanks! ill check it out
also, off topic, how do you get into twrp? doing the volume down and power just takes you to the bootloader screen and going to recovery ends up just leading to the stock recovery. I had to fastboot into twrp to get back. It also wouldnt let me backup which is an whole different issue.
Click to expand...
Click to collapse

JasonVaritekMVP said:
Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
Click to expand...
Click to collapse
yea that looks different. i just installed the twrp zip file from inside twrp.
and i dont need to unroot first right? this does it automatically?

JasonVaritekMVP said:
Did you do both the fastboot to get into twrp and then the "adb shell twrp install" command listed in step 6 of the thread I linked?
It sounds like you might have booted with twrp but not made it persist.
Click to expand...
Click to collapse
EDIT: Scratch that. i ended up just doing that sideload of the ota like you suggested and im good to go now!
thanks again!

deleted, not needed

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

November update is out

Just received the new update for anyone who is interested?
https://www.essential.com/developer/current-builds

johnny8910 said:
Just received the new update for anyone interested?
Click to expand...
Click to collapse
Yes it's here .

Updating now!!!

Audio HD adapter support included

If rooted, I shold side load?
What and how?

I love reading my Google news feed on my PH-1 telling me that "November security patch rolling out to Pixel/Nexus devices, factory images and OTAs live" and my essential phone is already up to date! Best $250 I ever spent on a phone..... And with the new "Night Mode" P3 camera app I can even take night photos!
And I don't even have to root my phone!!!!
Ok... Guess I am a bit over happy

SirDigitalKnight said:
I love reading my Google news feed on my PH-1 telling me that "November security patch rolling out to Pixel/Nexus devices, factory images and OTAs live" and my essential phone is already up to date! Best $250 I ever spent on a phone..... And with the new "Night Mode" P3 camera app I can even take night photos!
And I don't even have to root my phone!!!!
Ok... Guess I am a bit over happy
Click to expand...
Click to collapse
Totally agree, had mine for a year now ?

downloaded current ota from https://www.essential.com/developer/current-builds
booted into twrp
flashed ota zip (will change boot to other partition)
flashed twrp installer zip (will flash recovery to both partitions)
rebooted back into twrp (now booted on other partition)
flashed magisk zip (flash to new current partition)
rebooted to system
everything seems to work :good:

The Jack of Clubs said:
downloaded current ota from https://www.essential.com/developer/current-builds
booted into twrp
flashed ota zip (will change boot to other partition)
flashed twrp installer zip (will flash recovery to both partitions)
rebooted back into twrp (now booted on other partition)
flashed magisk zip (flash to new current partition)
rebooted to system
everything seems to work :good:
Click to expand...
Click to collapse
thank you.
If only this above instruction included hyperlinks so that we could download everything direct to the phone.
Or we could download a prepatched twrp and magisk boot image and save a step or two?
=====EDIT====
Switched to slot A flashed OTA then patched boot image
Switched to slot B flashed OTA then patched boot image
rebooted, works.. thanks all

The Jack of Clubs said:
downloaded current ota from https://www.essential.com/developer/current-builds
booted into twrp
flashed ota zip (will change boot to other partition)
flashed twrp installer zip (will flash recovery to both partitions)
rebooted back into twrp (now booted on other partition)
flashed magisk zip (flash to new current partition)
rebooted to system
everything seems to work :good:
Click to expand...
Click to collapse
I gave it a shot, but mow the touchscreen dosent work. not in recovery or when booted up into rom.

jsaxon2 said:
I gave it a shot, but mow the touchscreen dosent work. not in recovery or when booted up into rom.
Click to expand...
Click to collapse
Yesterday I had the same issue. Then I download the TWRP.img file from the "rooting your essential phone" thread and flash it using fastboot then go to recovery and redid everything again. Problem sloved.

jsaxon2 said:
I gave it a shot, but mow the touchscreen dosent work. not in recovery or when booted up into rom.
Click to expand...
Click to collapse
You've booted from the inactive slot. Fastboot switch slots and go back to twrp.

Installed correctly
Installed correctly
Security Patch November 2018

If u guys would flash the entire firmware each month to BOTH slots, u would never have that issue.and use the twrp patched boot imgs.NOT the official twrp installer and such.theyre based on old firmware and won't work.

jsaxon2 said:
I gave it a shot, but mow the touchscreen dosent work. not in recovery or when booted up into rom.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77597383&postcount=86
try following these steps.

No more ADB root
Just successfully applied this patch. However, I can no longer get an ADB session on the device to go directly to a root prompt (#).
EDIT: I originally thought this was caused by the patch, but more likely it was NOT. I have created a separate thread here to address the issue in general.

Anyone else lose the back button with this update? It works however doesn't show up on screen.

Jay8212 said:
Anyone else lose the back button with this update? It works however doesn't show up on screen.
Click to expand...
Click to collapse
Nope, fine for me.

SirDigitalKnight said:
I love reading my Google news feed on my PH-1 telling me that "November security patch rolling out to Pixel/Nexus devices, factory images and OTAs live" and my essential phone is already up to date! Best $250 I ever spent on a phone..... And with the new "Night Mode" P3 camera app I can even take night photos!
And I don't even have to root my phone!!!!
Ok... Guess I am a bit over happy
Click to expand...
Click to collapse
Which camera apk are you using for the night sight mode please

combat goofwing said:
Which camera apk are you using for the night sight mode please
Click to expand...
Click to collapse
This one works for me.
https://drive.google.com/file/d/1nCqGUk9f1IfDuabPY2MXsqH6DnZcSzhc/view

Feb 2019 update now available

Hope by performance fixes they mean memory leak fix.

I have not seen os ram usage this low after boot in many months.

Did you have round corner?

yaral said:
Did you have round corner?
Click to expand...
Click to collapse
It squared it when I screenshot.

Anybody figure out how to turn off the rounded corners?

Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.

enigma2446 said:
Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.
Click to expand...
Click to collapse
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.

TomTheGeek3 said:
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.
Click to expand...
Click to collapse
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)

adiejg said:
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)
Click to expand...
Click to collapse
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.

enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
If I edit the .bat file and remove "format userdata", that will prevent the wipe?

njsges said:
If I edit the .bat file and remove "format userdata", that will prevent the wipe?
Click to expand...
Click to collapse
It should without issues but always prepare for hickups.

Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?

hssxda said:
Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?
Click to expand...
Click to collapse
Are you rooted?

After three days running, memory Leak not fixed.. Bummer

enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.

adiejg said:
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.
Click to expand...
Click to collapse
Titanium Backup used to require root access. You probably need to be rooted before you update via fastboot and run the backup through Titanium Backup. Then you will need to copy your backup files to a computer because fastboot flashing will erase your phone data. Next apply the fastboot update, root again, copy your backup back to the phone and restore your backup.

enigma2446 said:
Are you rooted?
Click to expand...
Click to collapse
I was but I followed all the proper steps but for some reason this morning my computer wouldn't real the OTA zip file. I tried it tonight using a different USB port on my laptop and it is worked first time... so weird...

d14r1 said:
After three days running, memory Leak not fixed.. Bummer
Click to expand...
Click to collapse
I don't have memory leak anymore..
1.5gb ram not in usage.
The last time I restarted my phone was after the update.

I'm using my Essential 'phone in the UK having recently purchased it used. On the 7th I had a notice to say that an update was available. When I tried to install it it downloaded, but refused to install saying: Couldn't update... installation problem. As far as I know the 'phone is running the stock software but I noticed that no updates had been installed since October 2018. I unchecked 'allow bootloader unlocking' in case that was the issue, but still couldn't perform the update.
I went onto the Essential website and downloaded the OTA image to my iMac, then, following the guide, sideloaded the update on to the 'phone. This worked well and I now have an updated PH-1. I'll have to see if March's update now installs correctly or not.

so.... am i reading this right... and here is my thinking...
to keep root and still take the OTAs
- go to Essentials site and download the image zip
- (to keep root) copy boot.img to your device, patch it through magisk, then copy it back to your ota folder.
- open flashall.bat, comment the format userdata (to keep your data), change the boot.img line to patched_boot.img
- run flashall.bat
- profit