Database Users

XT-1644 Official Nougat Update?

My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png

You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.

echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?

waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612

echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.

waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.

Can I Update further upcoming security patch

Hi everyone When I am Rooted My Moto G4 Plus and install custom rom thn i downgrade to Official 7.0 with Dec 2016 Security Patch Update and when i try to Official OTA update of march 2017 with unlock bootloader but my phone goes hardbrick than via "blank flash" now i am on Official stock June 2017 security patch update and i Relocked my bootloader.....So My Question Is can i Update Further Upcoming Security patch or any official OTA update..??? Or My phone get Hardbrick????? Plz reply....

pritesh barot said:
Hi everyone When I am Rooted My Moto G4 Plus and install custom rom thn i downgrade to Official 7.0 with Dec 2016 Security Patch Update and when i try to Official OTA update of march 2017 with unlock bootloader but my phone goes hardbrick than via "blank flash" now i am on Official stock June 2017 security patch update and i Relocked my bootloader.....So My Question Is can i Update Further Upcoming Security patch or any official OTA update..??? Or My phone get Hardbrick????? Plz reply....
Click to expand...
Click to collapse
I have same question ,but I'm asking you can I unlock bootloader again

1) You can unlock the bootloader again, each time will wipe your device however. I think you can use the same unlock code as issued by Motorola (provided nothing has changed with your device hardware - i.e. you have the same motherboard).
2)As I mentioned in the other thread, if you've hard bricked and you flashed the June 2017 stock ROM in its entirety - all commands and wipes, then you may be okay to accept and install OTA updates. This is dependent on you having flashed all parts of that stock ROM, so your device is at the same patch level - if you have not, then taking the OTA might hardbrick you again. The OTA updates do not necessarily include complete files, they mainly are a collection of patches, and assume your device is at the same patch level (GPT, bootloader, system, kernel, and other firmware are all at the June 2017 patch level, for example).
If you're worried at all about the OTA updates, wait for an updated fastboot stock ROM with the included update, which is safer.
3)Once you've taken any OTA updates newer than June 2017, it is no longer safe to attempt to flash the June 2017 stock ROM - if you want to go back to stock, wait for an updated stock ROM to be leaked. Else, you could downgrade (which I do not recommend), but do not accept OTA updates. Our newest blankflash works on B1:06 bootloaders, I do not know if it works on newer bootloaders. If not, and you hard brick, you'll likely have to wait for a new blankflash or pay for a new motherboard. A new motherboard is around 7000-10000 rupees or your regional equivalent, from what I've seen.

echo92 said:
1) You can unlock the bootloader again, each time will wipe your device however. I think you can use the same unlock code as issued by Motorola (provided nothing has changed with your device hardware - i.e. you have the same motherboard).
2)As I mentioned in the other thread, if you've hard bricked and you flashed the June 2017 stock ROM in its entirety - all commands and wipes, then you may be okay to accept and install OTA updates. This is dependent on you having flashed all parts of that stock ROM, so your device is at the same patch level - if you have not, then taking the OTA might hardbrick you again. The OTA updates do not necessarily include complete files, they mainly are a collection of patches, and assume your device is at the same patch level (GPT, bootloader, system, kernel, and other firmware are all at the June 2017 patch level, for example).
If you're worried at all about the OTA updates, wait for an updated fastboot stock ROM with the included update, which is safer.
3)Once you've taken any OTA updates newer than June 2017, it is no longer safe to attempt to flash the June 2017 stock ROM - if you want to go back to stock, wait for an updated stock ROM to be leaked. Else, you could downgrade (which I do not recommend), but do not accept OTA updates. Our newest blankflash works on B1:06 bootloaders, I do not know if it works on newer bootloaders. If not, and you hard brick, you'll likely have to wait for a new blankflash or pay for a new motherboard. A new motherboard is around 7000-10000 rupees or your regional equivalent, from what I've seen.
Click to expand...
Click to collapse
Now I Hve Successfully Relock My Bootloader and now i am on stock June 2017 Can I Reflash With Same June 2017 without Unlocking Bootloader Again because during Relock i used Command Directly From X Da Thread For Relock Bootloader and Don't Sure Fully Install June 2017 Rom So Want To Reflash With 'Stock Flash.Bat' File So I Will Get OTA Without Waiting For Updated Fastboot Stock Rom....So Can I Flash June 2017 Without Unlocking Bootloader....??? Plz Reply...

