Database Users

After flashing phone changed from G4 Plus to G4

I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.

You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695

That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.

Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.

GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.

sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.

Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !

sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...

bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.

bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410

Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar

gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.

echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes

gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.

gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410

echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch

gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.

echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands

Moto g4 plus turned moto g4 help

Guys help me in this
Okay i have flashed moto g4 plus (43) firmware which was not for moto g4 plus now my phone say its moto g4 and fingerprint doesn't work ,
Even if i try to install some custom rom the network gone and shows only single sim with no network tried different firmware and rom nothing happened
But if i restore my previous backup my phone works normal except fingerprint and it says moto g4
I was wondering that my friend also have g4 plus
Can i create a backup of his phone and install it in mine and how do i get the whole backup of firmware
And also one thing which file contains the fingerprint or model name in firmware file

Better flash the latest complete firmware for your device via fastboot: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
The modem file is NON-HLOS.bin although :good:

Can Anyone downgrade moto g4 plus bootloader

okay first i flashed the wrong firmware which was quoted as moto g4 plus firmware huh now my phone is moto g4 and whenever i format mt phone it shows single sim no network and no fingerprint after a lot of research i fount that my bootloader version is changed
BL: BOE(*) Sha-4986429
i think it should be - BL: B1.03
do anyone knows hot to flash the write bootloader
and pls dont comment flash the correct firmware ****

fastboot flash bootloader bootloader.img
Flash the latest one don't downgrade it can brick your phone
Sent from my Moto G4 Plus using Tapatalk

The only way, as far as I know, to flash a bootloader is to flash one from stock firmware.
Assuming you were on MM, you can try to flash the MPJ23.139-23.1 build (which i think is for XT1643) or flash the MPJ24.139-63 build for XT1643 devices https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 , and that may repair your bootloader and IMEI/fingerprint sensor. As Blackbeats has mentioned, you may have to flash a Nougat bootloader if you were on a stock Nougat ROM at some point - and looking at the bootloader version (B1.03), I think that you'll want the Nougat NPJ25.93-14 stock ROM bootloader to flash back to: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
However, there is a chance that in future, because of the bootloader, future updates may be problematic (to the point where a brick could be possible), incidentally, for anyone watching this post, don't downgrade your bootloader or GPT partitions if you're downgrading your system!
Also as ____Mdd has mentioned in your other post, flashing firmwares may not repair your system as the hw partition may have been corrupted/wiped. The hw partition appears to hold details about your device and what properties to assign, and up until recently we didn't know that (and we seem to be able to fix it - details in this post as mentioned: https://forum.xda-developers.com/showpost.php?p=72340548&postcount=98 . You may be able to get assistance if you post in this thread to repair your XT1643.
Failing those, as has also been mentioned, a service centre and motherboard replacement may be required.

CEDRIC_NPPS25.137-72-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Download full fw.
BUILD REQUEST INFO:
SW Version: cedric-user 7.0 NPPS25.137-72-4 4 release-keysM8937_11.16.02.51R
MBM Version: B8.23
Modem Version: M8937_11.16.02.51R
FSG Version: FSG-8937-02.65.05
Build Fingerprint: motorola/cedric/cedric:7.0/NPPS25.137-72-4/4:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.246.4.cedric.retail.en.US
Model number: Moto G (5)
Android Version: 7.0
Baseband Version: M8937_11.16.02.51R
Build Number: cedric-user 7.0 NPPS25.137-72-4 4 release-keys
Build Date: Fri Aug 4 04:22:37 CDT 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.246.4.cedric.retail.en.US
Version when read from CPV: cedric-user 7.0 NPPS25.137-72-4 4 release-keys
CEDRIC_NPPS25.137-72-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

What is that?
Sent from my Moto G (5) using Tapatalk

fxdRoiD said:
What is that?
Sent from my Moto G (5) using Tapatalk
Click to expand...
Click to collapse
It's the last available fw for XT1676. NPPS25.137-72-4
https://forum.xda-developers.com/g5/help/stock-rom-moto-g5-xt1676-3-16-dualsim-t3696622
Haven't seen it anywhere untill now when I got a link that was valid for just a few hours, so I thought I should download it and share it.

Is this rom work for moto g5 model XT1677 Indian varient Amazon exclusive ?? If yes voLTE is working or not ??

Anyone have NPPS25.137-79-3 for the XT1670?
Sent from my Moto G5 using Tapatalk

It can relock bootloader?

When I try to install this from TWRP I'm getting an "Invalid zip file format!" error and it refuses to.
Any thoughts on why this could be? Would it be a bad idea to use fastboot to execute all the instructions in flashfile.xml?
I'm trying to install this to rid myself of a stubborn TWRP bootloop (wasn't fixed by e.g. reflashing twrp) and to do an OEM update before trying to restore TWRP, no-verity, Magisk, and my nandroid backup.
My XT1676 currently has TWRP and Magisk. Its settings indicate build number NPPS25.137-72-4, software channel reteu, and baseband version M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST.

macho_ said:
When I try to install this from TWRP I'm getting an "Invalid zip file format!" error and it refuses to.
Any thoughts on why this could be? Would it be a bad idea to use fastboot to execute all the instructions in flashfile.xml?
I'm trying to install this to rid myself of a stubborn TWRP bootloop (wasn't fixed by e.g. reflashing twrp) and to do an OEM update before trying to restore TWRP, no-verity, Magisk, and my nandroid backup.
My XT1676 currently has TWRP and Magisk. Its settings indicate build number NPPS25.137-72-4, software channel reteu, and baseband version M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST.
Click to expand...
Click to collapse
To start off with this is a stock firmware - stock firmware is flashed via fastboot and not twrp using fastboot commands
secondly - if you are talking about your phone booting into twrp instead of booting to system you obviously didn't read the FAQs on my TWRP thread as the answer is there
How to flash stock firmware
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737

