Database Users

Motorola Firmware for xt1625 (>= MPJ24.139-64)

Any idea where I can download firmware files for the xt1625 with build #MPJ24.139-64 or newer? I flashed my phone with the firmware from xt1624 thinking it would work, but now it can't get past recovery. I'm able to flash oem.img for MPJ24.139-48, but when I attempt to flash gpt.bin, I get the following error:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.055s
If it helps, here's the output for getvar:
Code:
C:\Users\aaron_000\AppData\Local\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223H2GWK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x93
(bootloader) uid: DE8F6B0100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354124072012644
(bootloader) meid:
(bootloader) date: 08-17-2016
(bootloader) sku: XT1625
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jun 19 10:15:49 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_amz/athene:6.0.1/M
(bootloader) ro.build.fingerprint[1]: PJ24.139-48/48:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.31.48.athene_amz.
(bootloader) ro.build.version.full[1]: amz.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband: M8952_70009.08.03.45R ATHENE_RETUSA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g06a4fb5 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld35) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Sun Jun 5 11:16:49 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: amz
all: listed above
finished. total time: 0.256s

-48 and -49 are the only two available for the US model

xtermmin said:
-48 and -49 are the only two available for the US model
Click to expand...
Click to collapse
And where can I find this? I have looked in all of the places it is supposed to be but have had no luck locating it. Doesn't seem to be available at this time.

stkpxl said:
I just posted the link for -49....
Click to expand...
Click to collapse
I don't have -49. My phone has -48. I would like to find a copy of the original firmware so I can return to stock if necessary.
UPDATE: Disregard the above. I found it.

stkpxl said:
I don't think it's been released for our model yet. I've been checking everyday. If you need to restore the stock firmware, use this one: https://androidfilehost.com/?fid=24591023225178637
Click to expand...
Click to collapse
is it work on xt1625 retail mpj 24.139 64/65 athene
i stuck in recovety since awhile .. if it works .. how to flash .. need it kindly .. im anew moto g4 user
---------- Post added at 02:42 PM ---------- Previous post was at 02:19 PM ----------
pastorbob62 said:
I don't have -49. My phone has -48. I would like to find a copy of the original firmware so I can return to stock if necessary.
UPDATE: Disregard the above. I found it.
Click to expand...
Click to collapse
whats the difference between 48 and 49 and whats the factory stock for this model 1625 mjp 24-139 retail 64/65

herakikoly said:
is it work on xt1625 retail mpj 24.139 64/65 athene
i stuck in recovety since awhile .. if it works .. how to flash .. need it kindly .. im anew moto g4 user
---------- Post added at 02:42 PM ---------- Previous post was at 02:19 PM ----------
whats the difference between 48 and 49 and whats the factory stock for this model 1625 mjp 24-139 retail 64/65
Click to expand...
Click to collapse
The -49 version is for the XT1635 not the XT1625. I have no idea if it will work with the XT1625, but experience has taught me that you should never flash any version except the one intended for your specific model. These forums are filled with people who didn't follow that simple rule and they are now bricked.
Here is a link to the -64 version for the XT 1625:
http://www.filefactory.com/file/3sq...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Here is a link to the filefactory repository with all versions for all G4 phones:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100

pastorbob62 said:
The -49 version is for the XT1635 not the XT1625. I have no idea if it will work with the XT1625, but experience has taught me that you should never flash any version except the one intended for your specific model. These forums are filled with people who didn't follow that simple rule and they are now bricked.
Here is a link to the -64 version for the XT 1625:
http://www.filefactory.com/file/3sq...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Here is a link to the filefactory repository with all versions for all G4 phones:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Click to expand...
Click to collapse
thanks alot
last thing .. how to flash it ?
the link named xt1644 not 1625 .. is it normal ?
thanks for your help .. i just anew user and dont know anything .. hope u patient and for the 3rd time thank u

herakikoly said:
thanks alot
last thing .. how to flash it ?
the link named xt1644 not 1625 .. is it normal ?
thanks for your help .. i just anew user and dont know anything .. hope u patient and for the 3rd time thank u
Click to expand...
Click to collapse
The link I posted is for the XT1625 and the XT1644 firmware.
Here is a link to flashing the firmware from Fastboot. Be sure you have the correct firmware before you flash. Read the instructions very carefully and be sure you understand BEFORE flashing. If you still have questions, ASK!
http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/

