[Help Thread][Moto G4 Plus] (2016) Ask Any Question, Noob Friendly

[IronTechmonkey]

Hey guys I'm new here....but I need your hepl while giving permission using ADB my phone shows unauthorised device ....how can I fix this issue...I don't understand till now.. I have done several things live kill-server, start-server it didn't work for me ......is there any solution for this

It would be well worth your while to thoroughly research (elsewhere and here at XDA) of how to work with ADB, especially if you will be doing these things regularly (which you probably will), but for a quick walk-through:

- On Android device: Settings > Developer Options > Enable "Android debugging" and Debugging notify"
- Revoke USB debugging authorizations.*
- Make sure you are not at the moment running apps with "write over other apps" permissions. (eg LMT Pie) since on some devices that interferes with the ADB prompt on the device.
- Connect device to computer via USB (leaving the device powered on adn in the OS).
- Look for and acknowledge on the Android the ADB prompt to allow that computer.
- If the prompt does not appear then continue.

- If on PC open command prompt with administrative credentials at the ADB folder (If you open the command prompt elsewhere then ADB must be in your system path variable) then enter adb devices from

- If on Linux and assuming ADB is installed and OS knows where it is, open terminal anywhere and type "sudo adb devices", then enter you administrative credentials.

* Disclaimer: This will clear the history of devices which have been previously granted permissions to access the device by USB (and I'm not responsible for any consequent damage to your device or the universe).

 

[IronTechmonkey]

So I am back on stock ROM Latest Build NPJS25.93-14-18 with 1 April 2018 security patch on my XT1643. All seems to be working well, none of the problems faced in the trials of the past few months, SIM card is detected well after many reboots. Will revert back soon if something goes wrong. I used procedure as described on https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

Meanwhile, I will search for a debug method that I can use and will use it in the event the stock ROM works well so that issues can be reported on Jira appropriately for others to benefit.

Will prepare list of issues faced that were recurrent and common with RR as well. The stock ROM is resilient to abrupt power shutdown whereas the lineage OS requires a clean shutdown or else I have seen both RR and 14.1 weekly going into loops at animation stage due to abrupt shutdown / reboots.

I don’t want to sound like I don’t appreciate your efforts because it is nice to have these comparisons in general way but as it stands now they belong in a general thread like this one.

Please, until you reach the point of a establishing this (or anything else) as an actual LOS specific bug in an actual clean flash (where you have verified the steps taken) post in this thread and stop clogging the primary LOS 14.1 Athene development thread with stuff that is off effectively topic.

The frequency with which you are jumping between tests, the fact that you’ve not confirmed clean flash process (and have resisted doing so several times), and the fact that you've cited the very different installation and test process for stock rather than the logging instructions from the LOS thread are all indicators that you've not simply clean flashed LOS and removed all 3rd party variables.

P.S. Don't be put off by the words "General" and "noob"in this thread's title. Some very knowledgeable users follow this thread and may have helpful advise. More so than in the LOS thread because this thread is not just for one ROM, and nor are your reports from just one ROM. If demonstrate an LOS bug in a clean flash then bring it back to that thread.

Meanwhile in the LOS 14.1 Athene development thread I'm going to bump my recent and informative feedback regarding the confirmed LOS screen-on lag bug, which was buried by OT almost immediately after it was posted.

 

[IronTechmonkey]

Yes this is what I asked. Due to this mobile radio is consuming too much of battery

As mentioned in the LOS 14.1 Athene dev thread you can add notes to and follow the ticket to stay updated.

As to battery:

The fact that the data usage is recorded in the wrong category (folded into Android OS) is not a cause of more battery drain. That may make it harder for you to figure out what is draining battery but it is not itself the cause of the drain.

There are very many factors which are not part of the ROM which could cause increased battery drain. You should test to determine what is causing the drain. Apps such as Better Battery Stats (available on XDA and at Play Store) and Wakelock Detector (available in Play Store) as well as other apps might help you determine what is consuming battery. Also, the XDA Better Battery Stats thread is full of good advise and users knowledgeable about this stuff. https://forum.xda-developers.com/showthread.php?t=1179809. This thread may also be a good place to search for clues.

 

[Krishan94]

It would be well worth your while to thoroughly research (elsewhere and here at XDA) of how to work with ADB, especially if you will be doing these things regularly (which you probably will), but for a quick walk-through:

- On Android device: Settings > Developer Options > Enable "Android debugging" and Debugging notify"
- Revoke USB debugging authorizations.*
- Make sure you are not at the moment running apps with "write over other apps" permissions. (eg LMT Pie) since on some devices that interferes with the ADB prompt on the device.
- Connect device to computer via USB (leaving the device powered on adn in the OS).
- Look for and acknowledge on the Android the ADB prompt to allow that computer.
- If the prompt does not appear then continue.

- If on PC open command prompt with administrative credentials at the ADB folder (If you open the command prompt elsewhere then ADB must be in your system path variable) then enter adb devices from

- If on Linux and assuming ADB is installed and OS knows where it is, open terminal anywhere and type "sudo adb devices", then enter you administrative credentials.

* Disclaimer: This will clear the history of devices which have been previously granted permissions to access the device by USB (and I'm not responsible for any consequent damage to your device or the universe).

Thanks mate it works now ....

 

[IronTechmonkey]

FYI regarding possible direction in which to take the Athene LOS 14.1 reboot issues, a long standing Jira ticket watched by 20 people which seems as if it could be related, described and linked here: https://forum.xda-developers.com/showpost.php?p=76660319&postcount=2823.

 

[GuestD2494]

Hi all, I have a Moto G4 Plus XT1643 Android 7.0 running Android Security Patch level April 1,2018 initially. After checking various websites I chose to root my phone so that I could try out a custom ROM. I followed the following tutorial "https://devsjournal.com/how-to-root-moto-g4-moto-g4-plus.html" to root my phone. Before rooting the phone I fortunately took a Backup using TWRP with the following partitions checked-System, Data(excl. storage), Boot. After that I completed the procedure as per the before mentioned website; but the phone did not boot up. So I booted into TWRP and restored the Backup but and now the phone settings is showing Android 7.0 running Security Patch Feb 1, 2018 instead of the April Patch Level that was originally running when I took the backup. When I checked the root status it is saying my phone is still unrooted so I could not flash any custom ROM.

I went and downloaded the OTA software update April Patch which showed up as a notification and gave install. But on rebooting it keeps going into TWRP. I only understood later on that with TWRP recovery installed one should not give OTA update from the phone settings. I thought restoring the previous backup would solve the boot into TWRP issue and gave restore but the phone still boots into TWRP. Now I am manually giving START option from the bootloader mode to get Android running when ever I feel like restarting the phone.

So the present state of the phone = Bootloader unlocked, TWRP installed (twrp-3.2.1.0-athene.img), Build no:NPJS25.93-14-15 and NO ROOT access and running Android 7.0 with Security Patch level Feb 1,2018 .

Few questions, that I have before I end up doing something worse:
1) Without rooting my phone if I simply flash the stock recovery.img using the same method as before (fastboot cmd) will it remove TWRP and the Backup in the internal storage and bring the phone back to normal boot sequence for OTA updates? If yes, please note that the Motorola Support does not provide official stock recovery.img for my phone, then can I use the ones available in this forum and does the recovery file have any version dependency?
2) Or do I have to root my phone and then go for the laborious process of downloading the entire stock ROM and flashing it to get OTA?

