Database Users

Can't find update (XT1625)

So I cannot find an update for the Moto g4. The software update says it is fully up to date even though it is running Android 6.1.1 when 7.0 is out.
If any info is needed, ask me.

I'm guessing you mean v6.0.1 MM (NPJ24-139.64/65 I think is the latest MM for XT1625 and XT1644 devices)?
If you wanted to, you could flash the fastboot stock ROM for NPJS25.93-14.4 which is the latest update available (v7.0, March 2017 security update):https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 As always, be aware that the update may affect your data (as with any flash to system), back up accordingly.

echo92 said:
I'm guessing you mean v6.0.1 MM (NPJ24-139.64/65 I think is the latest MM for XT1625 and XT1644 devices)?
If you wanted to, you could flash the fastboot stock ROM for NPJS25.93-14.4 which is the latest update available (v7.0, March 2017 security update):https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 As always, be aware that the update may affect your data (as with any flash to system), back up accordingly.
Click to expand...
Click to collapse
Are you sure this is for XT1625? It looks like it is for XT1641 and 1645.

FIUSHerson said:
Are you sure this is for XT1625? It looks like it is for XT1641 and 1645.
Click to expand...
Click to collapse
It should work, as the NPJS25.93-14.4 build is based on the NPJ25.93-14 (Dec 2016 security patch) build, just updated with the March 2017 security update.
If you wish to be more certain, you can flash the aforementioned NPJ25.93-14 update via the fastboot ROM (from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369) which has XT1625 users reporting it flashes, and then wait for the OTA for the March 2017 security patch (which recent indications suggest it's been deployed in the US), or you could sideload the OTA (after flashing the Nougat 93-14 update) by downloading from here: https://forum.xda-developers.com/moto-g4-plus/how-to/official-moto-g4-plus-ota-update-build-t3584982
Hopefully, by flashing the Nougat update, OTA updates will arrive again via the retail USA software channel.

ATTENTION!Help needed to revive phone

I downgraded to marshmallow and I tried to update to nougat through the official way. It was updating for some time and then screen went off. I tried turning it on with no avail. I had latest bootloader which was unlocked.
Please help guys
I beg you

CMKdaGreatest said:
I downgraded to marshmallow and I tried to update to nougat through the official way. It was updating for some time and then screen went off. I tried turning it on with no avail. I had latest bootloader which was unlocked.
Please help guys
I beg you
Click to expand...
Click to collapse
Seems you bricked your phone by downgrade the bootloader...
Did you tried to follow the unbrick guide here https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Otherwise please provide on which rom version you are before downgrade to marshmallow and also the device type you have.
I'm sure @echo92 will help further :good:

strongst said:
Seems you bricked your phone by downgrade the bootloader...
Did you tried to follow the unbrick guide here https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Otherwise please provide on which rom version you are before downgrade to marshmallow and also the device type you have.
I'm sure @echo92 will help further :good:
Click to expand...
Click to collapse
Downgraded from stock nougat to stock marshmallow and tried OTAing back to nougat

CMKdaGreatest said:
Downgraded from stock nougat to stock marshmallow and tried OTAing back to nougat
Click to expand...
Click to collapse
Which stock nougat rom and which marshmallow rom. The versions. And did you tried the unbrick guide?

I tried the unbrick guide. I flashed the blank flash and got a dummy bootloader but I can't flash gpt or bootloader. It always shows failed. How should I do it?

strongst said:
Which stock nougat rom and which marshmallow rom. The versions. And did you tried the unbrick guide?
Click to expand...
Click to collapse
I used this guide. In the third page there's a post containing a blank flash attached. I flashed that but can't flash gpt or bootloader

CMKdaGreatest said:
I used this guide. In the third page there's a post containing a blank flash attached. I flashed that but can't flash gpt or bootloader
Click to expand...
Click to collapse
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.

echo92 said:
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.
Click to expand...
Click to collapse
Thank you so much man. Much appreciated

echo92 said:
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.
Click to expand...
Click to collapse
I already flashed a blank flash. How do I flash another one??

CMKdaGreatest said:
I already flashed a blank flash. How do I flash another one??
Click to expand...
Click to collapse
You won't be able to flash another blankflash unless your device is in the Qualcomm HS-USB 9008 mode again (in other words, you hard bricked by corrupting your bootloader again).
I'm hoping as whatever blankflash you used worked properly and thus you shouldn't have issues flashing the latest firmware. However, they can overwrite a damaged bootloader with the dummy bootloader, and as such you need to verify you're flashing the correct blankflash. The inbuilt checks should stop you from flashing the wrong blankflash however.
If you still want to revert back to Marshmallow, then do not use OTA updates at all.
As an aside, do not always depend on these blankflashes, Motorola is updating the bootloader with every firmware release and there's always a chance the blankflashes may not work anymore. We're not supposed to have these blankflashes (leaks from generous engineers are our source) and so we don't know if we can get another one should the current blankflash stop working.

echo92 said:
You won't be able to flash another blankflash unless your device is in the Qualcomm HS-USB 9008 mode again (in other words, you hard bricked by corrupting your bootloader again).
I'm hoping as whatever blankflash you used worked properly and thus you shouldn't have issues flashing the latest firmware. However, they can overwrite a damaged bootloader with the dummy bootloader, and as such you need to verify you're flashing the correct blankflash. The inbuilt checks should stop you from flashing the wrong blankflash however.
If you still want to revert back to Marshmallow, then do not use OTA updates at all.
As an aside, do not always depend on these blankflashes, Motorola is updating the bootloader with every firmware release and there's always a chance the blankflashes may not work anymore. We're not supposed to have these blankflashes (leaks from generous engineers are our source) and so we don't know if we can get another one should the current blankflash stop working.
Click to expand...
Click to collapse
It worked. After the bootup, I received an update. I updates my phone and it successfully booted up. I received another update. Now, after this, its back to the same condition. Why is this happening?

Can you give me links for the firmware too if you don't mind? I need the Indian version for XT1643. Dont mind me man, I'm still in 9th grade

CMKdaGreatest said:
It worked. After the bootup, I received an update. I updates my phone and it successfully booted up. I received another update. Now, after this, its back to the same condition. Why is this happening?
Click to expand...
Click to collapse
CMKdaGreatest said:
Can you give me links for the firmware too if you don't mind? I need the Indian version for XT1643. Dont mind me man, I'm still in 9th grade
Click to expand...
Click to collapse
Did you re-flash the latest firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 For NPJS25.93-14-13 (Nougat, Dec 2017 build)
If not, then your device is still with a mismatched bootloader and system - you have the December 2017 bootloader but the much older Marshmallow system. That means any OTA update you take may well keep hard bricking your device unless you re-flash your device to have firmware of the same patch level (bootloader and system). Then, you should be okay to take OTA updates.
This is the major problem with downgrading - OTA updates have the ability to overwrite your bootloader without checking first if your bootloader is the same patch level as your system. As you've downgraded, this is likely why older OTA updates brick.
Un-brick your device then use the flashing instructions here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 with the latest NPJS25.93-14-13 firmware. Do not use/install OTA updates until you've re-flashed the latest stock firmware.

echo92 said:
Did you re-flash the latest firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 For NPJS25.93-14-13 (Nougat, Dec 2017 build)
If not, then your device is still with a mismatched bootloader and system - you have the December 2017 bootloader but the much older Marshmallow system. That means any OTA update you take may well keep hard bricking your device unless you re-flash your device to have firmware of the same patch level (bootloader and system). Then, you should be okay to take OTA updates.
This is the major problem with downgrading - OTA updates have the ability to overwrite your bootloader without checking first if your bootloader is the same patch level as your system. As you've downgraded, this is likely why older OTA updates brick.
Un-brick your device then use the flashing instructions here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 with the latest NPJS25.93-14-13 firmware. Do not use/install OTA updates until you've re-flashed the latest stock firmware.
Click to expand...
Click to collapse
The first link in your last post, does it have latest firmware? I reflashed the may or march 2016 firmware after the blank flash, I don't remember which

CMKdaGreatest said:
Can you give me link to latest firmware?
Click to expand...
Click to collapse
The link to the latest firmware was the first link I gave you in my previous reply... NPJS25.93-14-13 is the latest stock ROM for India, Brazil and EU devices.
Yeah, flashing the May 2016 or March 2016 firmware really won't help you - again, as your bootloader is December 2017 flashing older firmware and attempting to take OTA updates will just keep hard bricking you until you reflash the December 2017 firmware, or if you do not use OTA updates. You cannot downgrade bootloaders usually.

echo92 said:
The link to the latest firmware was the first link I gave you in my previous reply... NPJS25.93-14-13 is the latest stock ROM for India, Brazil and EU devices.
Yeah, flashing the May 2016 or March 2016 firmware really won't help you - again, as your bootloader is December 2017 flashing older firmware and attempting to take OTA updates will just keep hard bricking you until you reflash the December 2017 firmware, or if you do not use OTA updates. You cannot downgrade bootloaders usually.
Click to expand...
Click to collapse
Yea I'll try tomorrow man. Thanks a ton!! The method of blank flash is the same right?? If it doesnt work then what should I do??

CMKdaGreatest said:
Yea I'll try tomorrow man. Thanks a ton!! The method of blank flash is the same right?? If it doesnt work then what should I do??
Click to expand...
Click to collapse
Should be, please use the latest athene blankflash in the Unbrick guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 and the latest stock ROM as mentioned. I would also advise deleting any old stock ROMs - Marshmallow or Nougat - on your computer, unless you are confident you will not use OTA updates whilst downgraded. Motorola and other OEMs appear to have not designed protections into their updates for downgraded devices (and assume that you've taken responsibility ever since you unlocked your bootloader).
If this doesn't work, then you'll either have to wait for another newer blankflash to be leaked (perhaps when we get the Oreo update, but again, it's by chance whether we get another blankflash), or be willing to pay for a motherboard replacement. A motherboard replacement appears to be in the range of 7000-10000 rupees or your regional equivalent.

echo92 said:
Should be, please use the latest athene blankflash in the Unbrick guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 and the latest stock ROM as mentioned. I would also advise deleting any old stock ROMs - Marshmallow or Nougat - on your computer, unless you are confident you will not use OTA updates whilst downgraded. Motorola and other OEMs appear to have not designed protections into their updates for downgraded devices (and assume that you've taken responsibility ever since you unlocked your bootloader).
If this doesn't work, then you'll either have to wait for another newer blankflash to be leaked (perhaps when we get the Oreo update, but again, it's by chance whether we get another blankflash), or be willing to pay for a motherboard replacement. A motherboard replacement appears to be in the range of 7000-10000 rupees or your regional equivalent.
Click to expand...
Click to collapse
I'm just curious to know what happens if we flash an old blank flash.

CMKdaGreatest said:
I'm just curious to know what happens if we flash an old blank flash.
Click to expand...
Click to collapse
Depends - if it's an old blankflash for our device (for Snapdragon 617, MSM8952), it'll likely fail as the blankflash, in communicating with the device's bootloader, determines the blankflash is too old to repair the bootloader. Blankflashes appear to send a programmer over to your device which verifies that your device bootloader is not newer than the blankflash, else you'd be downgrading your bootloader and possibly causing a security issue. Thus, your device may not be rescued and require a new motherboard. We saw plenty of these incidents when users downgraded to Marshmallow from Nougat 6 months ago and then tried to use OTA updates, and it was only with the leak of a newer bootloader version B1:06 compatible blankflash that people were able to rescue their devices without spending a lot of money. Without that blankflash, I think we have very limited means of rescue. We cannot make these blankflashes as they have to be cryptographically signed and built by OEMs like Motorola, I think to maintain the bootloader security, as such we do not know if we'll get a new one. In theory, we could make a loader image - a complete image of a working device - to try to bypass the bootloader corruption without needing a blankflash. That has had some success on other devices, but hopefully you should need neither a blankflash nor a loader image.
We've seen instances of other Moto devices' blankflashes rescuing devices (e.g. Moto Z2 Play rescuing Moto Z Play and G5 Plus), however, their CPUs are very similar. Our Snapdragon 617 is not used by any other Motorola device, so we have a very limited source of blankflashes.
I would hope blankflashes are in general well programmed enough to not flash onto devices they are not meant to flash onto, else if they could flash onto a different device, you could really screw up your device.
In summary, an older blankflash likely just won't work, and you'd either have to wait for a newer blankflash or pay for an expensive repair. Unless you are willing to do either, I would be very careful in future with downgrading.

echo92 said:
Depends - if it's an old blankflash for our device (for Snapdragon 617, MSM8952), it'll likely fail as the blankflash, in communicating with the device's bootloader, determines the blankflash is too old to repair the bootloader. Blankflashes appear to send a programmer over to your device which verifies that your device bootloader is not newer than the blankflash, else you'd be downgrading your bootloader and possibly causing a security issue. Thus, your device may not be rescued and require a new motherboard. We saw plenty of these incidents when users downgraded to Marshmallow from Nougat 6 months ago and then tried to use OTA updates, and it was only with the leak of a newer bootloader version B1:06 compatible blankflash that people were able to rescue their devices without spending a lot of money. Without that blankflash, I think we have very limited means of rescue. We cannot make these blankflashes as they have to be cryptographically signed and built by OEMs like Motorola, I think to maintain the bootloader security, as such we do not know if we'll get a new one. In theory, we could make a loader image - a complete image of a working device - to try to bypass the bootloader corruption without needing a blankflash. That has had some success on other devices, but hopefully you should need neither a blankflash nor a loader image.
We've seen instances of other Moto devices' blankflashes rescuing devices (e.g. Moto Z2 Play rescuing Moto Z Play and G5 Plus), however, their CPUs are very similar. Our Snapdragon 617 is not used by any other Motorola device, so we have a very limited source of blankflashes.
I would hope blankflashes are in general well programmed enough to not flash onto devices they are not meant to flash onto, else if they could flash onto a different device, you could really screw up your device.
In summary, an older blankflash likely just won't work, and you'd either have to wait for a newer blankflash or pay for an expensive repair. Unless you are willing to do either, I would be very careful in future with downgrading.
Click to expand...
Click to collapse
It worked!! Thank you so much. Now it's perfect!!

questions about the 7.1.1 update

Hi guys, I recently read about 7.1.1 being officially released, the thing is I already updated to Nougat via the soak test uploaded last year, should I revert to stock rom and get Nougat officially? How it is on performance quality?, Also, I'm on September security patch, do i have risk of bricking?

If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

igna.98 said:
If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
How is your GPS on that firmware? Also, do you know if that firmware will work on the XT1607?

zahna said:
How is your GPS on that firmware? Also, do you know if that firmware will work on the XT1607?
Click to expand...
Click to collapse
I'm not able to tell you how GPS works because I don't own the phone, I installed it in a friend's phone. And AFAIK it can be installed on all models except Verizon's XT1609. Tell me if it works for you

igna.98 said:
If you flash this through fastboot you will get 1 November 2017 security patch without having to downgrade. Then you may get December and February updates
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
will it work on xt1607 ?
UPDATE: I will try it, when i get back home.

What is the latest patch, or what is the latest update for reteu device

My wife has moto g5plus reteu device. I looked into "About Phone"
She has android 7.0 with August 2017 patch.
This is not the latest. Am i right?
I was trying to search for latest update but it says its latest.
If not, how can i manually update it.
Is it possible to download the latest patch as zip and flash it with stock recovery.
Thanks

Has your device been tampered with (unlocked, reflashed stock) before? If you're fully stock, that should be the latest version. I don't know what's the current version for your software channel though, I'm on RETUS.

Npns25.137-93-4 january is the latest for EU.
Normally it will be available in the updater in settings: "about phone".
Try connecting both with and without WiFi.

reCoded said:
Has your device been tampered with (unlocked, reflashed stock) before?
Click to expand...
Click to collapse
Yes it was.

knjigo said:
Yes it was.
Click to expand...
Click to collapse
As Knutselmaaster said that the latest is the January patch, that must mean that you either didn't flash the correct firmware for your country, or something went wrong with flashing. Reboot into your bootloader and check if your software status says "Official."

reCoded said:
As Knutselmaaster said that the latest is the January patch, that must mean that you either didn't flash the correct firmware for your country, or something went wrong with flashing. Reboot into your bootloader and check if your software status says "Official."
Click to expand...
Click to collapse
just rebooted into fastboot it says "Official"

knjigo said:
just rebooted into fastboot it says "Official"
Click to expand...
Click to collapse
Alright, that's a good sign. I can't really help you too much since I don't have a RETEU device. I'd look into finding the correct build number for RETEU, find the firmware file, then flash the firmware and test your luck.

I'll hook up into this thread, as my stock software status says modified. Does:
1. Flashing TWRP
2. Flashing Magisk
3. Solving service and 4G problem by not erasing modemsts
influence the software status? I have all above, but I'd like to get OTA somehow. Now I'm with november's security update.

reCoded said:
Alright, that's a good sign. I can't really help you too much since I don't have a RETEU device. I'd look into finding the correct build number for RETEU, find the firmware file, then flash the firmware and test your luck.
Click to expand...
Click to collapse
so i found the latest two firmwares from 3.2.2018 (in motorola firmwares)
but the one is npn and the other one is retail.
what to flash?

knjigo said:
so i found the latest two firmwares from 3.2.2018 (in motorola firmwares)
but the one is npn and the other one is retail.
what to flash?
Click to expand...
Click to collapse
I believe I flashed a NPN build that didn't have retail on it. If you want, give it a go.

As far as I recall, the firmwares released for EU were:
NPN25.137-33 (Jan 2017) > NPNS25.137-33-5 (May 2017) > NPNS25.137-33-11 (Aug 2017) > NPN25.137-93 (Nov 2017) > NPNS25.137-93-4 (Jan 2018). Brackets indicate the associated security patch, not necessarily when they were released.
Hopefully one of those firmware is on your wife's device, from what you've mentioned, the likely candidate is NPNS25.137-33-11.

echo92 said:
As far as I recall, the firmwares released for EU were:
NPN25.137-33 (Jan 2017) > NPNS25.137-33-5 (May 2017) > NPNS25.137-33-11 (Aug 2017) > NPN25.137-93 (Nov 2017) > NPNS25.137-93-4 (Jan 2018). Brackets indicate the associated security patch, not necessarily when they were released.
Hopefully one of those firmware is on your wife's device, from what you've mentioned, the likely candidate is NPNS25.137-33-11.
Click to expand...
Click to collapse
Thank you very much for information.
Now I only need the phone. My wife don't like messing around with her phone. I hope I can get it somehow

echo92 said:
As far as I recall, the firmwares released for EU were:
NPN25.137-33 (Jan 2017) > NPNS25.137-33-5 (May 2017) > NPNS25.137-33-11 (Aug 2017) > NPN25.137-93 (Nov 2017) > NPNS25.137-93-4 (Jan 2018). Brackets indicate the associated security patch, not necessarily when they were released.
Hopefully one of those firmware is on your wife's device, from what you've mentioned, the likely candidate is NPNS25.137-33-11.
Click to expand...
Click to collapse
She has NPN25.137-83 it says August 2017 security patch
Is it safe to flash NPNS25.137-33-11 over NPN25.137-83. It seems that i flashed wrong firmware last year.

knjigo said:
She has NPN25.137-83 it says August 2017 security patch
Click to expand...
Click to collapse
NPNS25.137-93-4 Stock Rom With 1 January 2018 Security Patch
https://drive.google.com/file/d/165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD/view

Kdemwa said:
NPNS25.137-93-4 Stock Rom With 1 January 2018 Security Patch
https://drive.google.com/file/d/165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD/view
Click to expand...
Click to collapse
Thank you very much:good:

Successful flashed. Thanks guys

Kdemwa said:
NPNS25.137-93-4 Stock Rom With 1 January 2018 Security Patch
https://drive.google.com/file/d/165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD/view
Click to expand...
Click to collapse
Is this an unmodified stock rom? No messing with dm-verity or anything like that?

dunderball said:
Is this an unmodified stock rom? No messing with dm-verity or anything like that?
Click to expand...
Click to collapse
Should be:
1)Flashable on locked bootloaders - if it was modified, then the bootloader would block you from flashing and/or booting. We've seen users being able to flash this okay:https://forum.xda-developers.com/showpost.php?p=75703702&postcount=22
2)The description text file mentions 'release-keys', so this firmware is likely signed with Motorola's cryptographic keys.
3)Users appear to have no issues with this build. Bear in mind this build (NPNS25.137-93-4) is mainly for EU (retEU/retGB), US (retUS) and Asia (retAPAC) devices as seen from OTA updates, you may flash this build onto devices from other retail software channels but you may not receive future OTA updates.

echo92 said:
Should be:
1)Flashable on locked bootloaders - if it was modified, then the bootloader would block you from flashing and/or booting. We've seen users being able to flash this okay:https://forum.xda-developers.com/showpost.php?p=75703702&postcount=22
2)The description text file mentions 'release-keys', so this firmware is likely signed with Motorola's cryptographic keys.
3)Users appear to have no issues with this build. Bear in mind this build (NPNS25.137-93-4) is mainly for EU (retEU/retGB), US (retUS) and Asia (retAPAC) devices as seen from OTA updates, you may flash this build onto devices from other retail software channels but you may not receive future OTA updates.
Click to expand...
Click to collapse
Thank you!

echo92 said:
Should be:
1)Flashable on locked bootloaders - if it was modified, then the bootloader would block you from flashing and/or booting. We've seen users being able to flash this okay:https://forum.xda-developers.com/showpost.php?p=75703702&postcount=22
2)The description text file mentions 'release-keys', so this firmware is likely signed with Motorola's cryptographic keys.
3)Users appear to have no issues with this build. Bear in mind this build (NPNS25.137-93-4) is mainly for EU (retEU/retGB), US (retUS) and Asia (retAPAC) devices as seen from OTA updates, you may flash this build onto devices from other retail software channels but you may not receive future OTA updates.
Click to expand...
Click to collapse
I am from India and i have just successfully installed this rom and relocked bootloader with no issue but will i get ota updates?

February security patch available (RETBR)

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.