Related
I bought the device about a month ago and it came with COS yog4pas52c, This version has Android security patch level of January 2016.. Is it the latest? Because on cyanogen's website the latest version is yog4pas3oh and security patch level of November 2015.. Should I do manually update for this version or it's older than mine?
It ia the latest update. It is ok, you don t have to update anything
Latest its YOG4PAS60J with 2016-02-01 security patch
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?
Hey there !
I have a Moto G5 Plus International edition (XT1681) with firmware NPNS25.137-92-4 (latest January Patch).
I want to know what firmware to download from here (https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/) for factory flash not to get bricked like an idiot.
I don't know which one is good
Thanks
The last 2 ROMs are for your device, if you have a custom recovery I recommend to install the flashable version from this link .
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Here are the same version of your device NPNS25.137-92-4 (20180101 security patch)
Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/
CobraBoyFR said:
Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/
Click to expand...
Click to collapse
i didnt try to flash over a fastboot rom, maybe you cant do that.
Thanks
But basically, what I need is flashing full stock firmware (with recovery and kernel), no matter if it's january update or not. Just the factory images I had when I bought the phone. And I don't know what version is OK for my phone (XT1681 with NPNS25.137-92-4 now) 'cause I don't want to hard brick it when OTA updating (to Oreo for example)
From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.
RokCruz said:
From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.
Click to expand...
Click to collapse
Right now I'm on stock NPNS25.137-92-4, with TWRP recovery + Magisk root + ElementalX kernel
I'm not planning to flash any custom ROM for the moment. When the official Oreo update comes out, I want to update. But I know it won't go well if I OTA update it with my current configuration. That's why I want to be able to flash stock with fastboot (rough clean install), no matter what version I get : All i want is to be able to update to Oreo when it's out. Problem is, I don't know which image I need to download from here : https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I know it's there, but don't know exactly the good version.
This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.
RokCruz said:
This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.
Click to expand...
Click to collapse
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.
echo92 said:
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.
Click to expand...
Click to collapse
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?
RokCruz said:
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?
Click to expand...
Click to collapse
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
That was roughly what I figured out but damn, those explanations, thanks buddy :highfive:
The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.
driverdis said:
The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.
Click to expand...
Click to collapse
On xt1681 right?
Thanks for your feedback
echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
yeah i cant apply normal OTA over flashable rom. I was on NPN25.137-92(flashable) i download NPNS25.137-92-4(flashable too) i dirty flashed it and it works perfect without lose my stuff
I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.
jkl555 said:
I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.
Click to expand...
Click to collapse
Just to reply to myself for (2). I found the following link
https://www.stockrom.net/2017/05/st...g5-plus-xt1683-xt1681-android-7-0-nougat.html
hi everyone,
since i side loaded Android 8.1 image i didint receive any security update! i check for updates regularly but there is no updates !
what should i do ?
fully stock locked bootloader.
lastest patch 5 january.
I just bought another nexus 6p( was enrolled into beta program ). I did flash the latest image from google, and yeah, seems like the last ota security patch is from january. Can someone confirm this ? I forgot to look at my last nexus 6p.
Latest sec Update february 5th here...but flashed myself due to unlocked and rooted...
I updated to Oreo OTA on Sunday. Have February security patch installed.
Sent from my Nexus 6P using Tapatalk
do you guyes know to to downgrade to 8.0??
i've manually flashed all the missing updates i think its the only way.
Yeah, something about the beta program of 8.1 froze updates at the January security patch for me as well.
I ended up dirty flashing the release 8.1 system image and everything works fine now, still don't get OTA update notifications though.
A few days ago, I did get the march 5 security update, after flashing this image 8.1.0 (OPM3.171019.016, Mar 2018) from google .
after flashing all the missing updates , OTA updates started to roll out as normal to me
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