Sorry for the lengthy post, after reading different threads in xda I am confused as to what step to take further to avoid the boot issue since my phone is still unrooted.

 

[echo92]

Hi all, I have a Moto G4 Plus XT1643 Android 7.0 running Android Security Patch level April 1,2018 initially. After checking various websites I chose to root my phone so that I could try out a custom ROM. I followed the following tutorial "https://devsjournal.com/how-to-root-moto-g4-moto-g4-plus.html" to root my phone. Before rooting the phone <snip for brevity - the post is above anyway>

So the present state of the phone = Bootloader unlocked, TWRP installed (twrp-3.2.1.0-athene.img), Build no:NPJS25.93-14-15 and NO ROOT access and running Android 7.0 with Security Patch level Feb 1,2018 .

Few questions, that I have before I end up doing something worse:
1) Without rooting my phone if I simply flash the stock recovery.img using the same method as before (fastboot cmd) will it remove TWRP and the Backup in the internal storage and bring the phone back to normal boot sequence for OTA updates? If yes, please note that the Motorola Support does not provide official stock recovery.img for my phone, then can I use the ones available in this forum and does the recovery file have any version dependency?
2) Or do I have to root my phone and then go for the laborious process of downloading the entire stock ROM and flashing it to get OTA?

Sorry for the lengthy post, after reading different threads in xda I am confused as to what step to take further to avoid the boot issue since my phone is still unrooted.

