Updates as indicated are rolling out!
What's the security patch date? August?
linuxct said:
What's the security patch date? August?
Click to expand...
Click to collapse
July... I expected August ?
Edit.
Anyone notice any of the bug fixes or performance improvements they are talking about?
Munk0 said:
Anyone notice any of the bug fixes or performance improvements they are talking about?
Click to expand...
Click to collapse
The camera went from ver. 1.8 to 1.9 but i dont know what the specifics are. The update took like 45 min. to complete.
The Dolby Atmos demo is still upside-down /wrong way around
if i'm rooted and have twrp and magisk 17 installed, will I able to update and if yes will I lose root?
majedalanni said:
if i'm rooted and have twrp and magisk 17 installed, will I able to update and if yes will I lose root?
Click to expand...
Click to collapse
There's no factory image right now so you can't use the corresponding boot image to flash magisk back, it might work with the May one but I wouldn't count on it. You can also try the A/B magisk feature (flash stock boot.img, apply OTA, install magisk to inactive slot). You will definitely lose TWRP though. This wouldn't be a problem if fastboot boot worked.. I'm sure they'll release the images soon enough.
I'm still @ feb patch lol
can never get the OTA
Can someone post the build number/build version of the update?
OPM1.171019.011-RZR-180803.6033
Android version...8.1.0
Was trying to see if I could grab the factory images...doesn't look like it.
MishaalRahman said:
Was trying to see if I could grab the factory images...doesn't look like it.
Click to expand...
Click to collapse
I'm also waiting for the factory image. I think that's all I need in order to root my device. I need the boot img. I hope they don't take too long to post it.
lyall29 said:
I'm also waiting for the factory image. I think that's all I need in order to root my device. I need the boot img. I hope they don't take too long to post it.
Click to expand...
Click to collapse
They seem to be taking their time, last time it was within a day or so.
Out in HKG, and havent gotten the update yet
Related
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.
https://www.essential.com/developer/current-builds
Also, just received it on my phone this very moment.
Downloading now! Came to post this exact thing.
UPDATE
Screen shot for those interested
changelog?
mookiexl said:
changelog?
Click to expand...
Click to collapse
Check the screenshot one post right before your!
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
ziddey said:
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
Click to expand...
Click to collapse
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
If I try to unroot by restoring images it says "Stock backup does not exist!"
sruel3216 said:
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
Click to expand...
Click to collapse
I believe you'd fail the OTA if you have an altered boot, but you can try.
oracleoftruth said:
If I try to unroot by restoring images it says "Stock backup does not exist!"
Click to expand...
Click to collapse
I dumped the old boot before rebooting just in case: https://drive.google.com/file/d/11MjB4kTOHuxbUyHe_kIwZ1d0wqp6-Nmf/view?usp=sharing
You can flash it to your boot slot while rooted, take the OTA, and then install magisk to the other slot before rebooting.
Drop a shell.
Determine current boot slot: getprop |grep boot.slot
Flash the boot: dd if=/path/to/boot_b.img of=/dev/block/by-name/boot_b (change to boot_a if that's your slot)
Of course, don't reboot since you'll lose root. Instead, you should now be able to take the OTA, and then use magisk to patch the other slot before rebooting.
Magisk should now have a backup for next time, so you can uninstall/ota/install in the future.
Nice...4 days in, and patched with the security update already.
ziddey said:
I believe you'd fail the OTA if you have an altered boot, but you can try.
Click to expand...
Click to collapse
Was curious cuz I was able to update the OTA on my pixel when rooted with custom kernel.
For some reason after I ran the magisk uninstaller and made sure to flash the stock boot image I still ran into problems updating via OTA and after sideloading the OTA for the Sept Update with success I found that TWRP would seem to freeze whenever it got to the main screen for some reason. I was able to use adb commands to reboot to bootloader and flash the stock kernel for the update and was able to boot normally. Just wondering if anybody else is having issues with TWRP freezing after installing the security update and yes I did remove fingerprint and lock screen security before booting into TWRP so I know its not something from that causing it to freeze.
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Just installed patch. Scrolling feels so much better, especially when scrolling slow.
gorm said:
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Click to expand...
Click to collapse
That's exactly what happened to me.. a user on /r/essential said they had the same issue; frustrating!
I'm going to be going back to 8.1 via fastboot, and then flashing 9.0 august, THEN fastbooting september, and if that doesn't work, I'm going to fastboot 9.0 august and then try OTA to
get my screen back.
Really weird stuff.
EDIT: Here's a supposed fix for those with the touchscreen issue - https://www.reddit.com/r/essential/comments/9d0lg3/for_anyone_having_trouble_with_touchscreen_not/
I don't know if we're allowed to link to reddit or not, but I'm doing that fix now.
Thanks!
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
jon_ybanez said:
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
Click to expand...
Click to collapse
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
beard805 said:
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
Click to expand...
Click to collapse
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Sadly, I don't know much about the SIM side of the issue
Hope someone with more knowledge can chime in!
jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Are you rooted? Here are the unlocked modemst files: https://drive.google.com/file/d/1LQC-2QOC-PWX7vza-82tpwFrnUjaGZVq/view?usp=sharing
You can try to dd them:
Code:
dd if=/path/to/modemst1.img of=/dev/block/by-name/modemst1
dd if=/path/to/modemst2.img of=/dev/block/by-name/modemst2
Would be a good idea to backup your current images
from https://forum.xda-developers.com/essential-phone/how-to/discussion-brainstorm-sim-unlock-t3724135
So I just received a new security update, I don't think there's anything more than just the latest security package
same here, just 65 MB. couldn't find any new features yet.
Scrolling is definitely smoother.
It seems like booting up takes shorter time to load unlike with the previous update patches.
any improvements in unlock speed?
Did they bring back d2tw?
loop4444 said:
any improvements in unlock speed?
Click to expand...
Click to collapse
Phone is somewhat smoother / faster in general.
coolwei1 said:
Did they bring back d2tw?
Click to expand...
Click to collapse
Nope.
stuck
I am stuck on september update, everytime i try to install the october update it says installation problem (i have an unlocked bootloader) what to do i am a newbie when it comes to tinkering with android on this level.
peshovich said:
I am stuck on september update, everytime i try to install the october update it says installation problem (i have an unlocked bootloader) what to do i am a newbie when it comes to tinkering with android on this level.
Click to expand...
Click to collapse
Same here. Maybe it's because I'm rooted...
I'm waiting for the next (official) fastboot image...
downloadonlyaccount said:
Same here. Maybe it's because I'm rooted...
I'm waiting for the next (official) fastboot image...
Click to expand...
Click to collapse
Well at least i am not alone in this one, hopefully Xiaomi will fix this issue and we can update it normally. Gonna follow this thread.
Especially if you've rooted, you probably have modified system or vendor partitions.
You can see what the OTA doesn't like by looking at adb.
Code:
adb logcat | grep update_engine
There's been no 10.0.14.0 fastboot image but I do have backups of these partitions I made myself. They're huge but I might be able to get them on the internet if needed...
peshovich said:
Well at least i am not alone in this one, hopefully Xiaomi will fix this issue and we can update it normally. Gonna follow this thread.
Click to expand...
Click to collapse
So, now with 10.0.16.0 released, I was able to skip the .15 version. I had to download the complete package (around 1 GB) but now I'm on latest version. Just need to root again .
'
Well, they're on the Google site. Now...to figure out which one is which ??
Sweet!!
Check here: https://support.google.com/pixelphone/thread/18553639?hl=en
Wish we would get more details. Improvement on smooth display and camera doesn't give us much. Maybe they fixed some of the yellow tinted pictures in the camera.
I'll probably just keep mine on force 90hz anyways. My battery life has been just fine. Even running white theme all the time.
spencer92a said:
Check here: https://support.google.com/pixelphone/thread/18553639?hl=en
Click to expand...
Click to collapse
-14 looks like for me
spencer92a said:
Check here: https://support.google.com/pixelphone/thread/18553639?hl=en
Click to expand...
Click to collapse
So nothing for QD1A.190821.011?
StrangerWeather said:
So nothing for QD1A.190821.011?
Click to expand...
Click to collapse
That's oct patch, you need to flash nov patch
Mr Patchy Patch said:
I'll probably just keep mine on force 90hz anyways. My battery life has been just fine. Even running white theme all the time.
Click to expand...
Click to collapse
I have mine forced 90hz all the time. I always have a charger available and like the extra speed.
update without losing root ?
Jiggs82 said:
That's oct patch, you need to flash nov patch
Click to expand...
Click to collapse
I don't think so tbh, it's one of three variants: 014, 007, 011 based on this and this.
TheUndertaker21 said:
update without losing root ?
Click to expand...
Click to collapse
Not really. You'll need to flash the November update with the -w removed, let it boot up, then put a copy of the November boot.img on your internal storage, then patch it with magisk. Then you'll need to fastboot your patched boot.img, and you should be good to go :good:
Badger50 said:
Not really. You'll need to flash the November update with the -w removed, let it boot up, then put a copy of the November boot.img on your internal storage, then patch it with magisk. Then you'll need to fastboot your patched boot.img, and you should be good to go :good:
Click to expand...
Click to collapse
Thanks figured as much
From my previous pixels
TheUndertaker21 said:
update without losing root ?
Click to expand...
Click to collapse
If you receive the OTA, you can just try this method from pixel 3 xl thread a while back as i did before on my pixel 3 xl too :
S8rooted&tooted said:
Just took the OTA.
Uninstall restore images
Download OTA and DONT REBOOT
reinstall magisk to inactive slot.
Blammo up and running.
Click to expand...
Click to collapse
So .011 Variants have to wait? No Update available yet.
I noticed that they show one of the downloads available are specifically for Verizon and ATT. I have a Google Unlocked Device - but I am on ATT. Does anyone know what happens if I flash the firmware intended for ATT? If my bootloader is locked when I flash it - will my bootloader be locked after flashing ? Just curious.....
Geekser said:
I noticed that they show one of the downloads available are specifically for Verizon and ATT. I have a Google Unlocked Device - but I am on ATT. Does anyone know what happens if I flash the firmware intended for ATT? If my bootloader is locked when I flash it - will my bootloader be locked after flashing ? Just curious.....
Click to expand...
Click to collapse
No, it won't lock your bootloader. Only you can do that manually. I just updated mine to November, and all is well :good:
Badger50 said:
No, it won't lock your bootloader. Only you can do that manually. I just updated mine to November, and all is well :good:
Click to expand...
Click to collapse
I usually would have had my ota by now. Still nothing for me. Kinda weird.
Mr Patchy Patch said:
I usually would have had my ota by now. Still nothing for me. Kinda weird.
Click to expand...
Click to collapse
Nothing for me yet either
Msan2000 said:
Nothing for me yet either
Click to expand...
Click to collapse
It's weird. I wonder what's up with that.
the update of June 2020 is online
https://developers.google.com/android/images
https://dl.google.com/dl/android/aosp/coral-qq3a.200605.001-factory-dbd8ce20.zip
It fixed the face id finally.
Magisk root still working with June update.
gm007 said:
It fixed the face id finally.
Click to expand...
Click to collapse
What was wrong with it?
Personal safety is not available on mine.
pilotgav said:
What was wrong with it?
Click to expand...
Click to collapse
It was broken when downgrading from Android 11.
This include the Covid tracker?
Sent from my Pixel 4 XL using Tapatalk
MicroMod777 said:
This include the Covid tracker?
Click to expand...
Click to collapse
Doesn't give me an option to turn it on but it's there
MicroMod777 said:
This include the Covid tracker?
Click to expand...
Click to collapse
Do you mean an application or the service? The service was there before the update.
gm007 said:
It fixed the face id finally.
Click to expand...
Click to collapse
You might want to state which version of the Face Unlock issue you're talking about, the one from the DP4 and subsequent downgrade is still there.
Tried to update with magisk via OTA method
Phone boots to black screen, only thing I can do is access the power menu...
dragynbane222 said:
You might want to state which version of the Face Unlock issue you're talking about, the one from the DP4 and subsequent downgrade is still there.
Click to expand...
Click to collapse
Yes I'm talking about the downgrade from dp4 to 10.
Let me tell you what I did,it was by mistake that I fix it.
I was on May build with face id broken,I downloaded the June ota yesterday but by mistake I choose Telstra ota the one that end with 002.A1 and face id work.
Then I realized that the build number is wrong for my phone so I tried to flash the full June build the one that end with 001 and again face id stopped working so I decided to stay with Telstra build
Hey guys after flashing magisk image tje touchscreen doest react so i cant log in. After flashing stock image everything works fine again. Anyone else experiencing this??
xdidnothingwrongx said:
Hey guys after flashing magisk image tje touchscreen doest react so i cant log in. After flashing stock image everything works fine again. Anyone else experiencing this??
Click to expand...
Click to collapse
Best advice I could give is to first patch the boot.img when all your magisk modules have either been disabled, or removed. Then dirty fastboot, (-w removed) the factory image to your inactive slot, let it boot up, then fastboot the magisk_patched.img to both slots. Also make sure your platform-tools are up to date. Best of luck to ya :good:
gm007 said:
Do you mean an application or the service? The service was there before the update.
Click to expand...
Click to collapse
Since when?
Sent from my Pixel 4 XL using Tapatalk
MicroMod777 said:
Since when?
Click to expand...
Click to collapse
If you mean the covid exposure notification i got it 2 weeks ago, it's in the google setting in the system settings.
Updates to Telstra and worked. Hope they release an update for the regular software soon. Thank you for the tip.
Worse battery performance on June patch than may