pastorbob62 said:
The link I posted is for the XT1625 and the XT1644 firmware.
Here is a link to flashing the firmware from Fastboot. Be sure you have the correct firmware before you flash. Read the instructions very carefully and be sure you understand BEFORE flashing. If you still have questions, ASK!
http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
Click to expand...
Click to collapse
flashed it but after it's been flashed still stuck in recovery .. tried also another old version like 48 and 49 but they failed during flashing .. may be cause it cant downgraded but the version u gave me was able to flash 64 65 but after finishing no good news
any help

herakikoly said:
flashed it but after it's been flashed still stuck in recovery .. tried also another old version like 48 and 49 but they failed during flashing .. may be cause it cant downgraded but the version u gave me was able to flash 64 65 but after finishing no good news
any help
Click to expand...
Click to collapse
Stop trying to flash older versions of the ROM. It won't work for the reason you stated. When you flashed the -64 ROM did you get any errors at all? When you reboot, do you get the warning about your phone being unlocked? You should if everything flashed correctly. Also, you are certain you had the XT1625 with 139-64? Did you flash directly from fastboot entering the commands one at a time? Or did you use Flashstock.bat? I always do the commands individually so I can verify each one is successful. It takes more time and you need to be more careful but I prefer that method.
When you say you are stuck in recovery, do you mean the bootloader or stock recovery? I am assuming you mean the bootloader since you were able to flash the ROM using Fastboot. When you are in the bootloader, press the volume control until START is displayed next to the power button. Then press the power button. it should boot the phone. If it doesn't then I have no idea what to suggest.
Let me know what happens.

pastorbob62 said:
Stop trying to flash older versions of the ROM. It won't work for the reason you stated. When you flashed the -64 ROM did you get any errors at all? When you reboot, do you get the warning about your phone being unlocked? You should if everything flashed correctly. Also, you are certain you had the XT1625 with 139-64? Did you flash directly from fastboot entering the commands one at a time? Or did you use Flashstock.bat? I always do the commands individually so I can verify each one is successful. It takes more time and you need to be more careful but I prefer that method.
When you say you are stuck in recovery, do you mean the bootloader or stock recovery? I am assuming you mean the bootloader since you were able to flash the ROM using Fastboot. When you are in the bootloader, press the volume control until START is displayed next to the power button. Then press the power button. it should boot the phone. If it doesn't then I have no idea what to suggest.
Let me know what happens.
Click to expand...
Click to collapse
1st of all thanks for help
no errors happened due to flashing the room
all commands finished successfully
tried to flash one commend after one and also flashed once using rsd
the result of twice was the same
after finished successfully it make a reboot but its open on the stock recovery , and what i do after it opened i press on reboot sys boot loader to get the start icon to press put its start again on the recovery .. so i don't know what to do .. if u kindly know how to survive please heeeelp

herakikoly said:
1st of all thanks for help
no errors happened due to flashing the room
all commands finished successfully
tried to flash one commend after one and also flashed once using rsd
the result of twice was the same
after finished successfully it make a reboot but its open on the stock recovery , and what i do after it opened i press on reboot sys boot loader to get the start icon to press put its start again on the recovery .. so i don't know what to do .. if u kindly know how to survive please heeeelp
Click to expand...
Click to collapse
I'm sorry but I am out of suggestions. I didn't have any problem flashing this firmware. It must be something that happened when you first attempted to update. You might try to flash TWRP and see if you can flash a custom ROM. Other than that I am out of ideas.
I wish you luck my friend.

herakikoly said:
1st of all thanks for help
no errors happened due to flashing the room
all commands finished successfully
tried to flash one commend after one and also flashed once using rsd
the result of twice was the same
after finished successfully it make a reboot but its open on the stock recovery , and what i do after it opened i press on reboot sys boot loader to get the start icon to press put its start again on the recovery .. so i don't know what to do .. if u kindly know how to survive please heeeelp
Click to expand...
Click to collapse
From recovery try wiping data and cache then do reboot. May help

thanks all .. problem is solved

herakikoly said:
thanks all .. problem is solved
Click to expand...
Click to collapse
What did you do to fix it? Just wipe data and cache? There may be others who have the same problem and could use advice on how to get back to a working phone.

herakikoly said:
thanks all .. problem is solved
Click to expand...
Click to collapse
Once again, what did you do to get it up and running? Sharing information and fixes is one of the many features that makes these forums successful.