As a tip, if you wanted to flash a custom ROM, you do not require root whatsoever. You'd need an unlocked bootloader and the correct TWRP to flash the custom ROM.

It's odd that the backup you restored was the Feb 2018 security patch, is it possible you had another backup in addition to the April 2018 update? Since the backup was made before you rooted, it is expected you do not have root.

As for your questions:
1) Try this (I have not formally tried it, so be careful) https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 This should break the TWRP bootloop. If you wish to revert back to the stock recovery, you can find the recovery (pulled from the respective stock ROM): https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M If you've flashed the Feb 2018 firmware from your backup, I'd suggest flashing the Feb 2018 stock recovery, even if you were previously on the April 2018 firmware.
2)Alternatively, you do not have to root your device if you wish to re-flash the stock ROM for a clean start (or any ROM on our devices). If the above link doesn't work to break the bootloop, flashing the stock ROM should help.

The April 2018 NPJS25.93-14-18 stock ROM is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You may choose to use the following fastboot commands, instead of the commands in the stock ROM thread, if you wish to keep your bootloader unlocked and try to keep your data, but be aware that you may have to factory reset in case of instability. Thus, before using the following commands, I would recommend booting to TWRP and back up your TWRP backups and any important files on your internal storage. Then reboot to bootloader and begin flashing the stock ROM.

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

This should formally flash your device back up to NPJS25.93-14-18, it should also remove TWRP but you can re-flash that easily.

If you're still intent on rooting the stock ROM, please bear in mind that on stock Motorola Nougat, you must flash a custom kernel first before rooting. What that guide failed to mention is that those rooting steps work for stock Marshmallow, but under stock Nougat, the anti-rooting measures are much stricter. As such, attempting to root on the stock Motorola Nougat kernel will result in boot failures. If you flash a custom kernel such as ElementalX, that will make rooting straightforward (I'm rooted on NPJS25.93-14-18 with ElementalX 2.0.1 and magisk 16). Of course, this will make you ineligible for OTA updates unless you flash back the same stock ROM. However, with rooting or flashing custom ROMs, you may want a copy of the latest stock ROM to hand anyway. For rooting on stock Nougat, here's a guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You can substitute magisk for SuperSU depending on which root manager you prefer.

Again, you do not require root at all to flash a ROM (custom or otherwise) on our Moto G4/Plus devices to the best of my knowledge.

 

[IronTechmonkey]

I asked in this topic about this particular rom, so the question does not fit the generic section on the g4 plus device ... I believe that here in the section of this specific rom the users of this rom can give me a feedback on the use of this rom ... or was this topic created just to report the creation of the borderless rom to take questions from it?

The thread you posted in is a DEVELOPMENT thread focused on BUG TESTING in which general stuff is not suppose to go (and this is fairly obvious from the OPs of that thread which almost exclusively describe bug reporting methods). No decision of mine, that's just the the way it is, and this distinction is made in many forums including XDA.

