December update

[alealicks]

I'm from Mexico and like 20 mins ago I got this update. Has anyone got this update? (An OTA update link is in the thread just use the Search bar)

 

[RenePaul99]

I'm from Mexico and like a 20 min ago got this update. Anyone got the update? (I don't know how to extract the OTA, so don't ask me for that)

I'm from Mexico too, I received the OTA today too

---------- Post added at 10:37 PM ---------- Previous post was at 09:52 PM ----------

It seems that this update will also update the bootloader to B1:07(in the September patch Rom, it was B1:06)

 

[shadow20012]

Security Patch?

 

[Ann.Vogelfang]

I saw people complaining that the camera does not work well. It is true?

Enviado desde mi Moto G (4) mediante Tapatalk

 

[RenePaul99]

Security Patch?

Yes

 

[echo92]

I'm from Mexico too, I received the OTA today too

---------- Post added at 10:37 PM ---------- Previous post was at 09:52 PM ----------

It seems that this update will also update the bootloader to B1:07(in the September patch Rom, it was B1:06)

Thanks, that's useful to know, looks like updating to the December 2017 security patch may mean the latest blankflash we have could no longer work for rescuing bricked devices in the future. Until we get a new blankflash possibly.

 

[RenePaul99]

OTA Captured: https://mega.nz/#!VdcCTZpZ!i4RP94md7le4l5tOlT_88ywmFzxtP9GZISxnLIiyzw4

Sorry for Mega

 

[SoNic67]

Thanks! Now some of the wizards might "cook" a full install so we all can update our unlocked/rooted devices.

 

[tazlooney89]

Blur_Version.25.221.10.athene.retail.en.US.zip

Download

 

[echo92]

Some observations about this patch:

a)36.2 MB in size, carrying the December 2017 security patch as noted above with a final build of NPJS25.93-14-13/3. md5: 28d24a02c7e7caecf4be102a6059074f Though it's the 1st December 2017 update, I'm not sure if this update has the KRACK patches built in (as they were covered by the 6th November 2017 patch) - depends on when Motorola got the patch. Apologies for misleading anyone.
b)From the updater script, requires NPJS25.93-14-10 already on your device to flash.

Package expects build thumbprint of 7.0/NPJS25.93-14-13/3:user/release-keys or 7.0/NPJS25.93-14-10/10:user/release-keys