pastorbob62 said:
Once again, what did you do to get it up and running? Sharing information and fixes is one of the many features that makes these forums successful.
Click to expand...
Click to collapse
flashed amazon version .. and it works

herakikoly said:
flashed amazon version .. and it works
Click to expand...
Click to collapse
Hmmmm, interesting. I don't recall you ever saying you had the Amazon version. Knowing that would have saved me wasting a lot of time offering help with the retail version.

herakikoly said:
flashed amazon version .. and it works
Click to expand...
Click to collapse
Hi, can you help me? I have the same problem, where did you get the amazon version? :S

scotolive said:
Hi, can you help me? I have the same problem, where did you get the amazon version? :S
Click to expand...
Click to collapse
Here is a link to the filefactory repository with all versions for all G4 phones:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Be certain you download the correct version for your phone.

Unable to flash stock rom......please help

Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance

yshiv666 said:
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
Click to expand...
Click to collapse
Which ROM version you are trying ?
Try with latest September's patch one available here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

____Mdd said:
Which ROM version you are trying ?
Try with latest September's patch one available here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
yes I had tried it but it is not working

yshiv666 said:
yes I had tried it but it is not working
Click to expand...
Click to collapse
Was your bootloader unlocked ?
In bootloader loader screen it shows locked now, and system modified !
Baseband is unknown in bootloader screen, so i can say modem is not getting installed, (plus there may be other things too which are not getting installed)
Noe, do it, Flash ROM again,
But with entering one command at time,
After flashing/ending of one command, check that you are getting "OKAY"..
Let us know if there is any error or "FAILED" at command end.

____Mdd said:
Was your bootloader unlocked ?
In bootloader loader screen it shows locked now, and system modified !
Baseband is unknown in bootloader screen, so i can say modem is not getting installed, (plus there may be other things too which are not getting installed)
Noe, do it, Flash ROM again,
But with entering one command at time,
After flashing/ending of one command, check that you are getting "OKAY"..
Let us know if there is any error or "FAILED" at command end.
Click to expand...
Click to collapse
yes!!!! it says "FAILED" at the end.... see the screenshot of CMD

yshiv666 said:
yes!!!! it says "FAILED" at the end.... see the screenshot of CMD
Click to expand...
Click to collapse
That screenshot is of system,
What about bootloader and gpt ?
Again, tell me which version of ROM you are trying ?

____Mdd said:
That screenshot is of system,
What about bootloader and gpt ?
Again, tell me which version of ROM you are trying?
Click to expand...
Click to collapse
here is the screenshot for gpt.bin and bootloader.img!!!!!
and I'm flashing Sept 01 Security Patch which you have mentioned above.........

yshiv666 said:
here is the screenshot for gpt.bin and bootloader.img!!!!!
and I'm flashing Sept 01 Security Patch which you have mentioned above.........
Click to expand...
Click to collapse
I have never faced or seen anyone with this like issue,
Wait a while, @echo92 has better experience with this like stuff, he will guide you better than me.
Till than you can try blank flash again, with replacing gpt and bootloader from ROM's zip.

____Mdd said:
I have never faced or seen anyone with this like issue,
Wait a while, @echo92 has better experience with this like stuff, he will guide you better than me.
Till then you can try blank flash again, with replacing gpt and bootloader from ROM's zip.
Click to expand...
Click to collapse
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:

yshiv666 said:
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
Click to expand...
Click to collapse
Wait, December's !
You got your device back is good thing, but remain stuff will be of September's patch..
Now if you get update notification for December's patch dont take it... It will brick your device again.
You will have to wait for fastboot ROM of December's patch..
Till then, keep your phone on September...
Don't take OTA...
When December's patch build is available flash it with fastboot...

