Looks like February security update is rolling out.
Who's got the OTA? Also, what about the January Build NMJ88C OTA? Thanks in advance.
Saw this. How do we update if we're rooted? I unrootd and the update still won't install. Baring that, how can I clear that update notification since it won't update?
teostar said:
Saw this. How do we update if we're rooted? I unrootd and the update still won't install. Baring that, how can I clear that update notification since it won't update?
Click to expand...
Click to collapse
You can't take the update if you have TWRP installed, it all fail.
the correct way to update is go over to the ROM section and download the stock ROM version you want.
Flash it.
Root again.
Move on.
tech_head said:
You can't take the update if you have TWRP installed, it all fail.
the correct way to update is go over to the ROM section and download the stock ROM version you want.
Flash it.
Root again.
Move on.
Click to expand...
Click to collapse
I'm on stock NMJ88C, it was rooted (which conflicts with twrp) so I don't have trwp. I unrooted but still won't install.
lol a pixel 2 owner is sad they didnt get a security update first
https://twitter.com/essential/status/960953134511144960
Jonathanlc2005 said:
lol a pixel 2 owner is sad they didnt get a security update first
https://twitter.com/essential/status/960953134511144960
Click to expand...
Click to collapse
I got the update notice about 45 minutes ago.
Now installed.
Still waiting for Sprint to unlock my phone....... ARGH!!!!!
They are so messed up.
I just got the OTA update in the UK
Sent from my Essential Phone using XDA Labs
First time my Sprint locked ph-1 got a security update at the same time as my unlocked ph-1. :good: job Sprint
nothing on beta yet
I got the update in my Essential phone, and my Pixel 2 is still in January security patch. Good job Essential.
I hope 8.1 beta arrived by Friday(or so) as planned.
Anybody else experience call with no audio after updating this build. I have to rollback to previous firmware to fix no audio issue on any phone call.
saynot79 said:
Anybody else experience call with no audio after updating this build. I have to rollback to previous firmware to fix no audio issue on any phone call.
Click to expand...
Click to collapse
Same issue here. Will need to roll back now!
Update: just reboot phone and got audio back on phone call now! ?
rickyt63 said:
Same issue here. Will need to roll back now!
Update: just reboot phone and got audio back on phone call now! ?
Click to expand...
Click to collapse
Same here no audio at all.
Can't roll back right now.
Waiting for Sprint to UICC unlock. What an eff'n disaster. Don't get me started.
tech_head said:
Same here no audio at all.
Can't roll back right now.
Waiting for Sprint to UICC unlock. What an eff'n disaster. Don't get me started.
Click to expand...
Click to collapse
Did you reboot and try again?
I didn't have to roll back, just reboot it.
My is unlocked not Sprint though.
rickyt63 said:
Did you reboot and try again?
I didn't have to roll back, just reboot it.
My is unlocked not Sprint though.
Click to expand...
Click to collapse
Several reboots, no audio sent to other end or received from other end.
If it ain't broken, no need to fix. Don't see all the need to rush out for a security update (that apparently is causing audio issues for some).
When 8.1 is here, i'll bite..
rickyt63 said:
Did you reboot and try again?
I didn't have to roll back, just reboot it.
My is unlocked not Sprint though.
Click to expand...
Click to collapse
Now that Sprint understands that their UICC unlock system is broken I went back to B3.
Audio problem solved.
On nmj32f, stock/unrooted, Sprint, got the nmk24b sometime overnight. Haven't installed it yet though. Seems odd to go from nov17 security update to feb18.
Sent from my PH-1 using XDA-Developers Legacy app
Related
I have a Verizon Pixel that is bootloader locked and I have unenrolled from the beta and I'm not receiving the OTA to go back to N. I've tried re-enroll and unenroll, also downloading one of the OTA and flash through adb sideload but it says the version I'm using is to new.
Any thoughts?
I think you have to flash back manually
after unenrolling, i just went to settings, system, updates and it was ready to download the stock android n ota
bturkel said:
I think you have to flash back manually
Click to expand...
Click to collapse
Yeah, but he has locked bootloader and Verizon phone
exad said:
after unenrolling, i just went to settings, system, updates and it was ready to download the stock android n ota
Click to expand...
Click to collapse
I think the op would like to know how long that took.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
I think the op would like to know how long that took.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seconded. I've been unenrolled since Friday and still haven't gotten the OTA for N.
I've been unenrolled since maybe Wednesday night of last week with a locked Verizon Bootloader. No OTA update back to Android N so I am going to download the flash image at https://developers.google.com/android/images.
Battery life on the beta has been abysmal.
kantaris said:
I've been unenrolled since maybe Wednesday night of last week with a locked Verizon Bootloader. No OTA update back to Android N so I am going to download the flash image at https://developers.google.com/android/images.
Battery life on the beta has been abysmal.
Click to expand...
Click to collapse
That's not going to work. You have to wait it out. It's why I didn't enroll although I did on my unlocked 5x.
Drat, thanks for the heads up, this bites.
I just had a quick chat with Google Support, they are telling me that 'there is an issue with receiving the OTA back to N from the O beta, and that they are working on a fix'.
Sorry, I was busy, but for me it was instantly, right after I unenrolled.
This morning I went to the beta signup, enrolled my device again and unenrolled it, was asked to install Nougat within a minute.
kantaris said:
I've been unenrolled since maybe Wednesday night of last week with a locked Verizon Bootloader. No OTA update back to Android N so I am going to download the flash image at https://developers.google.com/android/images.
Battery life on the beta has been abysmal.
Click to expand...
Click to collapse
Has anyone else had a problem with this webpage. I've been trying to download the factory image and/or the OTA image. When I click on "Acknowledge" button, it doesn't do anything.
Run it in incognito mode or turn off script blockers
InoHello everyone.
It has been a long time since my last post....
I bought my HTC U11 128GB/6GB last August and I find it awesome. Since the announcement of the Oreo update being rolled out, I became impatient to try it. I checked and checked for updates... but nothing. Right now it's running Android 7.1.1, SW version 1.27.400.21, with the October 2017 security patch.
How can I find if there are other updates that I didn't receive? How can I find my model number? How can I force the updates?
Info: My phone is already unlocked (it's the first thing that I did after receiving it).
Edit: with Simple CID Getter I found out that my CID is HTC__060. Is it the DUGL/India model? If yes then I guess that the Oreo update didn't arrive yet?
Thank you in advance to anyone that can help me.
Samribi said:
InoHello everyone.
It has been a long time since my last post....
I bought my HTC U11 128GB/6GB last August and I find it awesome. Since the announcement of the Oreo update being rolled out, I became impatient to try it. I checked and checked for updates... but nothing. Right now it's running Android 7.1.1, SW version 1.27.400.21, with the October 2017 security patch.
How can I find if there are other updates that I didn't receive? How can I find my model number? How can I force the updates?
Info: My phone is already unlocked (it's the first thing that I did after receiving it).
Edit: with Simple CID Getter I found out that my CID is HTC__060. Is it the DUGL/India model? If yes then I guess that the Oreo update didn't arrive yet?
Thank you in advance to anyone that can help me.
Click to expand...
Click to collapse
There is unofficial update: https://forum.xda-developers.com/u1...u-firmware-t3612048/post74674442#post74674442 and https://forum.xda-developers.com/u1...u-firmware-t3612048/post75213806#post75213806 You can manually install OTA.
4squer said:
There is unofficial update: https://forum.xda-developers.com/u1...u-firmware-t3612048/post74674442#post74674442 and https://forum.xda-developers.com/u1...u-firmware-t3612048/post75213806#post75213806 You can manually install OTA.
Click to expand...
Click to collapse
Thank you very much. I will look at it.
Samribi said:
Thank you very much. I will look at it.
Click to expand...
Click to collapse
Please tell if it worked
dany xe said:
Please tell if it worked
Click to expand...
Click to collapse
I just did a backup. Downloading the first files to upgrade from 1.27.400.21 to 2.31.400.6 now. Do I have to flash all the files? OTA, recovery, boot and firmware? Or only the OTA zip is enough?
Edit:
I tried to install the OTA Zip with TWRP and it gives me an error message. I think I will wait until the official OTA arrives (hoping it doesn't take too long).
The wwe version has only just been updated so you'll probably get the update in a month or so once the carrier is happy with the release. My advice is to wait. Do not root and s-off for it.
Samribi said:
I just did a backup. Downloading the first files to upgrade from 1.27.400.21 to 2.31.400.6 now. Do I have to flash all the files? OTA, recovery, boot and firmware? Or only the OTA zip is enough?
Edit:
I tried to install the OTA Zip with TWRP and it gives me an error message. I think I will wait until the official OTA arrives (hoping it doesn't take too long).
Click to expand...
Click to collapse
It's OTA zip, you dont have to s-off or root, here you have guide how to install OTA: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
4squer said:
It's OTA zip, you dont have to s-off or root, here you have guide how to install OTA: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
Click to expand...
Click to collapse
I'm looking to the post, and (being S-OFF already) it says that I have to flash a Combined Full Wipe firmware and then the OTA. Does it mean that I will lose all my data?
You can try to connect through the VPN that allows to select server located in India.
Had exactly same problem as OP.
Solution with VPN worked for me. And phone updated to Software version 2.42.400.3
EugeniusD80 said:
You can try to connect through the VPN that allows to select server located in India.
Had exactly same problem as OP.
Solution with VPN worked for me. And phone updated to Software version 2.42.400.3
Click to expand...
Click to collapse
What kind of VPN did you use? What software?
Samribi said:
What kind of VPN did you use? What software?
Click to expand...
Click to collapse
I used NordVPN. They have servers in India.
Update download was a bit slow though.
Thank you very much. It is downloading now. Slow but at least I will have it. Thank you again.
EugeniusD80 said:
I used NordVPN. They have servers in India.
Update download was a bit slow though.
Click to expand...
Click to collapse
Downloaded the first time with VPN, tried to install it, but it didn't work (I had TWRP, and after reboot I got the message that the update was corrupted). I flashed the recovery from the Google Spreadsheet: https://docs.google.com/spreadsheet...EYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=2137120377
using:
Code:
adb reboot download
and then:
Code:
fastboot flash recovery recovery_1.27.400.21.img
I checked for updates and it asked me to download it again, no VPN needed. Downloaded it and tried to install it (much faster). Phone restarted, update started, and after a few seconds I saw a black screen with a red triangle.. it looks the same as when it's in recovery mode.... Had to restart the phone again.
I'm trying again to download it and I'll check better if I can see the error.
Edit: It goes fast from 1% to 24%, then it stops at 24% for about 19 seconds and then black screen with red triangle...
Any idea what the problem could be?
Samribi said:
I checked for updates and it asked me to download it again, no VPN needed. Downloaded it and tried to install it (much faster). Phone restarted, update started, and after a few seconds I saw a black screen with a red triangle.. it looks the same as when it's in recovery mode.... Had to restart the phone again.
I'm trying again to download it and I'll check better if I can see the error.
Edit: It goes fast from 1% to 24%, then it stops at 24% for about 19 seconds and then black screen with red triangle...
Any idea what the problem could be?
Click to expand...
Click to collapse
Sorry, don't think I can be of any help here. Have almost no experience with this sort of things.
In my case I did not do any tweaking with the original OS.
First tried to explore any possible option to get it "official" way.
My only guess would be to try to roll back to the original state and to have no trace of tweaking.
EugeniusD80 said:
Sorry, don't think I can be of any help here. Have almost no experience with this sort of things.
In my case I did not do any tweaking with the original OS.
First tried to explore any possible option to get it "official" way.
My only guess would be to try to roll back to the original state and to have no trace of tweaking.
Click to expand...
Click to collapse
Yes, I will try to do a factory reset this weekend. If it's not working, I will try to follow the instructions on the other post to flash a RUU.
Edit: I did a factory reset, tried to update to Oreo, it still stopped at 24%. I flashed the latest RUU I could find on the spreadsheet, and then after 2 updates I'm finally on Oreo!!!
HTC u11 Oreo update received via WiFi 4 days ago
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.
Just got the notification!
Android 9.0 - Beta 3
PPR1.180610.066
Don't notice anything new so far. It looks like the font may be slightly different, and the kernel has been updated. Still no notch settings, and the lag that happens still exists.
Sorry to be thick but do a have too sidload or flash or is it OTA?
I have no updates...
Sent from my PH-1 using Tapatalk
oracleoftruth said:
Sorry to be thick but do a have too sidload or flash or is it OTA?
I have no updates...
Click to expand...
Click to collapse
I fastboot flashed but you can OTA by downloading the zip from essentials sideloading like you mention
Did the GPU version changed？
OTA rolling out
t2jbird said:
OTA rolling out
Click to expand...
Click to collapse
It rolled out when I posted it, I got the notification about half hour before then. Probably a staggered rollout though
crixley said:
It rolled out when I posted it, I got the notification about half hour before then. Probably a staggered rollout though
Click to expand...
Click to collapse
This was the actual ota, pushed directly to the phone.
Package was released when you posted. I thought you just flashed it through fastboot.
crixley said:
Just got the notification!
Android 9.0 - Beta 3
PPR1.180610.066
Click to expand...
Click to collapse
I upgraded from Beta 2 using fastboot rom, but didnt erase data. Everthing is working except home button. Anyone else facing this issue?
I updated ota and my home button is working fine.
hariprs said:
I upgraded from Beta 2 using fastboot rom, but didnt erase data. Everthing is working except home button. Anyone else facing this issue?
Click to expand...
Click to collapse
Sent from my PH-1 using Tapatalk
Beta 4 update killed my WIFI
The Beta 4 update killed my WIFI reception on my Essential phone. YMMV
hello together.
I`m on the beta 3 with unlocked bootloader.
When I try to install the update ota on the phone I get a installation error.
What could be the problem? Do I have to lock the bootloader to be able to install updates ota?
I know that I can sideload the ota update via fastboot but would like to be able to get ota updates directly on the phone.
t2jbird said:
This was the actual ota, pushed directly to the phone.
Package was released when you posted. I thought you just flashed it through fastboot.
Click to expand...
Click to collapse
Yes, as was mine. I always flash them through fastboot, I'm rooted and even when I wasn't I had issues with the latest radio not applying, OTA failing even though I unrooted etc. That's why in the post I said I just received the notification.
hariprs said:
I upgraded from Beta 2 using fastboot rom, but didnt erase data. Everthing is working except home button. Anyone else facing this issue?
Click to expand...
Click to collapse
I did the same, no issues with my home button. Did you get any failed errors? I usually flash each .img myself
New PH-1 owner here, well new to me but mint from someone else lol. Woke up with the OTA update flag. Unlocked bootloader and unlocked critical. Quick download and restart and it's good to go... No chance to play with anything or poke around yet though
mikeearwood said:
The Beta 4 update killed my WIFI reception on my Essential phone. YMMV
Click to expand...
Click to collapse
Same here. I flashed the latest stable Oreo 8.1 then flashed P beta. It fixed the problem.
What's the best way to flash the fastboot files without wipe? Can I edit out the wipe command in the bat file?
srscott said:
What's the best way to flash the fastboot files without wipe? Can I edit out the wipe command in the bat file?
Click to expand...
Click to collapse
If you're looking to update the build, you can just flash the OTA from the Essential site in TWRP.
Thanks!
crixley said:
I did the same, no issues with my home button. Did you get any failed errors? I usually flash each .img myself
Click to expand...
Click to collapse
Data reset solved the problem.
I also flash the .img myself, didnt get any error while flashing.
Anyway thanks your reply
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