pritesh barot said:
Now I Hve Successfully Relock My Bootloader and now i am on stock June 2017 Can I Reflash With Same June 2017 without Unlocking Bootloader Again because during Relock i used Command Directly From X Da Thread For Relock Bootloader and Don't Sure Fully Install June 2017 Rom So Want To Reflash With 'Stock Flash.Bat' File So I Will Get OTA Without Waiting For Updated Fastboot Stock Rom....So Can I Flash June 2017 Without Unlocking Bootloader....??? Plz Reply...
Click to expand...
Click to collapse
Can I Reflash With Same June 2017 without Unlocking Bootloader - yes, the stock ROMs we have access to should be signed by Motorola, so should flash on a locked or unlocked bootloader regardless.
You should be able to get OTA updates without waiting for an updated stock ROM. From your previous posts, you seem unsure of this. It is still up to you and your responsibility whether you choose to take an OTA or wait for the updated stock ROM. If you re-locked your bootloader, then you must have been able to re-flash the entire stock ROM, else you may have failed to boot (as you'd have likely failed the verification checks performed by a locked bootloader). Thus, your device might be okay to update. Again, as I have mentioned previously in replies to your posts, if you are worried about hard bricking, then wait for the updated fastboot ROM. The updated fastboot ROM has complete files and thus has a lower risk of damaging/bricking your device. I understand you're eager to get the latest OTA updates, however you could wait and see if there are any bugs/outstanding issues before updating.
Depending on the commands in that stock flash.bat file, you may wipe your device, so back up accordingly.
As an aside, how are you not sure you flashed the full stock ROM? Surely if you followed the guide and used all the commands, you'd have fully flashed? If you look in the stock flash.bat script (open it in Notepad or a text viewer), you'll note the commands should be the same as what you used previously?

Software update problem

I reinstalled the stock os .. unrooted .. And booted up my phone .. everything works perfectly ..but when I tried to update from December to Feb security update ..the phone got hard bricked ...I did the blank flash and got it working ...I didn't try to update again ...so I don't know whether I should update to September update or not .. someone please help

First thing, Motorola does NOT support downgrading. What you did was you flashed the December update over some custom ROM you were using which in turn downgraded your bootloader and gpt partitions. Then you took OTA again which bricked your device.
You should always make sure that when you flash the stock ROM, you only flash the latest version available on XDA, in this case the June security update(NPJS25.93-14-8).
In case you flash any previous build of stock ROM DON'T flash the bootloader and gpt partitions (just ignore those two fastboot commands).
So what should you do now?
The link to the June security update full fastboot ROM : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash this one using the scripts provided. Then take the September OTA. Things should go fine now if you follow the steps carefully.

Swapnanil said:
First thing, Motorola does NOT support downgrading. What you did was you flashed the December update over some custom ROM you were using which in turn downgraded your bootloader and gpt partitions. Then you took OTA again which bricked your device.
You should always make sure that when you flash the stock ROM, you only flash the latest version available on XDA, in this case the June security update(NPJS25.93-14-8).
In case you flash any previous build of stock ROM DON'T flash the bootloader and gpt partitions (just ignore those two fastboot commands).
So what should you do now?
The link to the June security update full fastboot ROM : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash this one using the scripts provided. Then take the September OTA. Things should go fine now if you follow the steps carefully.
Click to expand...
Click to collapse
Thank you soo much ...I'll try this ?

I'd like to add a correction to what's been mentioned so far.
I agree that you likely hard bricked from flashing an older stock ROM than what you had on your device already. However, the act of downgrading your device may not cause a brick, but by downgrading you may not be able to flash an older GPT/bootloader as they detect a 'security version downgrade' and block you from flashing the older versions of the GPT/bootloader. However, as you were able to flash the system side of the firmware, then you'd have the mismatch of a newer bootloader (likely B1:06 from the June 2017 stock update?) and an older system from the December 2016 patch.
Now, when you accepted and downloaded the OTA, the OTA assumed that your device is fully patched to the December 2016 security level and was all on the same patch level, which by downgrading your device was not. OTAs appear to check if your system and OEM and other partitions are of the expected patch level and do not necessarily verify that your GPT and bootloader are matching too. Thus, when it attempted patching to upgrade your device to the March 2017 patch, it applied updates to your bootloader and thus corrupted your newer bootloader, leading to a hard brick.
That's a reason why downgrading and updating by OTA updates is so risky now. Therefore, if you've downgraded, do not update via OTA.
I agree with the suggestion that you should use the full fastboot ROM, (you may wish to omit the 'erase userdata' command) to ensure your device is fully flashed to the same patch level. We've now got the September 2017 fastboot ROM to flash too if you're unsure about taking OTA updates.
In future, verify what stock firmware you had on your device before you flashed a custom ROM, and ensure you flash the firmware of the same patch level.

echo92 said:
I'd like to add a correction to what's been mentioned so far.
I agree that you likely hard bricked from flashing an older stock ROM than what you had on your device already. However, the act of downgrading your device may not cause a brick, but by downgrading you may not be able to flash an older GPT/bootloader as they detect a 'security version downgrade' and block you from flashing the older versions of the GPT/bootloader. However, as you were able to flash the system side of the firmware, then you'd have the mismatch of a newer bootloader (likely B1:06 from the June 2017 stock update?) and an older system from the December 2016 patch.
Now, when you accepted and downloaded the OTA, the OTA assumed that your device is fully patched to the December 2016 security level and was all on the same patch level, which by downgrading your device was not. OTAs appear to check if your system and OEM and other partitions are of the expected patch level and do not necessarily verify that your GPT and bootloader are matching too. Thus, when it attempted patching to upgrade your device to the March 2017 patch, it applied updates to your bootloader and thus corrupted your newer bootloader, leading to a hard brick.
That's a reason why downgrading and updating by OTA updates is so risky now. Therefore, if you've downgraded, do not update via OTA.
I agree with the suggestion that you should use the full fastboot ROM, (you may wish to omit the 'erase userdata' command) to ensure your device is fully flashed to the same patch level. We've now got the September 2017 fastboot ROM to flash too if you're unsure about taking OTA updates.
In future, verify what stock firmware you had on your device before you flashed a custom ROM, and ensure you flash the firmware of the same patch level.
Click to expand...
Click to collapse
Thank you for your help !!!!!!!

[SOLVED] Stuck on BlankFlash (February 2018 Update)

Greetings XDA!
My moto g4 plus (xt1643) is stuck on the BlankFlash dummy bootloader screen.
Here's the sequence of events.
1. Stock Moto g4 plus.
2. Rooted, unlocked bootloader, flashed
Code:
Lineage-14.1
along with
Code:
ElementalX-G4-1.04
3. All worked fine. Decided to move to Oreo.
4. Reset phone, restore to stock. All went well.
5. Rooted, unlocked bootloader, flashed
Code:
Cardinal-AOSP-5.3.1-OREO-athene-OFFICIAL-20180106
along with
Code:
open_gapps-arm64-8.1-micro-20180119-UNOFFICIAL
using recovery
Code:
twrp-3.2.1-r2-arm64-tywinlannister7.img
6. Some apps did not work. Decided to revert back to stock.
7. Back to stock. All good.
8. Installed OTA Update (40.7 MB). Device hard bricked.
9. Used the
Code:
[GUIDE] Moto G4 Plus HardBrick SOLVED - ULTIMATE UNBRICKING GUIDE
.
10. BlankFlash successful.
11. Device online in dummy bootloader fastboot.
12. Cannot flash anything hereafter.
On trying to flash partition, error received is :-
Code:
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
Someone created a video for the same. Here's the link to the YouTube video:
/watch?v=m2NqpY6X-X4
I am stuck on the first step at 8:22.
Any help would be greatly appreciated.

Bro... you could have searched, before creating a thread for it... https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
All the discussion is already here!
Did you download the updated ROM???? security version downgrade means you are flashing old firmware!
Also a piece of advice, custom ROMs that are frequently updated carry latest security patches, however, stock ROMs carry old ones... hence, whenever, you go back to stock DO NOT FLASH BOOTLOADER AND GPT.BIN... you will never brick your device!

abhi212b said:
Bro... you could have searched, before creating a thread for it... https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
All the discussion is already here!
Did you download the updated ROM???? security version downgrade means you are flashing old firmware!
Also a piece of advice, custom ROMs that are frequently updated carry latest security patches, however, stock ROMs carry old ones... hence, whenever, you go back to stock DO NOT FLASH BOOTLOADER AND GPT.BIN... you will never brick your device!
Click to expand...
Click to collapse
I agree with the majority of your post, just to clarify that when you revert back to stock ROMs, the most important thing is that you flash the firmware as new or newer than your bootloader.
The hardbricks I've seen involve users flashing older stock firmware than their bootloaders. Generally, bootloaders do not downgrade, so you're left with a newer bootloader but older system firmware. The OTA for your system can flash to the bootloader without checking what bootloader you have, so in this case you have an older OTA corrupting a newer bootloader, hence the hardbricks. Regardless of whether you flash GPT/bootloader or not, this hopefully shows the importance of not using old firmware.
As for the opening poster, please use the newest firmware available as abhi212b had mentioned. If you require them, the latest GPT and bootloader files can be found here https://drive.google.com/folderview?id=0B-GUyOfb8OgzcUl1NUtHYWNIR2M but you must formally flash the newest firmware, else you may keep hardbricking until you fully update.
For Indian devices, the latest stock ROM is NPJS25.93-14-15 (Feb 2018 security patch) https://forum.xda-developers.com/showpost.php?p=76250128&postcount=753

abhi212b said:
Bro... you could have searched, before creating a thread for it... https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
All the discussion is already here!
Did you download the updated ROM???? security version downgrade means you are flashing old firmware!
Also a piece of advice, custom ROMs that are frequently updated carry latest security patches, however, stock ROMs carry old ones... hence, whenever, you go back to stock DO NOT FLASH BOOTLOADER AND GPT.BIN... you will never brick your device!
Click to expand...
Click to collapse
@abhi212b :
I went through the given thread and none of the given tips helped me out, hence I decided to create this thread after around 6 hours of searching.
Code:
custom ROMs that are frequently updated carry latest security patches
Thank you for this. I'll keep it in mind.

echo92 said:
I agree with the majority of your post, just to clarify that when you revert back to stock ROMs, the most important thing is that you flash the firmware as new or newer than your bootloader.
The hardbricks I've seen involve users flashing older stock firmware than their bootloaders. Generally, bootloaders do not downgrade, so you're left with a newer bootloader but older system firmware. The OTA for your system can flash to the bootloader without checking what bootloader you have, so in this case you have an older OTA corrupting a newer bootloader, hence the hardbricks. Regardless of whether you flash GPT/bootloader or not, this hopefully shows the importance of not using old firmware.
As for the opening poster, please use the newest firmware available as abhi212b had mentioned. If you require them, the latest GPT and bootloader files can be found here https://drive.google.com/folderview?id=0B-GUyOfb8OgzcUl1NUtHYWNIR2M but you must formally flash the newest firmware, else you may keep hardbricking until you fully update.
For Indian devices, the latest stock ROM is NPJS25.93-14-15 (Feb 2018 security patch) https://forum.xda-developers.com/showpost.php?p=76250128&postcount=753
Click to expand...
Click to collapse
@echo92 :
Thank you very much for pinpointing the resources. I've been tirelessly looking for these.
Just flashed the required files and everything went smooth.
For your assistance, you have my gratitude. Have a nice day!

carnage885 said:
@abhi212b :
I went through the given thread and none of the given tips helped me out, hence I decided to create this thread after around 6 hours of searching.
Code:
custom ROMs that are frequently updated carry latest security patches
Thank you for this. I'll keep it in mind.
Click to expand...
Click to collapse
I don't exactly remember which in which thread it is, however, i myself posted the solution...
Nevertheless, the problem is solved, that is more important...

Unlocked bootloader and OTA updates

Will i recive OTA update if i unlock the bootloader?

Androidtroll said:
Will i recive OTA update if i unlock the bootloader?
Click to expand...
Click to collapse
Yes. Just unlocking the bootloader still allows everything to work normally, though you can't install otas if you mounted or modified /system and /oem partitions, or have twrp recovery.
Otherwise your phone should still function as if it weren't unlocked.

In addition to the above reply - if you do modify your system and want to flash back to stock firmware, please check if you can download the correct firmware for your device. I see from your history you have a retEU device, so the latest series of firmwares would be the NPNS25.137-93 series (with NPNS25.137-93-10 being the April 2018 security patch). I'd suggest checking to see if there is a stock ROM matching your current build before you unlock the bootloader (either at https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ or https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ or https://androidfilehost.com/?a=show&w=files&flid=171014 ) though it seems the latest firmware that's been leaked is NPNS25.137-93-4 (the Jan 2018 security patch build). Just as a headsup, firmware.center has a cryptominer that could keep your CPU at 100 % if you have their page open.
If you download and flash the NPNS25.137-92-10 firmware, which is the April 2018 security patch for Brazil/India devices, you may be able to re-lock your bootloader and get back to full stock, but you may not be able to receive OTA updates (as the NPNS25.137-92 series of updates do not appear to be deployed to the retEU channel), so be careful which firmware you flash.
You can still unlock your bootloader without having the latest firmware to hand, but until the firmware matching your stock firmware before you unlocked or newer is available, you may not be able to re-lock your device. You may be able to flash older stock firmware for EU devices, but please do not use OTA updates if you flash older stock firmware, else you may hard brick your device.
Good luck whichever way you decide.

bazinga137 said:
Yes. Just unlocking the bootloader still allows everything to work normally, though you can't install otas if you mounted or modified /system and /oem partitions, or have twrp recovery.
Otherwise, your phone should still function as if it weren't unlocked.
Click to expand...
Click to collapse
Yes the Same thing Happened
I had TWRP recovery and I installed the Security Patch
my Phone Stuck at TWRP
but it has One solution
First, take the data backup of all in twrp at your sd card
now install any custom Rom
Reboot your device and check the rom is working or not
do reboot and go back to your Twrp and Restore the backup
I tested it and It worked perfectly

echo92 said:
In addition to the above reply - if you do modify your system and want to flash back to stock firmware, please check if you can download the correct firmware for your device. I see from your history you have a retEU device, so the latest series of firmwares would be the NPNS25.137-93 series (with NPNS25.137-93-10 being the April 2018 security patch). I'd suggest checking to see if there is a stock ROM matching your current build before you unlock the bootloader (either at https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ or https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ or https://androidfilehost.com/?a=show&w=files&flid=171014 ) though it seems the latest firmware that's been leaked is NPNS25.137-93-4 (the Jan 2018 security patch build). Just as a headsup, firmware.center has a cryptominer that could keep your CPU at 100 % if you have their page open.
If you download and flash the NPNS25.137-92-10 firmware, which is the April 2018 security patch for Brazil/India devices, you may be able to re-lock your bootloader and get back to full stock, but you may not be able to receive OTA updates (as the NPNS25.137-92 series of updates do not appear to be deployed to the retEU channel), so be careful which firmware you flash.
You can still unlock your bootloader without having the latest firmware to hand, but until the firmware matching your stock firmware before you unlocked or newer is available, you may not be able to re-lock your device. You may be able to flash older stock firmware for EU devices, but please do not use OTA updates if you flash older stock firmware, else you may hard brick your device.
Good luck whichever way you decide.
Click to expand...
Click to collapse
I would unlock the bootloader just to try to fix the camera (then edit the system files), not for flash twrp / custom rom

Androidtroll said:
I would unlock the bootloader just to try to fix the camera (then edit the system files), not for flash twrp / custom rom
Click to expand...
Click to collapse
Just unlocking the BL wouldn't be enough to edit system files. You'll need root privileges to do so and for that you will have to flash/boot TWRP to install a root app like magisk.
So all the useful information @echo92 posted above is significant for you.
Sent from my Moto G5 Plus using XDA Labs

Is there a way to take TWRP off or disable to still grab the security patches? Or is clean install/backup (like Rutambh mentioned) the only option? The reason I ask I needed TWRP to install camera mod, so it would be nice to still get those OTA's. I tried to just fastboot boot TWRP but it would just hang at it's logo. Flash was only option.

Frawgg said:
Is there a way to take TWRP off or disable to still grab the security patches? Or is clean install/backup (like Rutambh mentioned) the only option? The reason I ask I needed TWRP to install camera mod, so it would be nice to still get those OTA's. I tried to just fastboot boot TWRP but it would just hang at it's logo. Flash was only option.
Click to expand...
Click to collapse
If anything in /system or /oem is tampered like installing a camera mod (or just mounting system r/w) the only way to receive future OTA updates is flashing your current ROM incl. stock recovery via fastboot.
Sent from my Moto G5 Plus using XDA Labs