yshiv666 said:
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
Click to expand...
Click to collapse
Good to hear you got your device working. As ____Mdd has mentioned, I would strongly recommend you wait for the Dec 2017 stock ROM to flash. Looking at your bootloader details, since you've got a Dec 2017 GPT, a June/September 2017 bootloader and a marshmallow baseband, you likely cannot safely take OTA updates.
Because you've downgraded from Nougat to marshmallow, taking OTA updates runs a high risk of hard bricking again and our current blank flash may not work on your device now you've flashed the Dec 2017 GPT. Thus, do not take OTA updates until you flash the Dec 2017 Nougat stock ROM (which isn't available yet), and if you later downgrade again, do not accept OTA updates. Else the OTA updates may corrupt your newer bootloader again (bootloaders do not downgrade) with no recourse except to wait for a newer blankflash or a 8000+ rupees repair.

I have the same case and it sends me an error in the boot.
Can somebody help me

Turning OEM on without phone turning on
al3al3al3jandr0 said:
I have the same case and it sends me an error in the boot.
Can somebody help me
Click to expand...
Click to collapse
I am trying to flash my ROM as the phone is not turning on in any method be it normal of recovery mode or factory mode. My phone MOTO G4 Plus is unable to flash the ROM as it is OEM_LOCKED and None of the options from the bootloader menu works. On selecting any of the options from the power button nothing happens except for the barcodes which show the barcode and RESTART BOOTLOADER restarts the bootloader.
Please help someone.
Is there a way to unlock OEM without turning the phone on as I can't turn it on.

qjzxvkw said:
I am trying to flash my ROM as the phone is not turning on in any method be it normal of recovery mode or factory mode. My phone MOTO G4 Plus is unable to flash the ROM as it is OEM_LOCKED and None of the options from the bootloader menu works. On selecting any of the options from the power button nothing happens except for the barcodes which show the barcode and RESTART BOOTLOADER restarts the bootloader.
Please help someone.
Is there a way to unlock OEM without turning the phone on as I can't turn it on.
Click to expand...
Click to collapse
why doesn't it boot??? What were you doing before this happened. Please give the details

Heeth21 said:
why doesn't it boot??? What were you doing before this happened? Please give the details
Click to expand...
Click to collapse
Nothing I just kept it for charging overnight. And it doesn't power on in the morning. I plugged it while it was on though.
Someone suggested it has damaged its motherboard.

qjzxvkw said:
Nothing I just kept it for charging overnight. And it doesn't power on in the morning. I plugged it while it was on though.
Someone suggested it has damaged its motherboard.
Click to expand...
Click to collapse
Hmm, do you recall if there was an update notification at all before you put your device on charge?
Without getting your device to boot, there's no way to toggle the OEM_unlocking function unfortunately.
If you can, when you've plugged your device to your computer and booted to the bootloader:
1)Open a minimal ADB command window on Windows (download/install minimal ADB from here: https://forum.xda-developers.com/showthread.php?t=2317790 other fastboot/adb tools should work too)
2)Type 'fastboot devices' without quotes into the window. Press Enter - your device should respond with its serial number.
3)If you get that response, type 'fastboot getvar all' without quotes. Press Enter.
4)Please paste the output here or upload it as a text file (or paste it into a site like pastebin and put the link here). You may wish to omit the IMEI.
We could try to re-flash the stock firmware that you had, but if that doesn't solve things it may start to look like a hardware failure.

yshiv666 said:
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
Click to expand...
Click to collapse
make sure your bootloader is unlocked. and let me know.

echo92 said:
Hmm, do you recall if there was an update notification at all before you put your device on charge?
Without getting your device to boot, there's no way to toggle the OEM_unlocking function unfortunately.
If you can, when you've plugged your device to your computer and booted to the bootloader:
1)Open a minimal ADB command window on Windows (download/install minimal ADB from here: https://forum.xda-developers.com/showthread.php?t=2317790 other fastboot/adb tools should work too)
2)Type 'fastboot devices' without quotes into the window. Press Enter - your device should respond with its serial number.
3)If you get that response, type 'fastboot getvar all' without quotes. Press Enter.
4)Please paste the output here or upload it as a text file (or paste it into a site like pastebin and put the link here). You may wish to omit the IMEI.
We could try to re-flash the stock firmware that you had, but if that doesn't solve things it may start to look like a hardware failure.
Click to expand...
Click to collapse
Thanks for the response: Here is everything you asked:
I am sure there was no update notification as I always download any update that is released as soon as I see it. So I might have updated already.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223BGGD2 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223BGGD2
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 6E23DD0000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *************
(bootloader) meid:
(bootloader) date: 06-06-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 20 23:52: 3 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.201.4.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (208)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.244s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Thanks. It was indeed a hardware problem. Motherboard was broken in two pieces just below camera position.

Moto G4 Plus boot to TWRP problem

