Database Users

[Help] [Custom Rom] How to revert back to stock rom

Hello Moderators,
My Device Model : XT 1644 64 GB variant
Current Rom: Lineage OS
Bootloader Status: Unlocked
Since the US variant didn't get the nougat update, I decided to unlock my bootloader and switch to a CM based ROM.Though I love it I've been facing a lot of issues in fingerprint sensor and advanced settings
Now I'd like to go back to my stock ROM and I've few doubts
1. If I don't lock my bootloader again after switching to stock ROM will I be still eligible to receive the official updates?
2. This link to stock ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 says that it's for the Indian version will it work on the US versions?
3. After flashing the stock ROM will it be okay if I follow this thread and update to nougat https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943?
4.Does the soak test have any bugs?
5.If I'm on the soak test and Once the official nougat is available for my device what should I do?
I have a twrp backup of my stock ROM too
Click to expand...
Click to collapse
@rahulsnair @1chrome
Thanks for taking your time to help me out !!! I'd surely love to return the favour someday

Vijay Selvaraju said:
Hello Moderators,
My Device Model : XT 1644 64 GB variant
Current Rom: Lineage OS
Bootloader Status: Unlocked
Since the US variant didn't get the nougat update, I decided to unlock my bootloader and switch to a CM based ROM.Though I love it I've been facing a lot of issues in fingerprint sensor and advanced settings
Now I'd like to go back to my stock ROM and I've few doubts
1. If I don't lock my bootloader again after switching to stock ROM will I be still eligible to receive the official updates?
2. This link to stock ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 says that it's for the Indian version will it work on the US versions?
3. After flashing the stock ROM will it be okay if I follow this thread and update to nougat https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943?
4.Does the soak test have any bugs?
5.If I'm on the soak test and Once the official nougat is available for my device what should I do?
@rahulsnair @1chrome
Thanks for taking your time to help me out !!! I'd surely love to return the favour someday
Click to expand...
Click to collapse
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way

echo92 said:
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way
Click to expand...
Click to collapse
Thanks a lot bro @echo92
I actully followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 these steps now I'm running on stock nougat
Just omitted the bootloader unlock part since you told me that I'll be receiving updates even if the bootloader is unlocked

echo92 said:
1) Yes - you should still be eligible for stock OTA updates even with an unlocked bootloader - as far as I understand, the main thing the OTA checks is whether your recovery and kernel/system are stock and unmodified.
2) I didn't see any reports of that XT1643 update working for XT1644 devices - try this thread https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980 Looks like a few reports suggest the .48 firmware works.
3) If I recall, US firmwares don't have the right build versions for that Nougat soak (think US is ending in .48 or .64/65?), so that file may not work. Also, the soak tests available lead to a broken upgrade path - besides the 75.2 soak test, as I understand there are no other soak test updates available to bring you back onto the OTA update, meaning you'd have to flash another Nougat firmware.
If you still desire Nougat, perhaps try flashing the 93-11 (v7.0, Nov 2016 security update) or 93-14 (v7.0, Dec 2016 security update) stock ROMs; they are not the soak tests, rather they appear to be the full Nougat stock ROM. The 93-11 update also appears to be signed by Motorola (though not released by them through official channels) and possibly is the same for 93-14. Still, if you're interested: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 for the 93-11 and https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for 93-14. Also, if you flash these, you may omit 2) since you'll directly flash to Nougat.
4)Nougat 7.0 seems to be a mixed bag for many - though the OS appears to work well for some, others have mentioned lag, battery drain/heating issues with Nougat as well as some interface issues. Your experience may vary.
5) If you wish to move back to the official OTA channel updates once you've updated to Nougat, you may be lucky in that once Motorola releases the Nougat OTA, the released build may be 93-14, so any subsequent OTAs should flash okay (provided 1) is still applicable), since your installed build matches what the OTA expects for future updates.
If you wish to downgrade and then install the official OTA to ensure you have a verified firmware from Motorola, you may wish to downgrade to MM, then update via OTA. A guide like this may help (https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961) but ensure you do not downgrade your gpt or bootloader partitions else you risk damaging your phone - just omit those commands flashing either of those partitions. Someone correct me if I'm wrong, I think it's these commands you omit when downgrading:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Good luck either way
Click to expand...
Click to collapse
Thanks a lot bro @echo92
I actully followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 these steps now I'm running on stock nougat
Just omitted the bootloader unlock part since you told me that I'll be receiving updates even if the bootloader is unlocked

upgrading to nougat

Hi all,
I am using xt1643. I installed nougat sock test rom and it is not providing options to update to final nougat rom. Current build npj25.75-2
I read in a thread that downgrading can cause problems. So, what should i do: downgrade to marshmallow and then upgrade via ota or directly flash final nougat rom??
Thanks in advance.