Even though this thread is for Moto G4 in general and not specific to LOS, as I mentioned there are some knowledgeable people here who can advise you (including me) specifically about LOS. You can also search both threads for answers (an actual XDA rule) and search LOS jira for known bugs (https://jira.lineageos.org).

Additionally there are answers to your question about existing bugs (described in copious detail with linked references) in just the last few pages of the development thread, but if just you want a general review (which is a reasonable thing to seek) then please follow up here. That's what thread like this are specifically for. To that end I'll quote-post your original question, although it would be more efficient and easier for you to track replies if you did so yourself which is why I suggested it:

 

[IronTechmonkey]

@david.gs.gm asks:

Hello everyone ... I'm going to put this rom in my wife's cell ... but for that I wanted to know how the camera is ... wi-fi .... GPS ... sound ... and WhatsApp and Facebook ... that's what she uses .. even basic things.

[EDIT] From my experience with LOS on 2GB Moto G4 xt1625 (informed by comparison to 1GB Moto G3 Osprey and 1GB Moto G Peregrine):

Firstly, there is one potentially nasty bug where were spontaneous reboots occur. It's clear that this is an LOS Athene specific issue, but it affects devices in different usage scenarios to varying degree, and no one has pinned it down. Some people report frequent reboots while others report none. When there was a SIM in my Athene device it occured a few over a few months, and when there was no SIM it did not occur over several months. This in particular was the issue that has been "copiously reported" and it is worth reviewing those references. If your device experiences this issue then you might not want it hand it off to someone else. On the other hand if your device does not experience this, most other issues are probably not "deal-breakers".

One other issue is a delay between power button press and display on. This issue does not seem to be as prevalent as the aforementioned but is real, and device specific, and possibly LOS specific. This is another issue for which there have been detailed reports worth reviewing.

Camera: The LOS camera is, IMO not LOS' finest feature and I understate. On 1GB devices in general, and particularly for panorama pictures, it has an impact on RAM (background services may FC). On my 2GB Athene device it performs OK but not as well as some other cameras. Fortunately some of the stock Moto cameras are available (XDA and other places) as backup or even primary camera.

Wifi: Works well for me but I'm usually on the same home wifi network which does not speak for many aspects.

GPS, seems to work fine. It usually takes a few minutes longer to get a device-only GPS fix on my Athene than Osprey or Peregrine but AFAIK no worse than stock and not so much longer that it is a hindrance (in my usage case).

Sound: Seems quite good but this is a highly subjective measure.

Whatsapp People have reported but not clearly established some type of issue with whatsapp which may have been fixed. I don't use Whatsapp but have seen those references. They are worth researching.

Facebook: Could not say.

In general: Without casting an criticism at the device maintainer, among my 3 devices running LOS 14.1 this one seems to have the least presence for device specific bug fixes at LOS Jira but still benefits from the general work-flow. Maybe the focus is shifting to LOS 15, as is the case for many devices.

Considering the 2 established issues mentioned above if you are handing it off to someone else you might want to test if for a while first (at least several days). On that note... "Try it yourself" is a common response (not just from me) to "how does it perform" questions in development threads. You may not have liked being asked to go here but it was the appropriate thing to do and enabled a more helpful response.

 

[GuestD2494]

As a tip, if you wanted to flash a custom ROM, you do not require root whatsoever. You'd need an unlocked bootloader and the correct TWRP to flash the custom ROM.

It's odd that the backup you restored was the Feb 2018 security patch, is it possible you had another backup in addition to the April 2018 update? Since the backup was made before you rooted, it is expected you do not have root.

As for your questions:
1) Try this (I have not formally tried it, so be careful) https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 This should break the TWRP bootloop. If you wish to revert back to the stock recovery, you can find the recovery (pulled from the respective stock ROM): https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M If you've flashed the Feb 2018 firmware from your backup, I'd suggest flashing the Feb 2018 stock recovery, even if you were previously on the April 2018 firmware.
2)Alternatively, you do not have to root your device if you wish to re-flash the stock ROM for a clean start (or any ROM on our devices). If the above link doesn't work to break the bootloop, flashing the stock ROM should help.

The April 2018 NPJS25.93-14-18 stock ROM is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You may choose to use the following fastboot commands, instead of the commands in the stock ROM thread, if you wish to keep your bootloader unlocked and try to keep your data, but be aware that you may have to factory reset in case of instability. Thus, before using the following commands, I would recommend booting to TWRP and back up your TWRP backups and any important files on your internal storage. Then reboot to bootloader and begin flashing the stock ROM.

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

This should formally flash your device back up to NPJS25.93-14-18, it should also remove TWRP but you can re-flash that easily.

