Hi guys,
i have a pixel and i want to enrrol to the beta program, i just done the process but it seams that update is not arriving, its posible that verizon pixels can't enroll to beta program?
http://www.droid-life.com/2017/01/30/android-7-1-2-beta-download-update-nexus-pixel/
Regards
You can download the full image here
I dont have oem unlocked. I can sideloade it?
Yea even i didn't get it. I guess it not for the verizon phones.
Can anyone who has upgraded to 7.1.2 let us know if it appears stable enough for a daily driver and have they noticed any differences ? Thank you.....
Another locked bootloader VZW customer here who enrolled and is waiting for OTA. I think we'll get it, just have to wait for OTA's to start. Google let us enroll, and we seem to have gotten updates from Google and not VZW so far. I think it'll just take a day or 2 to start rolling.
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
I am a non VZW pixel user (Koodo - Canada) and have not received the OTA after signing up yesterday. They note that it may take 24 hours and looks like it's going to for me.
k.s.deviate said:
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
Click to expand...
Click to collapse
I know that the bootloader is what loads the Android filesystem to the boot image, I wonder if it can somehow be manipulated to unlock and root since you mention that the boot image is different? Does anyone know? Thanks
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
farfromovin said:
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
Click to expand...
Click to collapse
Signed up yesterday for both my Pixel (VZW sim) and Pixel XL (Project Fi sim) both bought direct from Google. Pixel XL rec'd update almost immediately not yet on Pixel so far.
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Sent from my Pixel using Tapatalk
joshw0000 said:
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Click to expand...
Click to collapse
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Nope it's exactly that. Just remove -w so it doesn't wipe the device. It's how I update my Pixel and 5X since I'm impatient waiting for OTAs.
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Sent from my Pixel using Tapatalk
joshw0000 said:
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Click to expand...
Click to collapse
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
OTA hasn't rolled for the pixel yet, likely "soon", my guess is today or tomorrow at the latest since XL has gone out. I am on project FI and got the pixel through the play store fyi
murryrulz said:
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
Click to expand...
Click to collapse
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
I am also in the waiting for the OTA camp and use an unlocked Verizon Pixel and PIxel XL. I have had better luck using the TWRP sideload method and it installing to the other slot with each subsequent sideload appears to me a more consistent way to keep everything updated in the same way that the system OTA works.
joshw0000 said:
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Get rid of windows, use Linux, no messing around with anything, it just works ?
-------- runs -----_ducks_---- runs ----
Sent from my Pixel using XDA-Developers Legacy app
Related
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
bush911 said:
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
Click to expand...
Click to collapse
I have tried to stay away from flash fire because I know a couple buddies who soft-bricked by using it.
xxbilxx said:
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Click to expand...
Click to collapse
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
TonikJDK said:
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
I don't have to sideload the March security patch first?
xxbilxx said:
I don't have to sideload the March security patch first?
Click to expand...
Click to collapse
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
TonikJDK said:
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
Click to expand...
Click to collapse
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
xxbilxx said:
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
Click to expand...
Click to collapse
Correct, you want N2G47E.
TonikJDK said:
Correct, you want N2G47E.
Click to expand...
Click to collapse
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
xxbilxx said:
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
Click to expand...
Click to collapse
No problem at all. Second to the last post in the same thread I linked you to before. It all still works fine on 7.1.2. Did all of this myself yesterday afternoon.
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Download the OTA, Flash it from TWRP, reflash twrp and reboot
mikeprius said:
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Click to expand...
Click to collapse
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
yeah saved it. There was only one section that had the w- and it was right before the update image. I can try it again at some point later on but that's what I did. I tried to sideload adb the OTA first which does not wipe data but kept getting an error saying device not found and emulator.
robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
Your instructions worked perfectly for me. I'm nor sure what setup the other guy had, but I did make sure I removed the -w like 20 times.
Juli112 said:
Download the OTA, Flash it from TWRP, reflash twrp and reboot
Click to expand...
Click to collapse
are you on the latest twrp rc2 or rc1?
Has anyone received the update ota on a stock google pixel XL for verizon. Mine keeps telling me I am current?
Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
The problem is I sideloaded the J series rom by mistake, and not the E series rom. The J series is the euro spec version
I tried to correct it by reflashing the E series but I received an error that the timestamp on the OTA was sooner than the J series and downgrading was not allowed
Does anyone have a download link to the Verizon specific OTA file for 7.1.2 so I can attempt to flash and correct???
Is the only other fix trying to do a full system reimage or the previous 7.1.1 build ??
Thanks
Sent from my Pixel using Tapatalk
Joe92T said:
Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
The problem is I sideloaded the J series rom by mistake, and not the E series rom. The J series is the euro spec version
I tried to correct it by reflashing the E series but I received an error that the timestamp on the OTA was sooner than the J series and downgrading was not allowed
Does anyone have a download link to the Verizon specific OTA file for 7.1.2 so I can attempt to flash and correct???
Is the only other fix trying to do a full system reimage or the previous 7.1.1 build ??
Thanks
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Use the full E image and take out the -w from flash-all.bat so you don't wipe SD.
Sent from my Pixel using XDA-Developers Legacy app
That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Sent from my Pixel using Tapatalk
Joe92T said:
That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Click to expand...
Click to collapse
I currently have N2G47E on my Verizon purchased Pixel now. No issues that I've run into.
Joe92T said:
That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Use E. The new VZW firmware isn't on Google's site. I flashed E and all is just fine.
Sent from my Pixel using XDA-Developers Legacy app
Joe92T said:
Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
Click to expand...
Click to collapse
Are you bootloader unlocked?
No
Sent from my Pixel using Tapatalk
So I tried to flash the stock Google firmware for the E build and got told no due to locked bootloader... I can't even flash official images?
Sent from my Pixel using Tapatalk
Joe92T said:
So I tried to flash the stock Google firmware for the E build and got told no due to locked bootloader... I can't even flash official images?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Not with a locked bootloader.
Sent from my Pixel using XDA-Developers Legacy app
So the only option I have is to find ota packages with a older timestamp?
Sent from my Pixel using Tapatalk
Joe92T said:
So the only option I have is to find ota packages with a older timestamp?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
If it is running fine on J then why not wait until May and sideload or take the OTA then.
I'm hearing there is a known Verizon issue with Volte on the K build anyway.
Sent from my Pixel using XDA-Developers Legacy app
I really wish I could factory flash the entire new image. I almost feel like I've "corrupted" it by installing this incorrect OTA and that even if I flash a new ota going forward that there may be some old lingering stuff kicking around from this old one
Sent from my Pixel using Tapatalk
Joe92T said:
I really wish I could factory flash the entire new image. I almost feel like I've "corrupted" it by installing this incorrect OTA and that even if I flash a new ota going forward that there may be some old lingering stuff kicking around from this old one
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Nothing is corrupted, relax. Wait for the OTA next time and then factory reset it if that will ease your mind. But it's really not necessary the phone is fine. You might be able to sign up for the beta, it will wipe the device, then roll back with another wipe and accept the OTA when it arrives. Probably more trouble than it's worth.
Sent from my Pixel using XDA-Developers Legacy app
Protibus said:
Use the full E image and take out the -w from flash-all.bat so you don't wipe SD.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Okay, this one caught my eye. The OP, like me, has a Verizon Pixel. So my phone's bootloader is locked until someone finds an appropriate exploit and publishes it, if ever. And I also sideloaded the N2G47J image by mistake, didn't know it was Deutsche Telekom, thought it was just the latest *sigh*. Learned my lesson about doing research.
After sideloading N2G47J, I did try to sideload the N2G47E image, and that failed because the E image is earlier than the J image, and it won't let me flash an earlier image (bootloader locked).
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Otherwise I'll have to wait for next month's update to get my phone working right again. At the moment, it has the "Wi-Fi calling" setting set to "Cellular preferred", which causes the phone to use up a lot of battery trying to make a low cellular signal work. When I've had "Wi-Fi calling" set to "Wi-Fi preferred", that doesn't happen since if you prefer Wi-Fi calling, apparently the phone doesn't care about the cell signal as long as you're on Wi-Fi. So at home, I have to set it on Airplane mode and turn Wi-Fi back on to keep my battery from getting drained too quickly. I'm anxious to get this problem fixed, since I forget to turn Airplane mode off when I leave the house and miss calls and texts.
Thanks!
RogerSC said:
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Click to expand...
Click to collapse
No you can not do that, you are bootloader locked.
RogerSC said:
Okay, this one caught my eye. The OP, like me, has a Verizon Pixel. So my phone's bootloader is locked until someone finds an appropriate exploit and publishes it, if ever. And I also sideloaded the N2G47J image by mistake, didn't know it was Deutsche Telekom, thought it was just the latest *sigh*. Learned my lesson about doing research.
After sideloading N2G47J, I did try to sideload the N2G47E image, and that failed because the E image is earlier than the J image, and it won't let me flash an earlier image (bootloader locked).
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Otherwise I'll have to wait for next month's update to get my phone working right again. At the moment, it has the "Wi-Fi calling" setting set to "Cellular preferred", which causes the phone to use up a lot of battery trying to make a low cellular signal work. When I've had "Wi-Fi calling" set to "Wi-Fi preferred", that doesn't happen since if you prefer Wi-Fi calling, apparently the phone doesn't care about the cell signal as long as you're on Wi-Fi. So at home, I have to set it on Airplane mode and turn Wi-Fi back on to keep my battery from getting drained too quickly. I'm anxious to get this problem fixed, since I forget to turn Airplane mode off when I leave the house and miss calls and texts.
Thanks!
Click to expand...
Click to collapse
You cannot flash a full image with a locked bootloader, must be unlocked. With a locked bootloader you are only able to sideload an OTA using ADB.
Sent from my Pixel using XDA-Developers Legacy app
Protibus said:
You cannot flash a full image with a locked bootloader, must be unlocked. With a locked bootloader you are only able to sideload an OTA using ADB.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, that's what I did, adb sideloaded the J OTA that I downloaded from the Google Android Developers site: https://developers.google.com/android/ota . From what the OP said, that's what they did, too. And then adb sideloading the E OTA on top of that failed, since it is an earlier OTA. So I'm currently looking for a solution for getting the E update on my phone.
So you're not talking about using adb sideload, then, like the OP was? I'm totally confused, what were you suggesting to the OP that he do to be able to get the E image on a Verizon Pixel that already had the J image? I guess that I'm not following how I can do this with a locked bootloader? I'd love to get a clue how this could be done? Doesn't matter to me how much work it is, I'm open to learning about how to do this, and gathering whatever tools I would need?
It just occurred to me, were you assuming that the OP has an unlocked bootloader, then? I made the opposite assumption I guess, since they were using adb sideload in the first place
Thanks!
RogerSC said:
Yes, that's what I did, adb sideloaded the J OTA that I downloaded from the Google Android Developers site: https://developers.google.com/android/ota . And then adb sideloading the E OTA on top of that failed, since it is an earlier OTA. So I'm currently looking for a solution for getting the E update on my phone.
So you're not talking about using adb sideload, then? I'm totally confused, what were you suggesting to the OP that he do to be able to get the E image on a Verizon Pixel that already had the J image? I guess that I'm not following how I can do this with a locked bootloader? I'd love to get a clue how this could be done? Doesn't matter to me how much work it is, I'm open to learning about how to do this, and gathering whatever tools I would need?
Thanks!
Click to expand...
Click to collapse
Sideloading an OTA you use ADB, bootloader does not have to be unlocked. Flashing a full image, you use Fastboot which requires an unlocked bootloader. The beauty of having an unlocked bootloader is if you mess up it gives you the ability to flash a full image to put you back to some full stock condition.
Sent from my Pixel using XDA-Developers Legacy app
I would bet that the Verizon OTA has a later timestamp then both of the Google official images. So we should be able to flash that to fix it over E or J
The problem is I can't find a download link to the Verizon OTA anywhere at all. No one has it
Sent from my Pixel using Tapatalk
Joe92T said:
I would bet that the Verizon OTA has a later timestamp then both of the Google official images. So we should be able to flash that to fix it over E or J
The problem is I can't find a download link to the Verizon OTA anywhere at all. No one has it
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I would try it if I had a copy of it.
Sent from my Pixel using XDA-Developers Legacy app
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
Has anyone else given it a go on this phone yet? So far I think its working pretty well, with only a couple slowdowns.
Has anyone else noticed a bit of a slowdown with wifi? Sometimes I have to kick it over to LTE to login to apps, even though I can run speed tests and things.
Just wanted to see what other people were experiencing with the beta, sorry if this the wrong place for this.
Other than poor "stand by" battery drainage for me, I think it works pretty good.
But, Android Q it's not on Pixel 3A, isn't it?
Xtremeviper said:
But, Android Q it's not on Pixel 3A, isn't it?
Click to expand...
Click to collapse
Not via OTA, you can pick up the system image from the website and flash it manually though.
As to the OP, I gave it a shot for a couple days but I kept getting a bug where I'd unlock the phone and just get a black screen so I got frustrated and flashed back lol I hope the OTA thats supposedly coming next month fixes it up so it could be a daily driver.
Thanks antp121
I tried to find from official website the Android Q image for Pixel 3A and flash it via sideload or similar.
Can you help me how to do?
Xtremeviper said:
Thanks antp121
I tried to find from official website the Android Q image for Pixel 3A and flash it via sideload or similar.
Can you help me how to do?
Click to expand...
Click to collapse
You know how to use fastboot? I believe the instructions are right on the Google factory image site where you grab the beta 3 image.
Sent from my Pixel 3a using Tapatalk
Thats the point...
I can't found it on Google Factory image, the Beta 3.
Hello,
Do you know if Android Q will brings face unlock ?
Even if it's not safe as the finger print sensor
Xtremeviper said:
Thats the point...
I can't found it on Google Factory image, the Beta 3.
Click to expand...
Click to collapse
Here you go bud. They took it down.
https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
And if you need any instructions:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-install-android-q-beta-3-june-t3930217
jmtjr278 said:
You know how to use fastboot? I believe the instructions are right on the Google factory image site where you grab the beta 3 image.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
crackedvenom2 said:
Here you go bud. They took it down.
https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
And if you need any instructions:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-install-android-q-beta-3-june-t3930217
Click to expand...
Click to collapse
Many Thanks!!! I succeed!
antp121 said:
Not via OTA, you can pick up the system image from the website and flash it manually though.
As to the OP, I gave it a shot for a couple days but I kept getting a bug where I'd unlock the phone and just get a black screen so I got frustrated and flashed back lol I hope the OTA thats supposedly coming next month fixes it up so it could be a daily driver.
Click to expand...
Click to collapse
I've actually been getting the same thing. I also keep having an issue with wifi, I think I'm going go back to pie and see if it's still doing it. I just really like the new gestures and don't wanna give them up lol
I've been running it for a few weeks. Side loaded the OTA as soon as I got the phone. They took down the OTA file but it's posted in this thread. I've had no issues other than a few apps not being comparable yet and there is no working Magisk out for Pixels 3/3a with Q beta.
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
bejunk said:
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
Click to expand...
Click to collapse
Yes
sd_N said:
Yes
Click to expand...
Click to collapse
bejunk said:
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
Click to expand...
Click to collapse
On a related note, does anyone know if opting out of the Beta will delete any esim profiles?
Axe_L_Thief said:
On a related note, does anyone know if opting out of the Beta will delete any esim profiles?
Click to expand...
Click to collapse
Simply "opting out" of the beta by pressing the button on the web page will not change anything. But as soon as you (download and) install Pie, my guess is that it will erase everything including any esim profiles. When you go from one major release to another - especially a downgrade - the phone is typically going to be wiped completely. It purposefully erases all information to ensure there isn't any conflicts between the two OS versions.
Just enrolled in the beta myself, does anyone know if it is being pushed OTA yet?
Sent from my Pixel 3a using Tapatalk
upinsmoke7610 said:
Just enrolled in the beta myself, does anyone know if it is being pushed OTA yet?
Click to expand...
Click to collapse
DP4 was pulled iirc. You can still sideload it.
Anybody having any issues with it so far?
Sent from my Pixel 3a using Tapatalk
So far I'm having no issues with the beta, but did anyone else get a small update today? Any idea why?