Morning,
I have a Motorla G4 plus UK model XTN1642 I rooted this and installed TWRP when I first bought it several months back.
Yesterday, I got the 'update is avaialble' notification and follishly I allowed it to download and then install which failed, now the phone will only boot to the TWRP screen each time it restarts.
However, If I boot into bootloader then manually click 'Start' the phone will boot normally, but this is not ideal.
The phone is running stock Android 7.0 build number NPJS25.93-14-4, i've tried reading the forum but there is quite a lot that I don't understand and I don't want to make it worse by killing it completely and then not having a phone to use.
Can anyone give me a straight forward way to get the phone to boot up normally without having to go through bootloader and then manually click start?
I'm hoping that it is something simple, I don't have any backups of the device either!

Look, with twrp installed there's no way to update via ota. That's why I reflashed stock rom for getting the ota update. Although I planned to flash 6.0 M stock initially, I managed to flash 7.0 N stock ROM since it was available on this forum.
The version I have at the moment is 25.93.14.10 which is the September 2017 security patch. My another G4 absolutely untouched received ota today from 14.4 March patch to 14.13 December patch. I am not quite sure what happened to my 14.10 September patch. Why there is no ota? Maybe because this ROM was found on the G4+ forum?
Back to your question, find a stock ROM to flash, don't install twrp as it will modify the recovery. For install ota you will need to keep the ROM completely untouched.

Hi,
Yes, I am aware of that now but at the time I wasn't or else I wouldn't have done it.
But, after reading through teh forum, I followed this https://forum.xda-developers.com/moto-g4/help/ota-upgrade-7-0-twrp-installed-t3727807 after which the device booted normally again.
I should have left it at that, but again, I was notified of the update, so having read the thread above, let it go ahead, it download the update and rebooted., I then tried to root again and install twrp and elementalx and now it doesn't boot just get a black screen, I can still get into twrp and bootloader though.
Here is what I get from fastboot getvar all
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x41
(bootloader) uid: E492B10000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ****************
(bootloader) meid:
(bootloader) date: 05-30-2016
(bootloader) sku: XT1642
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 20 23:53:41 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.01R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.562s
I've blanked out the IMEI and Serial number in the above
I guess I should have left it ater getting it back and booting, but it sort of made sense to do the update then I needed to root it again.
What now?

right then,
I've followed this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the phone is back up and running, i've lost all my data stored on the phone, but that is no big deal.
Now, is there a current thread that explains simply how to root this latest version and install TWRP again.
I don't want to stuff it up yet again, I reckon i've been luck so far to recover it TWICE !

ffrlr said:
right then,
I've followed this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the phone is back up and running, i've lost all my data stored on the phone, but that is no big deal.
Now, is there a current thread that explains simply how to root this latest version and install TWRP again.
I don't want to stuff it up yet again, I reckon i've been luck so far to recover it TWICE !
Click to expand...
Click to collapse
How are you rooting, and what software are you using?
The general order for rooting is to:
1)Flash/boot TWRP. Either the official TWRP (3.2.1 - https://dl.twrp.me/athene/ ) or shreps' TWRP should suffice: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
2)In TWRP, backup your stock ROM and make a separate copy of your kernel (boot) partition.
3)Flash ElementalX or another custom kernel. Ensure this happens before you root else you'll bootloop. ElementalX v1.04 or v2.0 is here: https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
3a)Wipe cache and Dalvik. At this point, you may wish to boot and check your device is working. If so, proceed to 4)
4)In TWRP (or boot back to TWRP), flash the root manager of your choice, either SuperSU v2.8.2 SR5 https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 or magisk 14/15. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Do not mix and match root managers without fully uninstalling and flashing the stock kernel again (hence the separate backup you made in 2)).
5)Wipe cache and Dalvik if not done in 3a) and reboot.
6)Any issues, revert to your backup made in 2).
This should give you a device booting with the latest stock ROM and rooted. This procedure is working on a XT1642 with NPJS25.93-14-13 (same firmware as you have now) and ElementalX v2.0 and magisk 15.3. As I linked in the other thread you've seen, you may wish to disable the Motorola updater to stop you from getting into another TWRP bootloop.
Hope that helps.
EDIT - have a look at this thread too: https://forum.xda-developers.com/moto-g4/how-to/guide-how-to-root-moto-g4-magisk-stock-t3725712/

