December images for Android 8.1 Oreo
Official factory images
Official full OTA images
Build OPM1.171019.011 - non-operator-specific
This is not marlin...
Great to see your high quality information and Link's! Kudos
The verizon one is only for phones bought from verizon, right? Not for everyone on verizon even if you bought the nonspecific version of the phone?
December 8.1 images are up.
Kisakuku said:
December images for Android 8.1 Oreo
Official factory images
Official full OTA images
Build OPM1.171019.011 - non-operator-specific
Click to expand...
Click to collapse
Do I need to opt out of beta in order to get this ota?
swooperstar said:
The verizon one is only for phones bought from verizon, right? Not for everyone on verizon even if you bought the nonspecific version of the phone?
Click to expand...
Click to collapse
No. The Verizon update is for the unlocked Google store phone. Only use that one if you're on Verizon. The only difference is a different radio image that is presumably optimized for Verizon's network.
With this update my phone has reached puberty. The TTS voice is a fair bit deeper for some reason.
I want to try OTA! Will I lose my root by magisk?
Cannot update my unlocked Taimen with the official 8.1 OTA over the DP2, sideload says it's older than the current one...anyone else? I wouldn't do this otherwise but it's been 2 days since the official roll out and still no OTA via update.
drfroz said:
Cannot update my unlocked Taimen with the official 8.1 OTA over the DP2, sideload says it's older than the current one...anyone else? I wouldn't do this otherwise but it's been 2 days since the official roll out and still no OTA via update.
Click to expand...
Click to collapse
You cannot sideload OTA on DP2, only full factory image...or wait until Google sends you an OTA that will work.
Related
As Verizon users know a new OTA was pushed yesterday 02/16/17 the update is safe to take if you have a unlocked bootloader you will need to reflash TWRP and root you will lose both after updating
Haven't seen a new OTA on Verizon.
@Shiftydogit, build no. anything?
I'm guessing it is not showing on anyone who manually upgraded with the latest Google OTA files. Not sure about the regular Google update files, but probably checks the system version ether way for 7.1.1, NOF26V and the latest (February) security version.
sliding_billy said:
I'm guessing it is not showing on anyone who manually upgraded with the latest Google OTA files. Not sure about the regular Google update files, but probably checks the system version ether way for 7.1.1, NOF26V and the latest (February) security version.
Click to expand...
Click to collapse
Its all determined by the IMEI and ICCID. The images from Google and VZW are now identical. I got the OTA push and Im on the latest Google OTAs. They simply don't roll out OTAs to everyone at the same time .
Newer than February security patch 7.1.1 NOF26V? What's the build number? I'm 100% stock on NOF26V and can't pull an OTA at this time.
Shiftydogit said:
As Verizon users know a new OTA was pushed yesterday 02/16/17 the update is safe to take if you have a unlocked bootloader you will need to reflash TWRP and root you will lose both after updating
Click to expand...
Click to collapse
Have you rerooted? Idk if I have much reason to, since I rooted mostly for tethering, but I'm curious about the reliability in that
Soccerdude588 said:
Have you rerooted? Idk if I have much reason to, since I rooted mostly for tethering, but I'm curious about the reliability in that
Click to expand...
Click to collapse
Not at the moment been to lazy to reflash TWRP lol
farfromovin said:
Newer than February security patch 7.1.1 NOF26V? What's the build number? I'm 100% stock on NOF26V and can't pull an OTA at this time.
Click to expand...
Click to collapse
NOF26V is the newest OTA. NOF26W is for Rogers. NOF26V was pushed a few weeks ago and includes the February Security patches. I'm assuming those getting it on 2/17 were either late, or part of the 7.1.2 beta program.
Hi guys,
I have received an OTA update for android nougat. I was rooted and have xposed framework. So I have flashed stock firmware so that system status is changed to Official. I have received OTA updates after flashing till January 2017 security patch. After this update, even if i manually check for update, it just says "Your device's software is up to date".
Not able to get OTA for nougat when everyone else in India are receiving it. I received update for the same device when I had root and Xposed. Please help. Currently I'm on stock firmware without root & xposed.
Update:
Received the OTA update again. sharing the link here. Just extracted it from /data partition. Its unmodified.
Nougat OTA Link: https://drive.google.com/file/d/0B6DJKZBTXr7MNGlmUmtmLVJ4aUk/view?usp=sharing
same issue with me, I received update of security patch 1 january 2017, now it says up to date, installed stock in last week. anyone help :__:
May be we'll get it in a couple of days!
Sudarshan Q700S said:
same issue with me, I received update of security patch 1 january 2017, now it says up to date, installed stock in last week. anyone help :__:
Click to expand...
Click to collapse
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Lord of Hell said:
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Click to expand...
Click to collapse
I havent downloaded it once even. I still don't get the update. Complete stock since purchase. No modding done
swaggy123 said:
I havent downloaded it once even. I still don't get the update. Complete stock since purchase. No modding done
Click to expand...
Click to collapse
I have downloaded it once, but not able to find it in the cache partition. Then flashed stock firmware and no more update notification for Nougat. Even I'm wondering what really is happening.
Maybe Motorola might be pushing the update randomly. I see that many others are reporting the same issue at XDA. I hope we would get the update in a couple of days.
Lord of Hell said:
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Click to expand...
Click to collapse
Sure I'll tell you if i got it
Can you got update notification
Yes, I did get an update notification
nitingarje24 said:
Can you got update notification
Click to expand...
Click to collapse
I have downloaded it and its around 764MB. I have flashed the stock firmware and tried to update it, but my device got updates till Jan 2017 security patch only, nougat update didn't appear second time! Still waiting for the update
Lord of Hell said:
I have downloaded it and its around 764MB. I have flashed the stock firmware and tried to update it, but my device got updates till Jan 2017 security patch only, nougat update didn't appear second time! Still waiting for the update
Click to expand...
Click to collapse
Hey,
I did the same. I used RR ROM almost a month than re-flashed the stock one.
I got the 7.1.1.
What is the build number?
when you got 7.1.1
[email protected] said:
Hey,
I did the same. I used RR ROM almost a month than re-flashed the stock one.
I got the 7.1.1.
What is the build number?
Click to expand...
Click to collapse
These are the current stock ROM details.
Lord of Hell said:
These are the current stock ROM details.
Click to expand...
Click to collapse
Seems you are using the right version of marshmallow.
What i did was:-
1. Downloaded the ROM from https://github.com/motoxplay/stock. Indian version 5.1.1 (XT1562).
2. Flashed it.
3. Now the ROM was automatically updated to 6.0.1 then 7.1.1.
Just try to download and flash the ROM from here. https://github.com/motoxplay/stock
after flashing 5.1.1 it said device up to date.not working now its Lollipop.
tell me when you got nougat update because after 4 oct 2017 didn't get notification of ota
Tried it few days back, didn't work!
[email protected] said:
Seems you are using the right version of marshmallow.
What i did was:-
1. Downloaded the ROM from https://github.com/motoxplay/stock. Indian version 5.1.1 (XT1562).
2. Flashed it.
3. Now the ROM was automatically updated to 6.0.1 then 7.1.1.
Just try to download and flash the ROM from here. https://github.com/motoxplay/stock
Click to expand...
Click to collapse
I have already tried this method. Flashed Indian Official Lollipop firmware and it received OTA updates till Jan 2017 security patch. No more update after that! When did you receive the notification?
I think Motorola has rolled back the OTA due to battery drain and other issues few people reported. Fingers crossed!
when you got nougat update please provide date if you remember
4th Oct
nitingarje24 said:
when you got nougat update please provide date if you remember
Click to expand...
Click to collapse
I got the update on 4th Oct. Tried it again on 5th, it disappeared!
When did you get the update?
Lord of Hell said:
I have already tried this method. Flashed Indian Official Lollipop firmware and it received OTA updates till Jan 2017 security patch. No more update after that! When did you receive the notification?
I think Motorola has rolled back the OTA due to battery drain and other issues few people reported. Fingers crossed!
Click to expand...
Click to collapse
May be they rolled back the update due to issues.
I got the update on 3rd October 2017.
I don't have any issues but yes Nougat battery is not as much effective than MM.
But its not draining like other people reporting.
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
nitingarje24 said:
after flashing 5.1.1 it said device up to date.not working now its Lollipop.
tell me when you got nougat update because after 4 oct 2017 didn't get notification of ota
Click to expand...
Click to collapse
Kindly select based on region.
Updates will come based on combination of country & IEMI number.
If you are not from India and flashed the Indian version then it don't update further.
So make sure while flashing the ROM.
After flash check, should have stock recovery and ROM than only you will get the same.
Guys! I have received the OTA update today again. Not sure where to capture the OTA. Last time I didn't find it in Cache partition. This time I was able to pull the OTA zip file from data partition. Will upload it this evening if anyone wants the OTA zip file.
yes
thanks
Bought an unlocked S8 from Samsung I use AT&T for service. I wouldn't be opposed to flashing/odin'ing AT&T firmware. Currently on build NRD90M.G950U1UEU1AQH3 and the August 1st security patch. I'm unsure of the best path to get to an AT&T firmware.
Go to the att section. Find the qf7 firmware and flash it with Odin.
Go to the adb update from server thread. Download all the firmwares (starting with qf7 to whatever it is) and put them on your external storage. While on qf7 reboot into recovery and select install update from storage. Flash each one, after the last one wipe data/factory reset and reboot.
So to be clear, flash AQF7 in Odin. This will get me onto an AT&T specific SM-G950U (<-- Not U1) ROM that I can then sideload the updates onto? Is sideloading the ADB updates just to speed things up vs waiting for OTAs once I'm on the correct ROM?
I flashed my at&t version to AHQ3 thinking I would be getting faster support. I am also surprised that the Unlocked AHQ3 is still on the August security patch. I really expected this version to get patched much faster or am I missing something?
msk said:
I flashed my at&t version to AHQ3 thinking I would be getting faster support. I am also surprised that the Unlocked AHQ3 is still on the August security patch. I really expected this version to get patched much faster or am I missing something?
Click to expand...
Click to collapse
The US unlocked version is the red headed stepchild of the S8 world, it really is slower for updates.
I am running AQK3 on an ATT version, think I got it from sammobile, just got one I think it was the VZW version but don't remember, didn't change the AT&T bloatware... since I did not pawn/root it in my current setup. Patch level is oct not nov...
You should have received the November security patch update last night or should be getting it sooner than later. If anything try running the manual software update on WiFi when you get a chance.
I just bought an unlocked AT&T Galaxy S7 to use on another carrier. Because I'm not on AT&T, I don't get OTA updates. I sideloaded the QA6 update which brought the device up to Android 7.0. However, I noticed there are like 8 OTA updates that at&t pushed out. I would like to be able to get onto the latest update which was released a couple weeks back, but the idea of sideloading that many updates is discouraging. Are there some updates I can skip? Thank you.
enjoymoosic said:
I just bought an unlocked AT&T Galaxy S7 to use on another carrier. Because I'm not on AT&T, I don't get OTA updates. I sideloaded the QA6 update which brought the device up to Android 7.0. However, I noticed there are like 8 OTA updates that at&t pushed out. I would like to be able to get onto the latest update which was released a couple weeks back, but the idea of sideloading that many updates is discouraging. Are there some updates I can skip? Thank you.
Click to expand...
Click to collapse
You can Odin flash QE1 from this thread then the five ota updates to get to the latest firmware: https://forum.xda-developers.com/att-galaxy-s7/how-to/ota-update-ss-g930aucs4bqj2-to-u4bqk2-t3716713
I was on Oreo 85.13 pre-release...then I unlocked bootloader...and installed pixel experience...but meanwhile I formatted all data which ihave backed up..then I installed twrp flashable with June security patch zip..and I was on Android 7..then I flashed pixel experience..now..if I want to back on Oreo stock and to lock bootloader..what should I have To do...???I heard somewhere you need stock Oreo ROM zip where I can find one...???is that same one which we have used in manually updating to Oreo... please reply...
As far as I know the only stock Oreo zip we have is the OTA, which can't be used to flash firmware. We need the full firmware file before we're able to flash stock ROMs via fastboot.
Anyway, I'm also curious if there are any differences for the unlocking/flashing/backup process starting at the official Oreo we have now, and if going back to it later is the same as it is with Nougat.
The stock US OTA update can be found here: https://technoplanners.blogspot.com...tock-update-for-moto-g5-plus-OPS28.85-13.html
This can be side-loaded to upgrade after you've flashed Nougat with one caveat. Nougat has to be at Build number NPNS25.137-92. If your Nougat ROM has the June security patches (Build number NPNS25.137-93) you'll be SOL since the manifest specifies the pre-req for the update. So the fools at Motorola released the June update for Nougat, then released Oreo at the same security patch level and won't let you apply the update. Real geniuses.
nvrpayretail said:
The stock OTA update can be found here: https://technoplanners.blogspot.com...tock-update-for-moto-g5-plus-OPS28.85-13.html
This can be side-loaded to upgrade after you've flashed Nougat with one caveat. Nougat has to be at Build number NPNS25.137-92. If your Nougat ROM has the June security patches (Build number NPNS25.137-93) you'll be SOL since the manifest specifies the pre-req for the update. So the fools at Motorola released the June update for Nougat, then released Oreo at the same security patch level and won't let you apply the update. Real geniuses.
Click to expand...
Click to collapse
That's not quite correct; the build required for this Oreo OTA that's currently around is NPNS25.137-92-14 (June 2018 security patch for Brazil and Indian devices). The NPNS25.137-93-14 patch you mentioned is the June 2018 patch for EU, US and Asian devices, which means the Oreo patch for those devices isn't around yet.
To the opening poster, as previously mentioned, you will have to wait for the OPS28.85-13 stock fastboot ROM to be leaked. You must lock with a stock firmware as new or newer than your current bootloader. You cannot downgrade bootloaders via fastboot anyway and it's really not recommended to downgrade.
The US patch is available (Blur_Version.28.51.16.potter.retail.en.US.zip). It can be downloaded from the link I provided.
Correction: My bad. Didn't realize "92" indicated India and "93" indicated US. Evidently the referenced download is labeled wrong