Hi there
I've had my nexus 6p pretty much from launch here in the uk.
I have never received a OTA to the point i flashed MDB08L around a few week back. Did me flashing MDB08L break my OTA? I'm still on stock everything and flash the stock image from the google site. Or am i in the same boat as everyone else?
Thanks.
If you flashed the full OEM and have not rooted then you should get OTA's. They do get rolled out over time, not everyone gets them at exactly the same time. No idea if M (November patch) should be with everyone yet though.
Flashing the factory image did not hamper your ability to get OTA updates.
Rooting does NOT impact receiving OTA updates, it only prevents them from installing (until you restore the system /boot/recovery partitions).
It is believed that only phones in Korea will receive MDB08M. Everyone else is still on L.
Related
I have a SM-N910F, bought it from Clove back in November just after my old nexus 5 got lolipop, and not received an OTA lollipop upgrade yet. It's a european version as far as I know.
I don't want to get into flashing etc. Should I expect to get an OTA upgrade at any time? Or will I be stuck on KK until I bite the bullet and flash it?
You'll receive it. Not yet released for your particular build.
As posted here: https://community.republicwireless.com/blogs/republic/2015/11/23/device-mr-progress-update-112315, it appears that RW is going to be rolling out Lollipop this week, starting Monday and finishing Wednesday.
I plan on using Sunshine before the update, as TowelPieRoot likely won't be compatible. At the very least, unlocking the bootloader will allow downgrading back to KitKat if Lollipop has some serious issues.
Sadly, the update as of December 8th says the update's been delayed AGAIN-- the soak test starts January 11th, the general roll out begins January 18th.
https://community.republicwireless.com/blogs/republic/2015/12/08/device-mr-progress-report-120815
Has anybody been able to capture the RW 5.1 OTA?
I did something stupid with my phone after updating to 5.1, then had to downgrade to 4.4.4 (I have an unlocked boot loader), but parts of it will not downgrade.
Now the motorola update thinks I am already on 5.1 and will not download the 5.1 OTA again.
mercrapper said:
Has anybody been able to capture the RW 5.1 OTA?
I did something stupid with my phone after updating to 5.1, then had to downgrade to 4.4.4 (I have an unlocked boot loader), but parts of it will not downgrade.
Now the motorola update thinks I am already on 5.1 and will not download the 5.1 OTA again.
Click to expand...
Click to collapse
The OTA can be found in the first comment here.
Thanks. I was hoping for the release version, but I guess the SOAK Test will have to do.
bparent86 said:
The OTA can be found in the first comment here.
Click to expand...
Click to collapse
It's the exact same file as the final release.
OTA update zip
Does anyone else have the OTA update zip? Maybe final release? I know you said it's the same file, but maybe it's slightly different? Because it won't work for me. BUT I was able to just take and install the EMR update. So I don't know why Motorola update won't give me 5.1 too? Is it something with the phone reporting Sprint keys instead of Republic Wireless keys, like mentioned in the Reddit post? Or they think I have it already? I just get an "aborted" message. I have no system mods and I went back to stock recovery. It worked for the EMR update, so I can't figure out the problem. Any ideas? If hoping to not have to factory reset or install 5.1 from scratch (if it's available). Thanks!
PackerDroid said:
Does anyone else have the OTA update zip? Maybe final release? I know you said it's the same file, but maybe it's slightly different? Because it won't work for me. BUT I was able to just take and install the EMR update. So I don't know why Motorola update won't give me 5.1 too? Is it something with the phone reporting Sprint keys instead of Republic Wireless keys, like mentioned in the Reddit post? Or they think I have it already? I just get an "aborted" message. I have no system mods and I went back to stock recovery. It worked for the EMR update, so I can't figure out the problem. Any ideas? If hoping to not have to factory reset or install 5.1 from scratch (if it's available). Thanks!
Click to expand...
Click to collapse
Like I said, the soak test OTA is the *exact* same file as the final update. They wouldn't make changes to the build that got soaked or they'd have to redo the entire certification process again. That said, your issue is probably the Sprint keys issue. I know you don't want to do a factory reset, but you'll probably need to flash the RW 5.1 .sbf factory image to get yourself on the new update with everything sorted out.
The sbf file is here: http://www.filefactory.com/file/27kl2ef9ngk7/XT1049_GHOST_REPW_5.1_LPA23.12-39-R-15_cid6_CFC.xml.zip
Thanks!
Hey guys i have question. I am currently on 24.11.18.lux.reteu.reteu.en.En reteu. I flashed this with a link that was posted on here before the update for 6.0 came to my country. The update that came OTA was 24.41.33 (with the januari patch). I never received this and am wondering if i will still get updates in the future or if I have to keep doing this myself. I am not rooted or anything. I just updated with the link that was posted here. http://forum.xda-developers.com/moto-x-play/help/marshmallow-ota-uk-t3277756/post64971862#post64971862
So basically:
I flashed from 5.1.1 to 6.0 myself with link posted here through recovery mode.
I now have 24.11.18. (december patch)
Others in my country that just waited have 24.41.33. (januari patch)
What do I do now in order to get updates? Wait and it will come? Or do i have to keep updating myself?
Hope everything is clear. :good: Thanks in advance.
veteNL said:
Hey guys i have question. I am currently on 24.11.18.lux.reteu.reteu.en.En reteu. I flashed this with a link that was posted on here before the update for 6.0 came to my country. The update that came OTA was 24.41.33 (with the januari patch). I never received this and am wondering if i will still get updates in the future or if I have to keep doing this myself. I am not rooted or anything. I just updated with the link that was posted here. http://forum.xda-developers.com/moto-x-play/help/marshmallow-ota-uk-t3277756/post64971862#post64971862
So basically:
I flashed from 5.1.1 to 6.0 myself with link posted here through recovery mode.
I now have 24.11.18. (december patch)
Others in my country that just waited have 24.41.33. (januari patch)
What do I do now in order to get updates? Wait and it will come? Or do i have to keep updating myself?
Hope everything is clear. :good: Thanks in advance.
Click to expand...
Click to collapse
The best to do is flash the 5.1.1 factory image for your model and location. And then updating through the normal way. Not manually
Thanks. I'm not sure how to go about doing that. So updates wont come to my phone anymore OTA? I've read on here that the 6.0.1 update should arrive soon. I'm new to all this and don't want to risk breaking my phone. Maybe it's better to wait? I'm from the Netherlands too btw.
veteNL said:
Thanks. I'm not sure how to go about doing that. So updates wont come to my phone anymore OTA? I've read on here that the 6.0.1 update should arrive soon. I'm new to all this and don't want to risk breaking my phone. Maybe it's better to wait? I'm from the Netherlands too btw.
Click to expand...
Click to collapse
You should have the january security patch, if you dont and dont have an update you need to flash the factory image. If you don't want to brick your phone you shouldnt flash updates manually in the first place.
You can also try this: https://www.androidfilehost.com/?fid=24421527759884307 which is the flashable zip for the dutch 6.0 firmware (but you need twrp and unlocked bootloader for that.
But you probably need to download and flash this: https://www.google.com/url?q=https:...sntz=1&usg=AFQjCNGTQx60cH6emtbDNwtOZh-3m7Mdww
And follow this: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
(doesn't need an unlocked bootoader
Thanks. I think I'll just wait until 6.0.1 arrives here in NL and see if it let's me update too before i try and do all this.
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.
Greetings devs and members:
I have recently begun using a Moto G5 Plus (XT1687 - N. American SKU) that was never updated (due to being in a drawer someplace).
I know that many things have been unlocked and improved by the devs for this particular handset. My question is simply this:
How should I update it? Should I update it?
Should I go OTA (retus) (currently blocking), or should I bypass everything and go directly to Oreo (using the update file, after a factory reset and such)?
Or, hell should I stick with Nougat right now? It seems that lots of folks are having issues, and I just wanted a more informed opinion.
Thank you.
sinister008 said:
Greetings devs and members:
I have recently begun using a Moto G5 Plus (XT1687) that was never updated (due to being in a drawer someplace).
I know that many things have been unlocked and improved by the devs for this particular handset. My question is simply this:
How should I update it? Should I update it?
Should I go OTA (retus) (currently blocking), or should I bypass everything and go directly to Oreo (using the update file, after a factory reset and such)?
Or, hell should I stick with Nougat right now? It seems that lots of folks are having issues, and I just wanted a more informed opinion.
Thank you.
Click to expand...
Click to collapse
To stay with Nougat is not a bad choice, it's a well working system.
If you want to get to Oreo just apply all the OTA updates until you're there. No need to do anything else if your device isn't rooted or the system has been tampered in any other way.
Both firmwares seem to work well.
If the phone is not rooted, then OTA updates are the easiest. Make sure the phone is fully charged or plug it in first. Go to about phone, go to check system updates, accept OTAs until it says up to date, which is likely be Oreo. If it stops at -18 the it may take a few days before the phone alters you to Oreo update.