If you're still intent on rooting the stock ROM, please bear in mind that on stock Motorola Nougat, you must flash a custom kernel first before rooting. What that guide failed to mention is that those rooting steps work for stock Marshmallow, but under stock Nougat, the anti-rooting measures are much stricter. As such, attempting to root on the stock Motorola Nougat kernel will result in boot failures. If you flash a custom kernel such as ElementalX, that will make rooting straightforward (I'm rooted on NPJS25.93-14-18 with ElementalX 2.0.1 and magisk 16). Of course, this will make you ineligible for OTA updates unless you flash back the same stock ROM. However, with rooting or flashing custom ROMs, you may want a copy of the latest stock ROM to hand anyway. For rooting on stock Nougat, here's a guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You can substitute magisk for SuperSU depending on which root manager you prefer.

Again, you do not require root at all to flash a ROM (custom or otherwise) on our Moto G4/Plus devices to the best of my knowledge.

Dear echo92,
Thank you for the fast reply. I will certainly look into both options thoroughly. I am a little busy this weekend. I will post the updated status soon. Thanks again. Also I was under the misconception that a phone has to be rooted first to flash custom roms, since almost all tutorials use the rooting method. Thank you for clearing up that misunderstanding.

Update :
Hi,
I downloaded the stock recovery with correct build number (the stock recovery file obtained from the link to the drive you posted) for the Feb Patch and gave the command "fastboot flash recovery recovery.img". I thought this will replace the TWRP with stock recovery so OTA update will happen on its own. The boot into TWRP problem is solved

However now when I give the ota update the installing update animation is shown for some time and then the screen changes to simply error. I tried rebooting the phone again and giving the ota update but same error is shown.

Image : https://imgur.com/GsuRy7r

On booting along with the "bootloader is unlocked" message of motorola, now it is showing "ID: bad key".

Is this because of some difference in the recovery like being from not for the India region or something?
Is it safe to give a factory reset with this new recovery installed?

 

[ezezap]

Did a lost my phone???

Hi, sorry to bother you but I can't find anyone with a similar problem/solution to this, I was updating by OTA my XT1641 and It get stucked in a boot loop, every single option in Fastboot mode (except Power OFF) leads to bootloop again. Anyone knows how to solve this???
I have tried with all options available in fastboot, bootloop response only
I tried with ADB and some different ROMs, bootloop again...

 

[Dhanush-raj]

Hi, sorry to bother you but I can't find anyone with a similar problem/solution to this, I was updating by OTA my XT1641 and It get stucked in a boot loop, every single option in Fastboot mode (except Power OFF) leads to bootloop again. Anyone knows how to solve this???
I have tried with all options available in fastboot, bootloop response only
I tried with ADB and some different ROMs, bootloop again...

Read 1 page back echo92 has given two ways to fix your issue.. Hope so it helps.

https://forum.xda-developers.com/mo...-question-noob-friendly-t3526598/post76681434

 

[StevenFernandes]

Hello guyz, I'm running into really weird issue. My phone suddenly shuts down at around 50% and then it refuses to boot and shows 'it cannot be started because of low battery' (even if my phone is at 50%). Then i have to plug it to a charger and it boots properly.

Model: xt1643
Rom: Stock Nougat, RR 6, RR 5.8 (experienced this issue on these 3)

 

[echo92]

Hello guyz, I'm running into really weird issue. My phone suddenly shuts down at around 50% and then it refuses to boot and shows 'it cannot be started because of low battery' (even if my phone is at 50%). Then i have to plug it to a charger and it boots properly.

Model: xt1643
Rom: Stock Nougat, RR 6, RR 5.8 (experienced this issue on these 3)