ankit.hinsu said:
Hi all,
I am using xt1643. I installed nougat sock test rom and it is not providing options to update to final nougat rom. Current build npj25.75-2
I read in a thread that downgrading can cause problems. So, what should i do: downgrade to marshmallow and then upgrade via ota or directly flash final nougat rom??
Thanks in advance.
Click to expand...
Click to collapse
The 75-2 soak test update is a dead end unless you were on the official soak test program. I've not seen any further updates captured to allow you to formally upgrade via OTA to the official Nougat (currently build 93-14).
You could explore either option though:
1) Downgrade to MM, do not flash gpt partitions or bootloader (omit those commands) - you may find a signed stock ROM here: http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 (and the associated guide for downgrading: https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-downgrade-nougat-to-marshmallow-t3487201). Then update via OTA to Nougat. You may prefer this to ensure that your update comes directly from Motorola. EDIT: note this method will void your warranty.
2) Flash via fastboot/RSDLite either the 93-11 Nougat update (v7.0, Nov 2016 security update) https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612 and update to the latest version via OTA, or flash 93-14 (v7.0, Dec 2016) https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 This option is the more direct/less potential for things going wrong, it's up to you how much you'd trust the updates you flash. EDIT: This method does not appear to void your warranty.
With either option, back up your key data and be aware your settings and personal data may be erased in the process. Personally, I'd suggest a full wipe to limit the number of issues that may arise. Good luck though

You can now flash full stock roms with (the right) TWRP:
https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147
bootloader and partition table is not flashed with these zips

Hey @echo92 and @Droidphilev...
Can I use this method??
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296

ankit.hinsu said:
Hey @echo92 and @Droidphilev...
Can I use this method??
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Click to expand...
Click to collapse
No idea. Never done that. I use the flashable zips.

ankit.hinsu said:
Hey @echo92 and @Droidphilev...
Can I use this method??
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Click to expand...
Click to collapse
It appears to be the same method as one of the 93-11 methods I posted above: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Just bear in mind with using the 93-11 update to install it in India or somewhere we know that particular firmware has been released (and thus has an upgrade path to the latest 93-14 firmware) or download this 93-14 OTA update once you've updated to 93-11. https://forum.xda-developers.com/moto-g4-plus/how-to/ota-zip-update-npj25-93-14-t3539407

Thanks for the help....Followed the other link and successfully upgraded to Nougat full build 93-11 and then updated using OTA to 93-14.

NPNS version to NPN version

I am having xt1686 indian variant .. i unlocked the bootloader and installed the custom roms.. now while going back to stock i mistakenly installed NPNS (US VARIANT, I suppose) ..
I am unable to install the NPN version now .. i guess the bootloader is not matching ..
Right now i am having a bootloader - C0.8(*) in NPNS ...
PLEAAE SUGGEST HOW TO MOVE TO INDIAN VERSION OF NPN... THNKS..

S does not mean US or any other variant specific build... there are literally different builds for different variants. My US Retail version is NPN25.173-83
In previous Moto models, the S meant it had been upgraded from an OTA, but in looking in my current device it has received several OTAs and does not have the S, so either that has been depreciated or our original assumptions in earlier models was incorrect.
Either way, the fact the S is there does not mean US (or any other country), just a slightly different build... I don't have an answer of why you can't go back though.
https://forum.xda-developers.com/g5-plus/help/npns-nps-firmware-t3677576

Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/

abhi.a3s said:
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
Click to expand...
Click to collapse
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. If you've flashed a NPNS firmware, you'd likely be at least on the may security patch. The Indian firmware you'd need is the January patch (NPN25.137-15, as I don't think the NPN25.137-67 or 67-5 firmwares have been leaked). Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.

echo92 said:
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
Click to expand...
Click to collapse
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616

Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download

abhi.a3s said:
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457

echo92 said:
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Click to expand...
Click to collapse
Well ofcourse there is a big potential of hard bricking the device by the method. That's why I said last resort.
So what do you suggest?
TWRP image? And if it doesn't work, he should probably wait up for next NPN build? @toyesh.patra you should consider keeping a custom rom if possible.
Btw
The ota update which I received was August patch. After which I unlocked my bootloader. It was either NPN25.137-67 or NPN25.137-67-5. I'M not sure about version. But it was definitely August patch.
Or maybe I was lucky one time.
Won't do it another time.

anuraag.neo said:
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
Click to expand...
Click to collapse
For 1686? Full fastboot firmware leaked?

yea, right now i m using the 67-5 build using twrp..
although i wanted to use the 67-5 with locked bootloader.. nevermind ..

psychopac said:
For 1686? Full fastboot firmware leaked?
Click to expand...
Click to collapse
Yes

So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5

psychopac said:
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
Click to expand...
Click to collapse
Yes

I can't download it. How Can I download? please upload googel Thanks bro

birkhoffChang said:
I can't download it. How Can I download? please upload googel Thanks bro
Click to expand...
Click to collapse
use search function before asking
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738

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!!

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.