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
Related
So basically, after I rooted, I was stuck in a bootloop at the "warning: bootloader unlocked" screen when I tried to boot, so I tried "factory reset" with the same result. Then I DL'd the stock xt1250 firmware and the update back to 5.0.2 (which the phone had before I F'd it up), but TWRP won't install either of them.
I can access the bootloader, and TWRP recovery, but any other option from the bootloader, or restarting results back in the "warning: bootleader unlocked" screen loop
I've seen a few places on here that there is a Brazilian version of 6.0.1 that it TWRP-able, but living in the U.S.of.A. and not being able to speak Portuguese, I was wondering if that would work for me?
thanks,
N.K.
Actually, I just tried copying the Brazilian 6.0.1 onto the phone and I got an error that "the file is larger than the device limit", so I guess that option's out!
I feel horrible right now! I just got this awesome phone, and broke it within 2 days
I really hope someone can help!
Status Update:
-I downloaded a bunch of zips... American xt1250 4.4.4 and conversion to 5.0.2 (which the phone is), Brazilian xt1225 5.0.2 and 6.0.1
-I tried RSD because twrp was obviously doing nothing.
-I ended up getting one to work, which was the Brazilian 5.0.2 with some files from another one (I forgot which, but I think the American 5.0.2 conversion) because is was lacking some key components (which it seems they all were).
-none of the others worked at all
-I have yet to test my sim card in it, but...
Problem:
-I got my phone up and running, but now the wifi wont turn on. It says "turning on wifi..." but nothing ever happens. I looked it up and found lots of stuff about wifi and bluetooth not turning on, but my bluetooth seems to turn on as it should.
Aright... I installed Bliss Rom, and it all works! The camera sucks compared to the stock camera, but I can live with that. Thanks for the help everyone! :good: :good: :good:
albinoethiopian3 said:
I've seen a few places on here that there is a Brazilian version of 6.0.1 that it TWRP-able, but living in the U.S.of.A. and not being able to speak Portuguese, I was wondering if that would work for me?
Click to expand...
Click to collapse
The TWRP-flashable 6.0.1 ROM was made by a Verizon user who lives in the U.S. It works for ALL Quarks. It doesn't matter what language you speak, you choose the language you want at the bootup screen. Just like every other version of Android.
albinoethiopian3 said:
Actually, I just tried copying the Brazilian 6.0.1 onto the phone and I got an error that "the file is larger than the device limit", so I guess that option's out!
I feel horrible right now! I just got this awesome phone, and broke it within 2 days
I really hope someone can help!
Click to expand...
Click to collapse
Tons of people are using that TWRP-flashable ROM. You have 64GB storage space unless you've used it all up. So, there's no reason you shouldn't be able to transfer that file and flash it.
albinoethiopian3 said:
Status Update:
-I downloaded a bunch of zips... American xt1250 4.4.4 and conversion to 5.0.2 (which the phone is), Brazilian xt1225 5.0.2 and 6.0.1
-I tried RSD because twrp was obviously doing nothing.
-I ended up getting one to work, which was the Brazilian 5.0.2 with some files from another one (I forgot which, but I think the American 5.0.2 conversion) because is was lacking some key components (which it seems they all were).
-none of the others worked at all
-I have yet to test my sim card in it, but...
Problem:
-I got my phone up and running, but now the wifi wont turn on. It says "turning on wifi..." but nothing ever happens. I looked it up and found lots of stuff about wifi and bluetooth not turning on, but my bluetooth seems to turn on as it should.
Click to expand...
Click to collapse
Glad you got it running! However, in the future don't just download and flash anything. Brazilian 5.0.2 won't work because it's not made for your phone (U.S. Moto Maxx XT1250), and the radio/modem won't work. The Brazilian TWRP flashable 6.0.1 file works in part because @iiWoodstocK used custom @bhb27 kernel to make it compatible. It's stock Motorola Marshmallow ROM otherwise. So, that one was OK, but just flashing XT1225 firmware for your XT1250 is not wise.
Also, you can't downgrade bootloaders, so be careful when flashing different versions of software. You can downgrade from MM to Lollipop or even Kitkat, but you have to leave out gpt.bin.
It seemed you were just flashing a lot of stuff, so be careful.
albinoethiopian3 said:
Aright... I installed Bliss Rom, and it all works! The camera sucks compared to the stock camera, but I can live with that. Thanks for the help everyone! :good: :good: :good:
Click to expand...
Click to collapse
You can change the camera. There's stock Moto Camera files in this forum you can flash. This is from the Bliss ROM thread:
kitcostantino said:
^^ agreed. great ROM. as far as camera quality, that is just the stock CM camera. idk why. i never use it for that reason. there are a few "moto canera and gallery" flash able zip files on androidfilehost.com and mega. or you can try to install them from Play store. the moto ones are better in that aspect. the htc 10 camera works okay as do several others. find a replacement that works for you.
Click to expand...
Click to collapse
kitcostantino said:
the moto one works fine for me. i couldn't find the link i got it from, so i just uploaded it to mega. (where i got it from in the first place. ) https://mega.nz/#!ChsyQZSC!ULtLteziJ__n7GOt_XmlSvaFz_tf68u0RvEDsNq4NAs
Catch and release. lol
Click to expand...
Click to collapse
Hello all here is my situation, was running cf's Rom and backed up in twrp backed up all available options using mod 04 version of twrp.
Flashed the newest cm 13 for a day then this morning wiped and tried to restore my backup of cf's Rom all goes well until it's about done then then in red letters it says no modem installed system busy. My phone is a 1254 any assistance with this would be greatly appreciated.
Sent from my HTC6500LVW using XDA-Developers mobile app
Steve One said:
Hello all here is my situation, was running cf's Rom and backed up in twrp backed up all available options using mod 04 version of twrp.
Flashed the newest cm 13 for a day then this morning wiped and tried to restore my backup of cf's Rom all goes well until it's about done then then in red letters it says no modem installed system busy. My phone is a 1254 any assistance with this would be greatly appreciated.
Click to expand...
Click to collapse
Try reflashing the modem/radio in ADB. Not restoring in TWRP, but actually flashing the XT1254 radio again.
ChazzMatt said:
Try reflashing the modem/radio in ADB. Not restoring in TWRP, but actually flashing the XT1254 radio again.
Click to expand...
Click to collapse
Have no computer to do with.
Sent from my HTC6500LVW using XDA-Developers mobile app
Steve One said:
Have no computer to do with.
Sent from my HTC6500LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
there's also a TWRP flashable version
ChazzMatt said:
there's also a TWRP flashable version
Click to expand...
Click to collapse
Thank you so much for your help ChazzMatt sir I don't suppose you could give me a link or pm me with a possible download kind sir, would this be a image file to flash like flashing twrp?
Sent from my HTC6500LVW using XDA-Developers mobile app
Steve One said:
Thank you so much for your help ChazzMatt sir I don't suppose you could give me a link or pm me with a possible download kind sir, would this be a image file to flash like flashing twrp?
Sent from my HTC6500LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
There's fastboot and TWRP flashable in that first post. Read carefully.
ChazzMatt said:
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
There's fastboot and TWRP flashable in that first post. Read carefully.
Click to expand...
Click to collapse
Does one flash as an image file?
Sent from my HTC6500LVW using XDA-Developers mobile app
Steve One said:
Does one flash as an image file?
Sent from my HTC6500LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
In TWRP it's just a zipped file for the radio.
ChazzMatt said:
In TWRP it's just a zipped file for the radio.
Click to expand...
Click to collapse
Apparently twrp was hung up,just got back home from apple orchard played around in twrp and was able to flash a ROM again. Seriously thinking of flashing back to twrp mod 2.
Sent from my DROID Turbo using XDA-Developers mobile app
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
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
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
Have a major issue. lyft driver app will not work on the pixel 2 with Pie if you do a fresh install. it only works if you do an upgrade.
No clue what causes it, don't really care.
I need to roll back to oreo immediately but when I try to use adb to do the full ota oreo update and it errors out and says "update package is older than the current build.....downgrade not allowed"
Can anyone assist?
Have you try this
https://android.gadgethacks.com/how-to/downgrade-from-android-9-0-pie-back-oreo-your-pixel-0183424/
Sent from my Pixel 2 using Tapatalk
Voloshvett said:
Have you try this
https://android.gadgethacks.com/how-to/downgrade-from-android-9-0-pie-back-oreo-your-pixel-0183424/
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I presume that the bootloader is locked and thus there is no way to roll back. If it's bl unlocked then he can always flash an older factory image but not an OTA.