Hi
thank you for the reply, very much appreciated, I'm keen to get my phone rooted again as I use 'timed toggles' to switch the phone into aeroplane mode when i'm asleep etc.
When I last rooted it after I bought it, I used magisk from what I recall, but I amnot really fussy to be honest.
Yesterday, I bravely attempted several times to install twrp in fact it was the shreps version which I found a link to, but for some reason I cannot get it to install.
I boot the phone using volume down button and power, then connect to the pc, then type fastboot flash recovery twrp-3.1.1-athene_shreps.img.
during the flash, I get the following
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
I then immediately boot to recovery using the volume keys and power button, after the device reboots, I don't get TWRP, justa dead android lying on it's back with a red exclamation mark above it, beneath is written no command.
I've had about four goes, but each time I get the same, am I missing something?, i've followed various threads and tutorialsd to no avail.

Echo92
I don't know what is different in your last post detailing how I go about rooting the G4, but that is basically what I did and it failed continually to restart to TWRP.
I've just tried again, albeit from a different PC (Windows 7 x32 instead of Windows 10 x32) and downloaded the zips from your links, and it has worked perfectly first time.
I've powered off the phone several times and each time i'm able to get into TWRP, I have also done the root using Magisk, again worked first time, I have deleted the apk from /system/priv-app/3c_ota/ so hopefully i'll not be in this position again!
Finally, i've also done a further full backup now everything is installed and the root is done using TWRP, so if anything does go awry, I should be able to (hopefully) revert back.
Thank you very much for the very informative instructions, they have been of great help, hopefully they will be for others too.

ffrlr said:
Echo92
I don't know what is different in your last post detailing how I go about rooting the G4, but that is basically what I did and it failed continually to restart to TWRP.
I've just tried again, albeit from a different PC (Windows 7 x32 instead of Windows 10 x32) and downloaded the zips from your links, and it has worked perfectly first time.
I've powered off the phone several times and each time i'm able to get into TWRP, I have also done the root using Magisk, again worked first time, I have deleted the apk from /system/priv-app/3c_ota/ so hopefully i'll not be in this position again!
Finally, i've also done a further full backup now everything is installed and the root is done using TWRP, so if anything does go awry, I should be able to (hopefully) revert back.
Thank you very much for the very informative instructions, they have been of great help, hopefully they will be for others too.
Click to expand...
Click to collapse
Good to hear it worked I'm glad that it worked on your other computer - Windows 10 appears to cause some headaches on flashing - I don't know if it's to do with the driver signature enforcement, that I don't think Windows 7 has. I've not had issues with Windows 10 flashing for the most part, though I do have a computer with a BIOS and not UEFI - though that being said, last time I flashed TWRP (shrep's TWRP), it didn't stick and required another re-flash, so maybe it's to do with the updated B1:07 bootloaders in both cases?
By the way, that 'image not signed or corrupt' message when flashing TWRP is normal and expected. TWRP is not cryptographically signed with the keys that the system/fastboot is expecting, so it's simply a message to alert you.
Have fun with your new root powers (please use responsibly )

G5 Plus Hard bricked after flashing wrong ROM

I have Indian Set.
These are the things I did:
Unlocked Bootloader [Successful]
Flashed TWRP [Successful]
Tried to install Custom ROM and Failed because TWRP was 32 bit.
Installed 64 bit TWRP [Successful]
Flashed Custom ROM but was draining lot of battery; so I decided to get back to Stock.
Flashed flashable stock ROM from TWRP from here. [NPNS25.137-92-4 (20180101 security patch)] [Successful]
Which was the Wrong ROM; I guess.
After Flashing the ROM, IMEI showed : 0. So there were no signal.
Tried to fix IMEI after seeing YouTube video using GS_II_Repair app.
The app was for Samsung Galaxy S II. The YouTube video didn't mention it. So. I followed the video.
This HardBricked the phone. [no sign of life, no bootloader, no recovery, no booting menu, just LED light flashing after connecting to charger].
I used Albus Blank Flash to get to Bootloader Menu.
I tried to install the Stock Firmware using fastboot. The flashing Process is successful but the device shows "Bootloader Unlocked Warning" in a loop.
This is what I get of
Code:
fastboot getvar all
Code:
D:\POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.x
ml>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY224393KX
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 199046E600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358958064342378
(bootloader) meid:
(bootloader) date: 04-22-2017
(bootloader) sku: XT1686
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 5: 1:22 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-92-4/6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.291.6.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_37.46.07.47u POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gd732fd2 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Jan 23 11:31:28 CST 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.C5-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VC0.C5-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) devcfg.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) keymaster.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) cmnlib64.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) prov.git: git=MBM-NG-VC0.C5-0-g3d71f29
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 1.528s
I need help to save my device.

