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.
Related
Hi all.
I just noticed there's new firmware. Has anyone updated yet? In using an XT1572.
I'm rooted etc... So I can't quite simply update.
Should I be flashing the last stock firmware i have and then update? The last fastboot I have is the February patch, but my phone is on the May patch. Whatever firmware i flashed gives me another language in the update notification screen...lol.
Any guidance would be appreciated. Otherwise, I'll just do my thing blindly.
d.casper.b said:
Hi all.
I just noticed there's new firmware. Has anyone updated yet? In using an XT1572.
I'm rooted etc... So I can't quite simply update.
Should I be flashing the last stock firmware i have and then update? The last fastboot I have is the February patch, but my phone is on the May patch. Whatever firmware i flashed gives me another language in the update notification screen...lol.
Any guidance would be appreciated. Otherwise, I'll just do my thing blindly.
Click to expand...
Click to collapse
After your post, I rechecked the update service on my phone (xt1572 also). I got also new update here, but right now I cant do update (rooted + xposed). WIll try later, but I suppose that there is just new security patch. Strange that I got another version..
EDIT:
fount out Motowebpage
it look like the only improvements are - September security patch there.
Is the update for India dual sim xt1572?
I've installed the update today. The download size was about 40 MB, so seems to be a small patch indeed. I can confirm that it contains the september security patch, haven't noticed anything else yet.
I do think it's a shame that Moto is lacking so much in the update department lately. This is a security patch of two months ago... Also I would have expected them to have news on Nougat by now, at least for their Moto Z family...
6.0.1 ? at the time of 7.0?
BooBzi said:
After your post, I rechecked the update service on my phone (xt1572 also). I got also new update here, but right now I cant do update (rooted + xposed). WIll try later, but I suppose that there is just new security patch. Strange that I got another version..
EDIT:
fount out Motowebpage
it look like the only improvements are - September security patch there.
Click to expand...
Click to collapse
makarand1881 said:
6.0.1 ? at the time of 7.0?
Click to expand...
Click to collapse
it's not 6.0.1 update it's only security patch, we already had 6.0.1 in eu for a while
Has someone already tried the update with Flashfire? Im Rooted, on Frankenclark and Xposed. Does anyone know if we can get a flashable zip to flash in TWRP? To much work to go back to Stock, update and install everything again. Is the patch it worth?
Sent from my XT1572 using XDA-Developers mobile app
can someone upload full firmware for retasia? thx
We have to wait for Moto to release/leak the firmware image, the OTA zip won't do any good... This usually takes 2-4 weeks, sometimes more, to get the factory image. Be patient.
BTW, it is nothing special, all it does is patch to the Sept 1, 2016, security update, including Dirty Cow (which if you have been following the security threads is pretty much worthless on Lollipop and newer devices anyway)
aakashverma0007 said:
Is the update for India dual sim xt1572?
Click to expand...
Click to collapse
India bro?
we will get it by next week and i hope volte support for jio also is gonna be fix in this upcoming build
What's your source?
Since 7.0 came to the s7, I have been keeping up with the monthly updates the carriers push out but for the past couple of months I've been getting some terrible kernel wake locks and I've tried everything possible to prevent them but I can't find a solution. So my thought was downgrading to an earlier 7.0 where I didn't have that problem.
Now my question is: Has the bootloader been updated prior to the first 7.0 monthly update (march)? Because I've heard once the bootloader has been updated you can't go downgrade to an earlier bootloader and I've experienced a soft brick on my s7 edge while tried to downgrade to an earlier version of marshmallow and someone told me it was because of an update to the bootloader. The firmware i'm on now is G935W8VLU2BQH1 and I want to go down to G935W8VLU2BQB6 which is the first nougat update (march)
orlans21 said:
Since 7.0 came to the s7, I have been keeping up with the monthly updates the carriers push out but for the past couple of months I've been getting some terrible kernel wake locks and I've tried everything possible to prevent them but I can't find a solution. So my thought was downgrading to an earlier 7.0 where I didn't have that problem.
Now my question is: Has the bootloader been updated prior to the first 7.0 monthly update (march)? Because I've heard once the bootloader has been updated you can't go downgrade to an earlier bootloader and I've experienced a soft brick on my s7 edge while tried to downgrade to an earlier version of marshmallow and someone told me it was because of an update to the bootloader. The firmware i'm on now is G935W8VLU2BQH1 and I want to go down to G935W8VLU2BQB6 which is the first nougat update (march)
Click to expand...
Click to collapse
Just download rom from sammobile, you will have all the files for downgrading.
MS420 said:
Just download rom from sammobile, you will have all the files for downgrading.
Click to expand...
Click to collapse
I did that back in December while on 6.0.1 and odin failed then when rebooting I got a software error message
orlans21 said:
I did that back in December while on 6.0.1 and odin failed then when rebooting I got a software error message
Click to expand...
Click to collapse
Well, I downgraded from 7.0 to 6.0 but with twrp, so maybe it's not possible via odin, but I flashed many times nougat via odin, from april to february security patch, it always worked..
MS420 said:
Well, I downgraded from 7.0 to 6.0 but with twrp, so maybe it's not possible via odin, but I flashed many times nougat via odin, from april to february security patch, it always worked..
Click to expand...
Click to collapse
So then it's possible. As long as Samsung didn't update the bootloader between March and August then I should be good. Did you include BL in Odin when you downgraded to an earlier security patch?
orlans21 said:
So then it's possible. As long as Samsung didn't update the bootloader between March and August then I should be good. Did you include BL in Odin when you downgraded to an earlier security patch?
Click to expand...
Click to collapse
Yes.
MS420 said:
Yes.
Click to expand...
Click to collapse
Then they haven't updated it so far. When I wanted to go from 6.0.1 November security patch back to February security patch it failed and the phone went into a softbrick
orlans21 said:
Then they haven't updated it so far. When I wanted to go from 6.0.1 November security patch back to February security patch it failed and the phone went into a softbrick
Click to expand...
Click to collapse
Well, if you have custom recovery, you can downgrade to 6.0.1 very easy..
MS420 said:
Well, if you have custom recovery, you can downgrade to 6.0.1 very easy..
Click to expand...
Click to collapse
I've chosen not to root this phone so I just have stock recovery
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
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.
Few mins ago Moto pushed February security patch for RETBR.
Download it here:
https://motoota.lolinet.com/index.p....26.241.15.addison.retail.en.US&carrier=retbr
You need to be on build NPNS26.118-22-2-12 to flash this update!
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
Just the security patch. Although islt coincided with the Oreo update in China. Let's hope that's in preparation for retbr Oreo.
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
I presume they will push Oreo in few hours.
rafikowy said:
I presume they will push Oreo in few hours.
Click to expand...
Click to collapse
That will be great. Even though I'll wait for a .xml.zip, on the one hand I accidentally did a downgrade (and I have no idea of the bootloader of September and December patch are different enough to cause bricking with OTAs) and I think my phone is due for a factory reset. It reboots very randomly and even though battery life is great I'm told it should be even better. Let's see if that does the fix
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
8cpaiw said:
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
Click to expand...
Click to collapse
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Artim_96 said:
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Click to expand...
Click to collapse
Hahahah true, but I'm still hoping for the best outcome
Already available for RETIN and RETUS. I'm guessing this is the last nougat patch, hopefully Oreo is next
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
You are 100% right :good:
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
If I'm reading the info in fastboot correctly, the Feb update does include an updated bootloader:
C1.14 (sha-a62b7ae, 2018-02-21 16:09:43)
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
SherlockDk said:
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
Click to expand...
Click to collapse
If the blankflashes in the other thread don't work, then you may either:
1)Have to wait for a newer blankflash to get leaked. These are Motorola internal development tools and as such aren't generally available - as they're also signed by Motorola, we may not be able to make them ourselves. The ones we have either came with the factory stock ROM or a leak from a generous Motorola engineer. You may be lucky and a blankflash may be included if an Oreo factory stock ROM comes out (not the usual fastboot ROM, a full factory image).
2)Have to pay to have your motherboard replaced, which seems to be 60-70% of the cost of a new device as far as I understand, so you may wish to put that money towards a new device instead.
I'm sorry I don't have better news, hard bricks are very difficult to resolve without the proper tools. You may wish to research making a loader image (a partition level copy of a working device, loaded onto an SD card), but it's not a definite rescue method.
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
fernseher said:
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
Click to expand...
Click to collapse
You will stay on RETEU. The link I provided is RETAIL version.
Hey can i use these files for my guide? This save me some time
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Bad url
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
If you still have that file, please upload it to androidfilehost or somewhere.