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
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.
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.
//
This is the OTA update I received for the G5 Plus.
The phone was running a North American (retus) build OPSS28.85-17-2 (October 1, 2018 patch level) prior to the update. After the update, the phone is running OPSS28.85-17-4 (December 1, 2018 patch level).
MD5: f840a71b9a1b347b13274c668adf77a0
SHA1: fb53a9a872c8a881f4bde111aaade4f23bb7a9a4
SHA256: d20bcd877222429dfc1620c5265b91cf29b2768d8e51314ef7b8f3ee0d9bba45
File size: 73,434,767 bytes (~70MB)
https://drive.google.com/file/d/1XWbH8emmxduw_yosNJASndgxesbwrp5d/view?usp=sharing
https://www.dropbox.com/s/1tyh80849p1qdsy/potter_US_OPS28.85-17-4_patch.zip?dl=0
reserved for future use
Please help!
Hello, how do I install this update if I have TWRP? I have searched for the stock recovery and I have not had luck.
MasterDoggy said:
Hello, how do I install this update if I have TWRP? I have searched for the stock recovery and I have not had luck.
Click to expand...
Click to collapse
If you have TWRP installed I suspect you have rooted your device or tweaked it in some other way.
In this case OTA updates won't work.
You have to be on unrooted full stock firmware incl. stock recovery (can be found in the related fastboot firmware as "recovery.img").
If you are:
Transfer the file to phone’s internal storage. Go to Settings > apps Provide storage permission to Motorola Update Services app. Check for OTA updates from Settings.
The package will be automatically detected and system upgraded.
(Source: https://forum.xda-developers.com/g5...fficial-moto-g5-g5-plus-t3848246/post77748504 )
Wolfcity said:
If you have TWRP installed I suspect you have rooted your device or tweaked it in some other way.
In this case OTA updates won't work.
You have to be on unrooted full stock firmware incl. stock recovery (can be found in the related fastboot firmware as "recovery.img").
If you are:
Transfer the file to phone’s internal storage. Go to Settings > apps Provide storage permission to Motorola Update Services app. Check for OTA updates from Settings.
The package will be automatically detected and system upgraded.
(Source: https://forum.xda-developers.com/g5...fficial-moto-g5-g5-plus-t3848246/post77748504 )
Click to expand...
Click to collapse
Phone doesn't detect the update package using this method. Please suggest if the file name needs to be changed.
checksamir said:
Phone doesn't detect the update package using this method. Please suggest if the file name needs to be changed.
Click to expand...
Click to collapse
You have to ask the OP, @Amishrabbit for that. But yes, the name the file has now is wrong, it has to be named something like Blur_Version.xx.xx.xx.potter.retail.en.US .
-redacted-
Wolfcity said:
You have to ask the OP, @Amishrabbit for that. But yes, the name the file has now is wrong, it has to be named something like Blur_Version.xx.xx.xx.potter.retail.en.US .
Click to expand...
Click to collapse
Well, my initial reply closed itself without posting, so I'm trying again.
I'm a novice at this stuff. I don't know any instructions about how to install it. I do know that I extracted the URL for the update from the logcat output from the phone on a debugger, and the URL was live for about 10 minutes and now doesn't respond, so presumably it's a time-limited download.
I did rename the file, and I know it's from an official OTA source URL, so I'm pretty sure you can't install it with TWRP. I don't have TWRP installed on this phone and retrieved and installed it using the normal System Update method.
I've attached a screenshot of the phone's version numbers. I can't find a reference to the "Blur" number above on the phone's UI, but the file itself contains the following string, so this appears to be a pairing of (newer version) (older version)
Code:
Blur_Version.28.231.5.potter.retail.en.US )Blur_Version.28.211.2.potter.retail.en.US
The Blur* filenames were only for nougat OTAs, Oreo OTAs are named according to the version you are upgrading *from*.
They can't be installed using TWRP, the stock recovery is required, as is an untouched system, OEM, modem, and other partitions.
If you're rooted, just use the TWRP flashable zips, easier...
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Note that I do have the most recent retus zip there, but haven't yet updated the OP. Link for that is in the last couple of pages.
NZedPred said:
The Blur* filenames were only for nougat OTAs, Oreo OTAs are named according to the version you are upgrading *from*.
They can't be installed using TWRP, the stock recovery is required, as is an untouched system, OEM, modem, and other partitions.
If you're rooted, just use the TWRP flashable zips, easier...
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Note that I do have the most recent retus zip there, but haven't yet updated the OP. Link for that is in the last couple of pages.
Click to expand...
Click to collapse
I guess Blur version works for Oreo as well. I have used the name "Blur_Version.28.21.5.potter.retail.en.US.zip" and system detected the update immediately.
Unable to upload the screenshot due to network issues..
SujataSam said:
I guess Blur version works for Oreo as well. I have used the name "Blur_Version.28.21.5.potter.retail.en.US.zip" and system detected the update immediately.
Unable to upload the screenshot due to network issues..
Click to expand...
Click to collapse
Thanks. It worked like a charm.
february security patch maybe?
any news of February 2019 update?
ashutoshmatari said:
any news of February 2019 update?
Click to expand...
Click to collapse
Seems not. If you see only questions about it but no answers it's unlikely. But feel free to search by yourself in the known sources or use Google and if you find something: Share it.
https://support.motorola.com/in/en/solution/MS137632
here is the maintenance release note of February 2019, but actual release of update is not known.
ashutoshmatari said:
https://support.motorola.com/in/en/solution/MS137632
here is the maintenance release note of February 2019, but actual release of update is not known.
Click to expand...
Click to collapse
Just got it
I have an ota to move from 17-4 to 17-6.
https://www.dropbox.com/s/b8i3l0qgi...8.85-17-6_OTA_Package_OPSS28.85-17-4.zip?dl=0
You'll have to rename it to get it to work automatically. Unfortunately I don't know what the name would need to be. You can however sideload it through ADB. Haven't done that myself so hopefully someone can help with that too.
hopefully they will release it soon for other regions too.
ashutoshmatari said:
hopefully they will release it soon for other regions too.
Click to expand...
Click to collapse
Why shouldn't they?
I installed the October update in the settings app on my pixel 6 pro, and updated to android 13 the same way. Are both my slots on Android 13 or do I still need to flash the October OTA via adb?
w_tapper said:
I installed the October update in the settings app on my pixel 6 pro, and updated to android 13 the same way. Are both my slots on Android 13 or do I still need to flash the October OTA via adb?
Click to expand...
Click to collapse
If you mean you updated to A13 (September) via OTA through System Update in settings and then updated to October the same way, then you should have A13 on both slots.
so does that mean that the bricked thing and having to send to google has no chance of happening now?
Lughnasadh said:
If you mean you updated to A13 (September) via OTA through System Update in settings and then updated to October the same way, then you should have A13 on both slots.
Click to expand...
Click to collapse
w_tapper said:
so does that mean that the bricked thing and having to send to google has no chance of happening now?
Click to expand...
Click to collapse
If that is how you updated, then correct. Each time you update via OTA it updates to the opposite slot you are on. Since you updated twice like this, both slots should have A13 on them and you should be fine.