I was wondering how many and what updates everyone else have received and when?
I'm currently on the April 2017 security update and I received that in early June I believe.
I'm hoping Huawei can at least be excused by the fact they're working on an Oreo update instead of doing security updates and bug fixes (highly doubtful though). Mine is a Nordic unlocked model by the way.
So are anyone else receiving security updates?
Not here, in Spain. The thing is, I don't see any security patch coming till next EMUI version arrives, hopefully before the end of the year.
Not sure if this helps, but I found some way opening another security gap
As far as I figured out, you need 3 files for the update to work:
update.zip
update_full.zip (or update_full_WAS-XXX_hw_eu.zip)
update_data_full_public.zip
I am sure, FirmwareFinder or any other tool might come in handy doing so. The next thing you'd need would be TWRP which is available as some beta build somewhere on this forum. Then you'd have to unlock the bootloader and root your device to get TWRP on it. I'd recommend doing some research on this as you might have to get some code for "fastboot oem unlock"...
Flash the files listed above the way they're listed.
Related
I've read a few posts stating the bootloader exploit for the S4 would be relatively easy to patch by At&t and my concern is that they may do so before my upgrade on June 7. If at&t does patch it before then would it be possible to use Odin to downgrade the phone to an earlier firmware release that doesn't have the patch? If not I'll have to figure out a way to get the phone as soon as possible.
calvin35 said:
I've read a few posts stating the bootloader exploit for the S4 would be relatively easy to patch by At&t and my concern is that they may do so before my upgrade on June 7. If at&t does patch it before then would it be possible to use Odin to downgrade the phone to an earlier firmware release that doesn't have the patch? If not I'll have to figure out a way to get the phone as soon as possible.
Click to expand...
Click to collapse
I don't see how anyone could know that for sure at this point. However, if a patch is released (OTA) or if newer firmware is put on the phones that patches the vulnerability itself, then it seems realistic that ODIN probably will not be able to fix the issue. Once it is patched, you probably won't be able to go back. Of course, another exploit might be found or Adam's attempt at a more permanent bottloader unlocker might find a solution. OTA updates can be fixed by just not taking them until they are cleared as OK. Newer firmware on the phone would probably need another fix. But nobody knows how long it will be until AT&T / Samsung patches the vulnerability.
Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Chavezlaw93 said:
Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Click to expand...
Click to collapse
Hello,
I would just sideload latest 7.1.2 N2G47H OTA from Google here: https://developers.google.com/android/ota
There is an easy tutorial explaining the process. If you're not sure, let me know...
Otherwise you can wait till you have an update notification. Though there's no time frame as to when it will come to you.
Good luck...
Chavezlaw93 said:
Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Click to expand...
Click to collapse
I agree with @5.1. The fastest, least hassle-free way to get to 7.1.2 is to just flash the full April image. You could also try borrowing a SIM from somebody on a different network and popping that in. Let the phone start up and wait for their cellular network to be displayed in the notification bar. Then power down and put your SIM back in. Works, but you are liable to set yourself up for a series of updates. I would also recommend you leave your bootloader unlocked and USB debugging enabled.
5.1 said:
Hello,
I would just sideload latest 7.1.2 N2G47H OTA from Google here: https://developers.google.com/android/ota
There is an easy tutorial explaining the process. If you're not sure, let me know...
Otherwise you can wait till you have an update notification. Though there's no time frame as to when it will come to you.
Good luck...
Click to expand...
Click to collapse
Hi! New to the 6p (completely) but not to flashing/mods/etc. Can this be flashed with TWRP or only via ADB? Anything I should be aware of on an unlocked/rooted nexus w/ProjectFi? Assume I will have to re-root - is this correct?
Thanks!
So as the title suggests. I bought my phone 2 months ago, and since I got it it hasn't updated once. Nothing, not so much as a security patch or anything.
I've tried googling this but nothing comes up. I obviously check via system update - and it says it's up to date.
My build number ends 137-33.
Android security patch 1st January 2017.
It's not rooted. And all stock.
Is this normal?
My phone came with same build and you're not alone. Twiddling thumbs may help with the long wait, or root and try some custom ROMs. I've got the June 5th security patch running CyberOS which is based on Android 7.1.2 and other custom ROMs are similar. There's a debloated stock ROM based on India's G5+ update (they got one already) with the March patch at least. That said, there are rumbles ours is finally coming soon if you do want to remain stock and get the OTA.
What does it say under Settings > About Phone> Software Channel?
There hasnt been an update for the UK Moto G5 Plus yet.
Dahenjo said:
.There's a debloated stock ROM based on India's G5+ update (they got one already) with the March patch at least. That said, there are rumbles ours is finally coming soon if you do want to remain stock and get the OTA.
Click to expand...
Click to collapse
I asked a similar question in a separate thread and maybe you know, is the update 137-35-5 that is available as a zip able to be flashed over this same build, 137-33 I have now? I unlocked my bootloader but stopped short of flashing twrp or rooting. I think the 35-5 update only has the May security patch only but someone uploaded the full firmware. Any opinions are welcome.
MrBelter said:
There hasnt been an update for the UK Moto G5 Plus yet.
Click to expand...
Click to collapse
Yeah, I cannot believe that some regions were being updated months ago to March and subsequently May security patches and the UK is still yet to receive any updates at all. Why do manufacturers make their lives so much more difficult by having such variances by region? A single software version for all regions seems to work just fine for Google and their Nexus/Pixel lines.
surrealjam said:
Yeah, I cannot believe that some regions were being updated months ago to March and subsequently May security patches and the UK is still yet to receive any updates at all. Why do manufacturers make their lives so much more difficult by having such variances by region? A single software version for all regions seems to work just fine for Google and their Nexus/Pixel lines.
Click to expand...
Click to collapse
I fully agree with you mate and i think it is only going to get worse with Lenovo pumping out more and more models.
I am in same boat my friend
I have the unlocked US model XT1607 and it's not the Amazon Prime version. So I'm on February 2017 security patch but my build is MPIS24.241-2.35-1-13 and that's not the build number I need to be on. I need to be on build number MPIS24.241-15.3-16
I have the 7.1.1 update file. I apply update from SD card in recovery and it sits there like it's working and then it aborts but before that it says something that I can't quite remember.
I want to unlock my bootloader but I don't have internet in my house so it's just this device. Seems like it might be tedious to go back and forth. I'll probably just do that if no one can help me here especially since 7 people have read this and given no help yet.
Does anyone elses Moto G4 Play have the February security patch but not the right build number that required to update the soak test? Please can someone help me? Unlocking my bootloader is only if I can't get this to work. Surely I'm not the only one that has a different build number than everyone else with the February 2017 security patch. Please can someone help.
MOTOG4PLAY said:
Does anyone elses Moto G4 Play have the February security patch but not the right build number that required to update the soak test? Please can someone help me? Unlocking my bootloader is only if I can't get this to work. Surely I'm not the only one that has a different build number than everyone else with the February 2017 security patch. Please can someone help.
Click to expand...
Click to collapse
Ya know, you have posted the same question multiple times in different threads over the past 24 hours. Enough! Your situation by no means warrants this level of noise. You'll get a response if someone has something meaningful to contribute. Silence also conveys a message ...
It's a real big issue for me man. Sorry. But have you ever heard about security patches with a different build number ever!?
Are you sure you downloaded the XT1607 OTA soak? because the only one I have seen is for the XT1603 and won't work.
Blur_Version.26.21.8.harpia.retail.en.US.zip
If you want to keep your bootloader locked, I would caution against flashing the 7.1.1 soak and wait for the official OTA to make it to the US for your current build (or be willing to wait for a fastboot 7.1.1 stock ROM).
As eager as you are, there's little evidence I've seen suggesting the leaked soak test is the version that Motorola will deploy in its public release of 7.1.1. It might turn out the soak test is the actual build Motorola will release - if it's not, then if this is flashed you may not receive OTA updates. As I understand it, Motorola is pushing soak test updates only to those registered with its Motorola Feedback Network (where they have your IMEI to track what update you've received). Thus, if you flash this soak test and it subsquently arises that further updates are needed to bring you back onto the offical OTA update patch, if those updates haven't been captured by someone on XDA, you're stuck with the soak test unless a newer fastboot stock ROM is available. I've seen this with the Moto G4/Plus update to Nougat (where users flashed NPJ25.75-2 and were not receiving the OTA to the final Nougat build, and had to flash the fastboot stock ROM to be back on the OTA update path) and also am seeing it with the Moto Z Play with their Nougat update.
Motorola has in the past released different versions of their updates for different territories, and soak tests from some test regions (e.g. Brazil, India) have not flashed onto devices because their builds have been different. E.g. with the Moto G4/Plus, the Indian Nougat soak test was flashable on EU devices (with the July 2016 patch, MPJ24.139-63) but not flashable on US devices with MPJ24.139-64, same security patch. A subsequent official Nougat update was flashable on US devices.
At the end of the day, it's your device and your choice, personally I'd wait for the official update. Additionally, with the soak test, it appears to have the June 2017 security patch. With this security patch, on the Moto G4 Plus at least, attempts to downgrade from the June 2017 update have resulted in hard bricks (and not recoverable by a blank flash). I do not know if this will happen on the G4 Play (I have a G4 Plus, and as such it's up to you how much of what I've written you take on board), but I really wouldn't risk downgrading.
Good luck whichever way you choose.
Hi XDA fam. I'm currently running NPH 25.200.22 unlocked and rooted with Majisk since it was released. Work and life has prevented me from keeping up with the update(s) that have come out since then. However, there was a thread put out a while back in the General forum that provided the instructions to update that came out after 25.200.22. I have been having a hard time finding this thread (don't know if it was deleted or not) and the search function isn't helping. Does anyone recollect the title or can point me to the instructions to flash (dirty) the OTA? I really don't want to go through the process of wiping the phone and putting on the firmware.
I appreciate the help.
I think 25.200.22 is the latest release and most likely the final "official release"
My phone lists the Security patch level as October 1, 2017.
swieder711 said:
I think 25.200.22 is the latest release and most likely the final "official release"
My phone lists the Security patch level as October 1, 2017.
Click to expand...
Click to collapse
There was at least one security update after that. My patch level is September 1, 2017.