This is great: my searches hadn't previously led me to either of those threads, thanks.
The TWRP bootloop solution seemed to work, although after I tried do the Nov OTA update, I got back into the bootloop and the update failed. Presumably I could have just repeated the fix again.
But instead of doing that, I flashed the stock image above using fastboot. On rebooting I initially got a scary robot-with-its-front-panel-open error that just said "Error!" When I tried to reboot to recovery I got the same robot with "No command". But then weirdly it soon just booted normally on its own. From there the most recent (November) OTA update finally installed without issue, then I restored twrp, magisk, no-verity-opt-encrypt, and finally the data partitions of a backup I made before starting everything above.
I'm really happy about this: these problems had been plaguing me for a while. Thanks again.

macho_ said:
This is great: my searches hadn't previously led me to either of those threads, thanks.
The TWRP bootloop solution seemed to work, although after I tried do the Nov OTA update, I got back into the bootloop and the update failed. Presumably I could have just repeated the fix again.
But instead of doing that, I flashed the stock image above using fastboot. On rebooting I initially got a scary robot-with-its-front-panel-open error that just said "Error!" When I tried to reboot to recovery I got the same robot with "No command". But then weirdly it soon just booted normally on its own. From there the most recent (November) OTA update finally installed without issue, then I restored twrp, magisk, no-verity-opt-encrypt, and finally the data partitions of a backup I made before starting everything above.
I'm really happy about this: these problems had been plaguing me for a while. Thanks again.
Click to expand...
Click to collapse
The robot is stock recovery - hold Vol up & press power button I think to access its menu but all you can really do is a factory reset

Can i install this on 1675 variant?
My bootloader is locked

can I flash stock ROM - with the same patch but another channel (from retin to retus) on a device with a locked bootloader?
if yes, how can I do that? from adb fastboot? RSD lite?

TheFixItMan said:
To start off with this is a stock firmware - stock firmware is flashed via fastboot and not twrp using fastboot commands
secondly - if you are talking about your phone booting into twrp instead of booting to system you obviously didn't read the FAQs on my TWRP thread as the answer is there
How to flash stock firmware
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
Click to expand...
Click to collapse
My phone is Moto g5 cedric with NPP25.137-72 android 7.0 this flash update but I want to flash oreo directly, you know about this???

rosel11078 said:
My phone is Moto g5 cedric with NPP25.137-72 android 7.0 this flash update but I want to flash oreo directly, you know about this???
Click to expand...
Click to collapse
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section

TheFixItMan said:
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
Click to expand...
Click to collapse
OK so, I have to flash latest offcial stock and apply update oreo then???

TheFixItMan said:
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
Click to expand...
Click to collapse
Do you know what is the lastest flashable firmware for moto g5 cedric 32gb 2ram xt1670 NPP25.137.72????
That will allow me to upgrade Oreo????

CEDRIC_NPPS25.137-93-2-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Can't turn on moto g4 plus

I cannot turn on moto g4 plus. While connecting the charger the led is blinking but cannot see the charging sign on screen. Please help

What ROM were you running and what device do you have?
Did you flash anything or install anything prior to your device being in this state?

echo92 said:
What ROM were you running and what device do you have?
Did you flash anything or install anything prior to your device being in this state?
Click to expand...
Click to collapse
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643

Krish_Vihaag said:
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643
Click to expand...
Click to collapse
Sounds like you bricked it cause you take ota on stock rom and you don't have stock recovery I think... You should try to flash the stock rom via fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Your information about what you did isn't exactly enough to provide a detailed troubleshooting. If you have more detailed information which steps you exactly take and which rom versions you restored etc it would be helpful.

Krish_Vihaag said:
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643
Click to expand...
Click to collapse
Do you remember what version of stock ROM you had when you flashed AICP ?
I don't think you had December's security patch as itis just month old, so you can try blank-flash with September's patch update.
to blank-flash (download September's gpt and bootloader, where it's mentioned on thread)
Follow it.: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
EDIT: Before proceeding to blank-flash, can you tell us if you have access to bootloader or recovery ?
If not, then proceed for blank-flash.

After flashing my phone with Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock Img, I tried to update the April 2018 security patch. After that my phone doesn't start. Then I use blank flash and my phone starts with recovery mode. Now the problem is when I try to flash my phone again, it say security version downgrade and FAILED. Can you guys please help me into this?

Mayur Thakur said:
After flashing my phone with Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock Img, I tried to update the April 2018 security patch. After that my phone doesn't start. Then I use blank flash and my phone starts with recovery mode. Now the problem is when I try to flash my phone again, it say security version downgrade and FAILED. Can you guys please help me into this?
Click to expand...
Click to collapse
Sounds like you flashed the Dec 2016 security patch firmware, and then took an OTA - the OTA update on a downgraded firmware likely is what hard bricked your device.
Flash this April 2018 stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
In future, please do not flash older stock firmware, or if you do downgrade, please do not use OTA updates. The safest way to update is to flash the latest stock firmware for your device/region - after that, OTA updates may be safe.

MOTO G4 plus stock rom
MOTO G4 plus will get OREO update officially so I flashed latest firmware via fastboot on my phone so can update it through ota update when it will be able without bricking my phone or else when it comes I should download the zip and flash it with fastboot with step same step of flahsing nougat forward on my phone

Gaminwarrior said:
MOTO G4 plus will get OREO update officially so I flashed latest firmware via fastboot on my phone so can update it through ota update when it will be able without bricking my phone or else when it comes I should download the zip and flash it with fastboot with step same step of flahsing nougat forward on my phone
Click to expand...
Click to collapse
Nobody can tell you about future things, but in my opinion it should be like this.