I am on 8.1 DP2 which is OPP6.171019.012, tried to install the official 8.1 OTA which is OPM1.171019.011 : obviously the latter is older that DP2, so now I am still on DP2.
Maybe I need to wait for the OTA for those that are on beta program?
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
skw5115 said:
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
Click to expand...
Click to collapse
I can confirm this, I have updated this way.
anyone has the OTA for those on DP2?
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Mikulec said:
I can confirm this, I have updated this way.
Click to expand...
Click to collapse
I'm assuming you already had an unlocked bootloader?
Mr Patchy Patch said:
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
Click to expand...
Click to collapse
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
oxman said:
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Click to expand...
Click to collapse
go to the website and unenroll.
imnuts said:
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Usually an OTA is made to go from one specific build to another. Which would make sense on why you can't do it that way. If you have the unlocked bootloader flashing the factory image for 8.1 can be done.
thegios said:
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Click to expand...
Click to collapse
If you have an unlocked bootloader, you can update now with the factory image. Otherwise wait until the OTA rolls or for beta users.
Sent from my Pixel 2 XL using Tapatalk
I just got the small ota to bump me from DP2 to final. So it's in the wild now. You can probably force the update at this point.
Like he said, I just got the official OTA bump yesterday to final. If you can't force it, it should come soon regardless.. This shows the December 5th patch.
hrkahn said:
I'm assuming you already had an unlocked bootloader?
Click to expand...
Click to collapse
yes
I have same problem with Nexus 5X.
Adb sideload breaks at 47%.
Now i can only wait, because i have the no-rpmb-bug.
Related
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
ttocs99 said:
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
Click to expand...
Click to collapse
Not yet. I'm on T-mobile.
mrpink10 said:
Not yet. I'm on T-mobile.
Click to expand...
Click to collapse
Same I spoke to Google support and they claim it's Al read available via ota
Haven't got it yet I bought my phone from Google.
Sent from my Nexus 5X using Tapatalk
Are you rooted? If so just get the ota from google and flash it with flashfire
jd1639 said:
Are you rooted? If so just get the ota from google and flash it with flashfire
Click to expand...
Click to collapse
Flashfire doesn't fully support Oreo yet so that's a no go, same with TWRP. ADB sideload might work.
I just flashed it this morning and had no problems.
I flashed a couple of hours ago official OTA package via ADB. No problems till now.
I took the plunge and flashed the 8.0 stock factory image the done a factory reset after to make sure and it been great ever since turned off animation and it's nippy just wish battery was about better but I'll give it a few days see if that goes
jd1639 said:
I just flashed it this morning and had no problems.
Click to expand...
Click to collapse
Did you use Flashfire?
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
jd1639 said:
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
Click to expand...
Click to collapse
Well then, I guess it's just when coming from the beta that it doesn't work. Thanks for the heads up.
ttocs99 said:
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Click to expand...
Click to collapse
Enable dev options and disable always keep mobile data on.
I just noticed that for some reason that is checked in oreo and it shouldn't be unless you are never on WIFI.
ttocs99 said:
Same I spoke to Google support and they claim it's Al read available via ota
Click to expand...
Click to collapse
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
I can confirm that jd1639's method works for people rooted with TWRP.
- download OTA (https://developers.google.com/android/ota)
- run Flashfire 60.0 (free version is OK)
- when asked "A system update has been detected", cancel
- Flash ZIP or OTA
- uncheck "restore boot and recovery images"
- press "EverRoot" and select "Inject SuperSU" and "Preserve recovery"
- Flash
- wait patiently
I tried flashing the modem FW using "Flash firmware package" on the OTA zip file. It rebooted and the screen went black for many minutes. I had to hard reset.
Can anyone confirm the 8.0 baseband? I have M8994F-2.6.39.3.03. I know that's the baseband for the 8.0 developer preview, but I wanted to make sure it was the final.
Billys20 said:
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
Click to expand...
Click to collapse
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
Nope
Sent from my Nexus 5X using Tapatalk
tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Billys20 said:
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Click to expand...
Click to collapse
6p here, downloaded ota (NOT factory), ran Tibu, ran Flashfire 7.0 pro as described and after three reboots and a while of booted finishing, was cleanly updated to 8.0.0. took < 20 min. [emoji2]
Sent from my Nexus 6P using Tapatalk
So I am a little late to the upgrade party. I have tried reading through the posts but quickly became confused. Here is what I have...
Google Store Pixel XL rooted unlocked bootloader running 7.1.2 on Sprint.
What is the easiest way to upgrade to O? Also can I upgrade without loosing everything I have right now?
Thanks for the help.
Sent from my Pixel XL using Tapatalk
I waited for OTA which was far to long after the original release
clone1008 said:
So I am a little late to the upgrade party. I have tried reading through the posts but quickly became confused. Here is what I have...
Google Store Pixel XL rooted unlocked bootloader running 7.1.2 on Sprint.
What is the easiest way to upgrade to O? Also can I upgrade without loosing everything I have right now?
Thanks for the help.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I flashed factory image from Google page: https://developers.google.com/android/images
That page also has basic instructions on how to perform the upgrade in this fashion. Alternatively, you can sideload the OTA - which is how I did all my monthly and version upgrades on Nougat. But, I figured I would start "clean" with a factory image flash for the upgrade to Oreo. I did remove the "-w" from the flashall.bat to retain data. Once the upgrade completes, you just need to reflash SuperSu and suhide and you should be good to go. The entire process took me less than 45 minutes. Detailed guides for all you need can be easily found on XDA. One important note: make sure you have the most recent version of platform tools prior to attempting the upgrade. That caused me a bit of trouble with this most recent upgrade - but was easily resolved by upgrading to the latest and greatest platform tools. (Also found on the Google site.) Good luck.
sb1893 said:
I flashed factory image from Google page: https://developers.google.com/android/images
That page also has basic instructions on how to perform the upgrade in this fashion. Alternatively, you can sideload the OTA - which is how I did all my monthly and version upgrades on Nougat. But, I figured I would start "clean" with a factory image flash for the upgrade to Oreo. I did remove the "-w" from the flashall.bat to retain data. Once the upgrade completes, you just need to reflash SuperSu and suhide and you should be good to go. The entire process took me less than 45 minutes. Detailed guides for all you need can be easily found on XDA. One important note: make sure you have the most recent version of platform tools prior to attempting the upgrade. That caused me a bit of trouble with this most recent upgrade - but was easily resolved by upgrading to the latest and greatest platform tools. (Also found on the Google site.) Good luck.
Click to expand...
Click to collapse
I don't use Android Pay. Is Suhide necessary?
Sent from my Pixel XL using Tapatalk
clone1008 said:
I don't use Android Pay. Is Suhide necessary?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
No - only if you want to keep passing SafetyNet - which affects AP, Netflix, ADT Security App, and others....but if you don't need to hide root and mask unlocked bootloader, SuperSu alone should be fine.
edit, wrong tab
Start fresh man. Take backup, flash the factory image with wipe, then restore the backup.
I went ahead and took the OTA that hit my phone. Flashed SuperUser the Suhide. All is good in the hood.
Sent from my Pixel XL using Tapatalk
clone1008 said:
I went ahead and took the OTA that hit my phone. Flashed SuperUser the Suhide. All is good in the hood.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
If phone is rooted, OTA works?
I thought if phone is rooted, updates needed to be done manually (i.e., flash). Is this not correct?
robchow said:
If phone is rooted, OTA works?
I thought if phone is rooted, updates needed to be done manually (i.e., flash). Is this not correct?
Click to expand...
Click to collapse
Think he took the ota and rooted afterwards... That what I did
galaxys said:
Think he took the ota and rooted afterwards... That what I did
Click to expand...
Click to collapse
I didn't consider this; I am still new to this whole root and updates being rooted. Good to know I am understanding what I am reading and not losing my mind due to old age
The OP stated he was rooted, then said he took OTA.
What's wrong with this picture?
I was rooted... I took the OTA and then re-rooted.
Sent from my Pixel XL using Tapatalk
clone1008 said:
I was rooted... I took the OTA and then re-rooted.
Click to expand...
Click to collapse
.
OK. Going from 7 to 8 did you do a full wipe? Since you were rooted probably would have been easier to flash factory image rather than unroot just to take OTA.
I didn't do anything but take the OTA. When that was finished everything was still on my phone. I then flashed twrp and flashed supersu and Suhide. All has been good so far.
Sent from my Pixel XL using Tapatalk
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Comet1966 said:
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Click to expand...
Click to collapse
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
piscesjoey said:
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It's like the system and recovery don't have access to the storage at all.
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Uzephi said:
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Click to expand...
Click to collapse
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Comet1966 said:
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Click to expand...
Click to collapse
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Uzephi said:
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Click to expand...
Click to collapse
I did the flashall and that's it. I have no idea what's up with it
Comet1966 said:
I did the flashall and that's it. I have no idea what's up with it
Click to expand...
Click to collapse
What is your current version? -11/November patch?
Uzephi said:
What is your current version? -11/November patch?
Click to expand...
Click to collapse
This
Comet1966 said:
This
Click to expand...
Click to collapse
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Uzephi said:
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Click to expand...
Click to collapse
I am trying that one again. Factory reset didn't help either.
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Comet1966 said:
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Click to expand...
Click to collapse
Which version of the bootloader? If the Oreo bootloader then perhaps this will result in an error.
If you installed Oreo Global or TMO after that, the bootloader will be upgraded to Oreo, perhaps this will lead to an error.
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Comet1966 said:
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Click to expand...
Click to collapse
Wow, must've been some kind of bad flash previously? Either way glad that you've finally joined the rest of us!
Sent from my Moto Z (2) using Tapatalk
is there anyway to Sideload Android P Preview on a lock Verizon Pixel 2 Xl ? I can get it to work getting errors like E:footer is wrong e:error 21 E:signatire verification failed
Thanks
https://developer.android.com/preview/download.html
Go to your recovery and flash it through adb sideload
I tried to flash it the ADB Sideload update.zip and it get to 0% and fails
You may have to enroll in Beta first in order for P to work.
There is no Beta Yet For Android P
Badwished said:
There is no Beta Yet For Android P
Click to expand...
Click to collapse
After doing some research, you have to be bootloader unlocked to flash the Android P firmware.
This is a developer preview. Next version will be Beta and then there will be an ota method.
update your adb and fastboot.
and get the OTA from here: https://developer.android.com/preview/download-ota.html
Remember if you go P on Verizon you can't go back because of the locked bootloader.
Is this still accurate? To sideload the OTA preview , any downside other than the locked bootloader?
bond32 said:
Is this still accurate? To sideload the OTA preview , any downside other than the locked bootloader?
Click to expand...
Click to collapse
You can flash the factory images through adb to go back to 8.1. I was on P and went back
franchise said:
You can flash the factory images through adb to go back to 8.1. I was on P and went back
Click to expand...
Click to collapse
Thanks! You got the OTA from here right?
https://developer.android.com/preview/download-ota
Why did you go back to O?
bond32 said:
Thanks! You got the OTA from here right?
https://developer.android.com/preview/download-ota
Click to expand...
Click to collapse
I bought my device from someone locally and it already had Android P on it. I just flashed the 8.1 images to go back. But that is the site to get the Image
franchise said:
I bought my device from someone locally and it already had Android P on it. I just flashed the 8.1 images to go back. But that is the site to get the Image
Click to expand...
Click to collapse
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
bond32 said:
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
Click to expand...
Click to collapse
Sorry to hear that. I may try it tomorrow to see if it works for me.
bond32 said:
Followed the correct procedure I think, no go. I think maybe it's because my pixel XL 2 is already on the latest Verizon OTA which is April security patch...
Click to expand...
Click to collapse
Yep, P is technically older than what you have so it won't OTA. A new P is due any day now.
//
I guess I have something to do when I get home. No update to platform tools.
https://developers.google.com/android/images
https://developers.google.com/android/ota
All seems good so far. Supposedly the charging issue is fixed...
Nothing via OTA update
Only images are available
Just get it on OTA via US IP (vpn), but update dont star
Im rooted, is't interfering??
These wouldn't allow a user to downgrade, correct? Like, to 7.1.0, use dePixel8, and then root?
Can the updates be installed out of sequence? I'm currently on the Oreo March update, can I install the May update without installing April first?
moyses said:
Nothing via OTA update
Only images are available
Just get it on OTA via US IP (vpn), but update dont star
Im rooted, is't interfering??
Click to expand...
Click to collapse
if you're rooted, then the ota won't apply via the google system update. your rom has to be completely stock in order for it to work. your bootloader can be unlocked. i don't know about flashing the ota via twrp. i've never done it.
Bramton1 said:
These wouldn't allow a user to downgrade, correct? Like, to 7.1.0, use dePixel8, and then root?
Click to expand...
Click to collapse
correct, they will not allow a user to downgrade. there isn't a downgrade method available for locked bootloaders.
Gulfstream 650 said:
Can the updates be installed out of sequence? I'm currently on the Oreo March update, can I install the May update without installing April first?
Click to expand...
Click to collapse
if you flash the full factory image, yes, you can flash the may update over the march update. i don't know about the otas though. i always flash the full factory image.
Does anyone know if I can flash the OTA on my nonrooted Pixel XL through TWRP ?