c)Looks to be carrying updates for some apps/services, such as BellTVWidget and OmegaPttMX.
d)As helpfully noted by RenePaul99, updates the bootloader to B1:07 (with a build date of 2017-11-07) from B1:06 in NPJS25.93-14-10. This may result in the blankflash we have at https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 failing to work if this OTA update is applied - it may check and only work on B1:06 and earlier bootloaders (and no, generally you can't downgrade bootloaders) I'm not certain of this, though I dislike seeing devices bricked and the only resolution being an expensive motherboard replacement. So crucially, if you've updated your device to this OTA update, be very careful if you decide to flash older Motorola stock ROMs (e.g. after flashing a custom ROM), as an OTA update could hard brick your device, and the current blankflash may not work in rescuing your device. The safest way to revert, if you updated to this stock patch level, would be to use your TWRP backup or wait for the NPJS25.93-14-13 fastboot ROM to be 'obtained' (leaked) from Motorola.

EDIT - 17/01/2018 - I've seen one possible rescue with the latest blankflash we have from a user updated to the December 2017 B1:07 bootloader. Though it suggests the blankflash is still working, be very careful regardless.

As generally with OTA updates, they only will flash successfully onto a device with a clean stock system, stock recovery and stock kernel. Unlocked bootloader status doesn't appear to matter.

Of course, if you're rooted, then the above aren't true; I was running a XT1642 with TWRP, ElementalX and magisk 13.3, so the OTA update is a no-go. One straightforward way to restore my device to a OTA friendly state was to re-flash the NPJS25.93-14-10 stock ROM (which we have here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138)

The following flashing commands I used should not affect your data and return your device to an OTA friendly state, but as always back up your data just in case. You may be able to use fewer commands but I prefer to flash all these partitions (you probably want to do things properly with the core firmware running your device!) As far as I know, system, OEM, boot, recovery and logo partitions need to be stock at the very least. GPT/bootloader/modem you could omit if you're sure they are the same patch level as NPJS25.93-14-10 (bootloader should be B1:06 and modem should be ending in 62.01R), if you're not sure, I'd flash them too to ensure all your firmware is of the same patch level. Don't mix and match patch levels when it comes to OTA updates... Oh, and check that you have plenty of time, you don't want to rush firmware flashes.

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot

After manually flashing each command (copy and paste is your friend, though nothing to stop you using a script), my device rebooted to system (complaining of bad key or N/A on the bootloader warning screen, that's normal). Rebooted to stock recovery (with the Android on its back and the no command), then held the power button before pressing and releasing the volume up key, then releasing the power button. Took a few tries before getting into the recovery menu. (as explained here: https://forum.xda-developers.com/moto-g4-plus/help/command-stock-recovery-xt1642-t3484616 )

As before, flashed the OTA update without issue from the SD card/internal storage (though had to mount /system as the recovery complained it couldn't mount internal or external storage, after mounting the 'apply update from SD card' worked and loaded up internal storage...), wiped cache after installation and rebooted.

Now I'm running NPJS25.93-14-13 and still have all my data Not rooted or having TWRP on, but I might see how I get on with this new build. Initial impressions are that it's fast and stable, though early days yet. As for the camera, photos and video with the rear camera appear to work okay with version 6.0.86.7 of the Moto camera app, what problems have been mentioned with the camera?

 

[alejo.z]

Working fine here XT1621 just used adb to sideload

 

[victor.neyoy]

that oreo update seems to be vaporware as the time goes on

 

[georgeiulian89]

that oreo update seems to be vaporware as the time goes on

Knowing that Motorola is updating the security patches every 3 months, in the best case will get Oreo by the end of March (the date of the new security patch update).

 

[Outfield303]

Still Waiting....

 

[leoh.rod]

Please anyone has the rom flasheable through adb? i tried to downgrade from npjs25.93-14-13 to npjs25.93-14-10 and now my phone is bricked and i need the rom npjs25.93-14-13 to flash. anyone?? links?

 

[echo92]

Please anyone has the rom flasheable through adb? i tried to downgrade from npjs25.93-14-13 to npjs25.93-14-10 and now my phone is bricked and i need the rom npjs25.93-14-13 to flash. anyone?? links?

What firmware did you try to flash that bricked your device? By bricked do you mean LED blinking and failure to boot?

Currently no NPJS25.93-14-13 firmware available, we have to wait for Motorola to deploy it to their firmware server and hopefully someone can grab the link.

 

[leoh.rod]

What firmware did you try to flash that bricked your device? By bricked do you mean LED blinking and failure to boot?

Currently no NPJS25.93-14-13 firmware available, we have to wait for Motorola to deploy it to their firmware server and hopefully someone can grab the link.

my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?

 

[echo92]

my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?

Are there any messages in recovery mode or is it just stuck booting? Have you tried a cache wipe in recovery and reboot, or if you've got your data backed up, try a factory reset (which would wipe your data)?

Was the flash complete, did you see [OKAY] on all the NPJS25.93-14-10 firmware flashing commands? You may have an incomplete flash if not, could try another flash of the September 2017 stock firmware (without flashing GPT/bootloader). Can I ask why you were trying to downgrade your firmware from the 7.0 December patch? Is your bootloader unlocked (should be if you're trying to downgrade)?

Are you able to boot to bootloader (power off your device, then hold down power and volume down, then you should boot into bootloader), and select 'Start' - does that boot your device or result in a bootloop again?

 

[SoNic67]

my phone was on npjs25.93-14-13 and i tried to downgrade to npjs25.93-14-10 and it doesnt boot. its stucked on recovery mode. what should i do now to bring it back?

Never downgrade when you don't have the full flash available. AFAIK the new bootloaders cannot be downgraded, and it was reported that the 14-13 brings in a new bootloader. Older system don't usually work with the new bootloaders.
As it was said, you might need to wait to get the full 14-13 and stay on that.

 

[jack_04]

Anyone from India got this update?