Hmm, if you've experienced this on the stock ROM as well, that suggests the battery or another issue with the hardware. Have you looked into getting the battery replaced? Could be the battery isn't holding a charge or not outputting enough power (as an aside, it's an issue which affects many devices over time, e.g. https://www.howtogeek.com/342185/how-to-disable-your-iphones-cpu-throttling-in-ios-11.3/ ) which would also explain why your device boots okay with supplied power.

 

[StevenFernandes]

Hmm, if you've experienced this on the stock ROM as well, that suggests the battery or another issue with the hardware. Have you looked into getting the battery replaced? Could be the battery isn't holding a charge or not outputting enough power (as an aside, it's an issue which affects many devices over time, e.g. https://www.howtogeek.com/342185/how-to-disable-your-iphones-cpu-throttling-in-ios-11.3/ ) which would also explain why your device boots okay with supplied power.

I was wondering the same thing, it might be the battery that is nt holding the charge (as this device is 2 yrs old). Thanks for the help.

 

[meetXD]

It's been a while since my headphone jack stopped detecting when anything was plugged in.

Until now, I was getting along fine using an app called SoundAbout to force route audio to the headphone jack, but the app doesn't work with Android Oreo.

I'd love it if someone would provide a script I can run with tasker (or similar) that I can use to enable and disable forced audio routing.

Only then can I finally update my Rom!

Thanks!

 

[rahulsj92]

Offline charging

Guys, how do I use offline charging in Oreo ROMs? My phone has some problem with it's charging point and I don't want to spend any money on it. Whenever the phone goes below 15% no matter what I do(airplane mode, recovery mode, bootloader, switched off), it never climbs over 15%. When I try to charge it switching off, it restarts and then due to low battery switches off. This vicious cycle drains battery. I read somewhere on XDA that offline charging is required for this. This issue prevails over all 64bit ROMs. Please help.

 

[sd_shadow]

Guys, how do I use offline charging in Oreo ROMs? My phone has some problem with it's charging point and I don't want to spend any money on it. Whenever the phone goes below 15% no matter what I do(airplane mode, recovery mode, bootloader, switched off), it never climbs over 15%. When I try to charge it switching off, it restarts and then due to low battery switches off. This vicious cycle drains battery. I read somewhere on XDA that offline charging is required for this. This issue prevails over all 64bit ROMs. Please help.

It should charge in bootloader mode.

Sent from my PH-1 using Tapatalk

 

[squirvel]

So this is a strange one: I have twrp flashed and whatnot, and am (or rather was) trying to sideload on a rom. In device manager (win7 x64) the phone appears as an unknown device as "omni_athene". A couple google searches for drivers is turning out blank (and while I just ended up copying the file), having a useable sideload would be quite nice. Any ideas on what to do?

 

[echo92]

Dear echo92,
Thank you for the fast reply. I will certainly look into both options thoroughly. I am a little busy this weekend. I will post the updated status soon. Thanks again. Also I was under the misconception that a phone has to be rooted first to flash custom roms, since almost all tutorials use the rooting method. Thank you for clearing up that misunderstanding.

Update :
Hi,
I downloaded the stock recovery with correct build number (the stock recovery file obtained from the link to the drive you posted) for the Feb Patch and gave the command "fastboot flash recovery recovery.img". I thought this will replace the TWRP with stock recovery so OTA update will happen on its own. The boot into TWRP problem is solved

However now when I give the ota update the installing update animation is shown for some time and then the screen changes to simply error. I tried rebooting the phone again and giving the ota update but same error is shown.

Image : https://imgur.com/GsuRy7r

On booting along with the "bootloader is unlocked" message of motorola, now it is showing "ID: bad key".

Is this because of some difference in the recovery like being from not for the India region or something?
Is it safe to give a factory reset with this new recovery installed?

Apologies for the late reply - I didn't see the edit.

As for your experience - did you end up flashing the full stock ROM? That error may be as a result of modifications made whilst flashing TWRP and attempting to root, which may cause the OTA to error out. One option as I mentioned previously is to full flash the stock ROM - unfortunately, simply replacing TWRP with stock recovery does not sometimes work in fixing OTA errors. Thus, you might have to restore your device to a clean, unmodified status before taking OTA updates (bootloader unlocked status does not matter). Ensure that you're flashing the latest stock ROM available (the latest leaked firmware is NPJS25.93-14-18, April 2018 https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 )

ID bad key is normal if you've tried to flash stock firmware/OTA updates. On subsequent updates, that should change to ID:N/A.

That recovery is for the India region, as it was part of the firmware released to Brazil, India and EU/UK regions (same goes for NPJS25.93-14-18).

If you really want to, I see no harm in a factory reset with the new stock recovery, however, you will lose your data. I would honestly recommend flashing back the stock ROM as I described previously and then attempt to use the OTA updates. I've performed this flash back of the stock ROM and have had few issues installing OTA updates. Alternatively, flash the NPJS25.93-14-18 firmware as I suggested and forget about using the OTA update this time.