DeepeshC said:
I have Indian Set.
These are the things I did:
Unlocked Bootloader [Successful]
Flashed TWRP [Successful]
Tried to install Custom ROM and Failed because TWRP was 32 bit.
Installed 64 bit TWRP [Successful]
Flashed Custom ROM but was draining lot of battery; so I decided to get back to Stock.
Flashed flashable stock ROM from TWRP from here. [NPNS25.137-92-4 (20180101 security patch)] [Successful]
Which was the Wrong ROM; I guess.
After Flashing IMEI shwed : 0. So there were no signal.
Tried to fix IMEI after seeing YouTube video using GS_II_Repair app.
This HardBricked the phone. [no sign of life, no bootloader, no recovery, no booting menu, just LED light flashing after connecting to charger].
I used Albus Blank Flash to get to Bootloader Menu.
I tried to install the Stock Firmware using fastboot. The flashing Process is successful but the device shows "Bootloader Unlocked Warning" in a loop.
This is what I get of
I need help to save my device.
Click to expand...
Click to collapse
Use twrp flashable stock rom.

Gokul said:
Use twrp flashable stock rom.
Click to expand...
Click to collapse
When I try to go to Recovery (TWRP) from bootloader menu "Unlocked Bootloader Warning" keeps looping.
I don't think its possible to flash twrp flashable rom from bootloader.
Is there any other way?

DeepeshC said:
When I try to go to Recovery (TWRP) from bootloader menu "Unlocked Bootloader Warning" keeps looping.
I don't think its possible to flash twrp flashable rom from bootloader.
Is there any other way?
Click to expand...
Click to collapse
Go to Service Center

Kdemwa said:
Go to Service Center
Click to expand...
Click to collapse
I am from Nepal and there are no Motorola Service Center here.

DeepeshC said:
I am from Nepal and there are no Motorola Service Center here.
Click to expand...
Click to collapse
flash any other bootloader logo.bin then it wont show up that bootloader unlocked warning,even though it shows like that it should not pose any problem you should be fine installing any twrp stock rom or custom oreo rom.
but if you had lost imei due to moving from oreo to stock rom then just flash any custom oreo rom (recent ones) and use these 2 commands fastboot erase modemst1,fastboot erase modemst2 then boot into the oreo rom you will have your signal back but for now volte is lost if your network provider supports volte.
wish u good luck.

Rakesh1b said:
flash any other bootloader logo.bin then it wont show up that bootloader unlocked warning,even though it shows like that it should not pose any problem you should be fine installing any twrp stock rom or custom oreo rom....
Click to expand...
Click to collapse
I flashed logo.bin and then twrp. again when I try to go to recovery or System the new logo.bin keeps looping. Is there any other way?

Reparar fastboot
DeepeshC said:
When I try to go to Recovery (TWRP) from bootloader menu "Unlocked Bootloader Warning" keeps looping.
I don't think its possible to flash twrp flashable rom from bootloader.
Is there any other way?
Click to expand...
Click to collapse
intenta buscar en youtube a DAN RATIA el tiene un video que se titula repara inicio en modo fastboot moto g5 plus

it is like me if you flash TRWP and chech the size of recovery partition you will see that you have 16Mb and image recovery need 20 MB this the problem , you should find how to resize partition recovery , if you find solution PM me we are same problem , you can flash stock ROM debloat but the original one is need to resize partition recovery , you made mistake like me by flashing wrong gpt.bin and bootloader

I had pixelexperience latest build (android 11) on my moto g5 plus (potter) . Now, my device is hard bricked because i flashed a wrong file. Now i tried to blankflash, but it gives error
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
Somebody please help!

aakashdeep930 said:
I had pixelexperience latest build (android 11) on my moto g5 plus (potter) . Now, my device is hard bricked because i flashed a wrong file. Now i tried to blankflash, but it gives error
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
Somebody please help!
Click to expand...
Click to collapse
Did you use this one?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
yes, i used this one also. It gave same error.

No available update, best way forward?

Hi all,
My XT1644 is currently on build NPJS25.93-14-4, I just flashed it. It is on the March 2017 Security patch, retus Software channel. Bootloader is unlocked and phone is unrooted.
I don't understand why I can't update the phone further through OTA. According to the system update check: "Your system is up to date", which is quite clearly not true.
I went back to stock in order to update my phone before re-rooting it, but it doesn't work. What can I do? Should I look for every OTA since March 2017 and flash it manually or is there an other option?
Thanks a lot for any guidance you could provide, I don't know how to proceed any further.

Hmm, do you have a SIM card installed in your device? Sometimes, the OTA servers only serve updates if they know what network you're on. Is this a clean flash of the firmware that you performed ( full data wipe)?
If I recall, the next update you should be getting is the June 2017 NPJ25.93-14.5 update. If you want to flash the firmware, have a look here: https://androidfilehost.com/?fid=673368273298984458

echo92 said:
Hmm, do you have a SIM card installed in your device? Sometimes, the OTA servers only serve updates if they know what network you're on. Is this a clean flash of the firmware that you performed ( full data wipe)?
If I recall, the next update you should be getting is the June 2017 NPJ25.93-14.5 update. If you want to flash the firmware, have a look here:
Click to expand...
Click to collapse
Thanks for answer.
I have indeed a SIM card installed. However, the flash was not 100% clean, I have not run
Code:
fastboot erase userdata
Could this cause the issue?

Artanaol said:
Thanks for answer.
I have indeed a SIM card installed. However, the flash was not 100% clean, I have not run
Code:
fastboot erase userdata
Could this cause the issue?
Click to expand...
Click to collapse
I'm not sure - it could be a factor. Is it possible for you to do a full data wipe? When you were rooted, was your Motorola updater disabled?
If possible, can you post your getvar all info too?
1)Boot your device to the bootloader. Connect your device to your computer via USB.
2)Open an ADB terminal on your computer. In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Please post the info here, omitting your IMEI. I'd like to see what state your device is in at the moment, which is what this info should show.

echo92 said:
I'm not sure - it could be a factor. Is it possible for you to do a full data wipe? When you were rooted, was your Motorola updater disabled?
If possible, can you post your getvar all info too?
1)Boot your device to the bootloader. Connect your device to your computer via USB.
2)Open an ADB terminal on your computer. In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.
3)Please post the info here, omitting your IMEI. I'd like to see what state your device is in at the moment, which is what this info should show.
Click to expand...
Click to collapse
Ideally I would rather avoid it, so I'm trying to keep the userdata reset as a last resort. When rooted, I had indeed disabled the Moto Update Services with Servicely, but I have disabled servicely after the new flash (I've done it unrooted, so I'm not sure it 100% reversed the process though).
Regarding the getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.05
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8952
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 05E16B0100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) reason: UTAG "bootmode" configured as fastboot
Thanks!

Here is the rest of the getvar, as I couldn't post it in one message (I have removed a few info, since the forum seemed to be blocking some?)
Code:
(bootloader) date: 09-13-2016
(bootloader) sku: XT1644
(bootloader) cust_md5:
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.201.4.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband: M8952_70030.25.03.62R ATHENE_RETUSA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.05-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.05-0-g8a1de8c
(bootloader) qe: qe 0/1
(bootloader) frp-state: no protection (277)
(bootloader) ro.carrier: retus

Artanaol said:
Ideally I would rather avoid it, so I'm trying to keep the userdata reset as a last resort. When rooted, I had indeed disabled the Moto Update Services with Servicely, but I have disabled servicely after the new flash (I've done it unrooted, so I'm not sure it 100% reversed the process though).
Regarding the getvar:
<snip>
Thanks!
Click to expand...
Click to collapse
Thanks for the info - looks like your device should be ready for another update - you've still got the B1:05 bootloader from the March 2017 security patch and the right firmware.
From what you've mentioned, I'm not sure if uninstalling Servicely would have restored the Motorola updater to its normal status (or whether it's still disabled).
You may either have to re-root, then activate the updater then revert back to full stock, or try to flash the NPJ25.93-14.5 firmware without wiping your data, if you really don't wish to wipe your data. You could also try to flash the NPJ25.93-14.7 Sept 2017 security patch firmware as an alternative: https://androidfilehost.com/?fid=817906626617945295
EDIT - is this your post on the Moto G subreddit? https://www.reddit.com/r/MotoG/comments/916to5/no_available_update_on_g4_best_way_forward/

Thanks, I will give a shot at the various options you suggested!
(It is indeed my post, good catch! I wasn't sure where I would get an answer).