Database Users

XT1572 every time reboot enter in mode fastboot

Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:

SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect

same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,

sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.

Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.

acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.

acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc

Sam to me. Any help?

ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.

typo - fastboot, not fasboot
fastboot oem fb_mode_clear

fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?

lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.

With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...

Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse

sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?

XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s

My tale of woe (looking for xt1644 stock rom)

I just got my xt1644 (G4 Plus, US version) yesterday and was trying to get root.
I got through successfully:
1) Unlocking bootloader.
2) Flashing TWRP.
3) Flashing the boot.img from the Root-motog4-athena-xt1641-xt1643.zip file (maybe a mistake, but read on).
4) Flashing SuperSU.
So then, I HAD root, but no WiFi. Seemingly others had this problem, so I added the ro.securestorage.support=false to the build.prop.
Nope. Still no WiFi. So I tried to change the build.prop BACK by deleting that line. Then, on the next boot, it stays in the "Your bootloader is unlocked" screen and does not boot to system.
I DO have bootloader access, and TWRP still works.
So, if anyone has:
1) A stock build.prop for the xt1644, or
2) New ideas, or
3) Access to the stock rom for the xt1644, which I cannot fiind,
PLEASE let me know.
Thanks!
J

http://www.filefactory.com/file/3t2...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
Posted this in a bunch of stock ROM topics.
For root, there is no need to flash a new boot.img. Just unlock bootloader, flash or boot TWRP, type in the command to tell SuperSU to flash in systemless mode, flash SuperSU, and reboot.
Guide: http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772

xtermmin said:
http://www.filefactory.com/file/3t2...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
Posted this in a bunch of stock ROM topics.
For root, there is no need to flash a new boot.img. Just unlock bootloader, flash or boot TWRP, type in the command to tell SuperSU to flash in systemless mode, flash SuperSU, and reboot.
Guide: http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Click to expand...
Click to collapse
THANK YOU!
I'm d/ling now and will follow your guide!
J

jogawa said:
THANK YOU!
I'm d/ling now and will follow your guide!
J
Click to expand...
Click to collapse
Yay! I got the phone back by flashing the stock ROM, then rooted using the guide, and I'm happy.
Thank you for pointing that stuff out xtermmin! I never thought to look for a ROM file with a name other than one that started with xt1644, and couldn't figure out how to search the directory.
You saved me.
Thanks again!
J

Filefactory link is acting very strangely. Its just loading the basic html, no css.
Could someone give me a mirror? Im as stuck as OP was without it.
EDIT: It took a few minutes but filefactory loaded enough of the css to get the download button. I may reupload somewhere and post a link when I get it downloaded.

http://www.filefactory.com/file/28u...PJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip
Enviado desde mi Moto G (4) mediante Tapatalk

So i did the same thing as you by flashing the xt143 file, and now my adb will no longer work. The phone will not give me an RSA key prompt. I've deleted the .pub file in data/user/android. Any tips would be appreciated.

jogawa said:
Yay! I got the phone back by flashing the stock ROM, then rooted using the guide, and I'm happy.
Thank you for pointing that stuff out xtermmin! I never thought to look for a ROM file with a name other than one that started with xt1644, and couldn't figure out how to search the directory.
You saved me.
Thanks again!
J
Click to expand...
Click to collapse
I'm getting a "could not find 'meta-inf/com/google/android/update-binary'" error when I try installing zip with TWRP and when I try sideloading. Any idea why?

acharlest said:
I'm getting a "could not find 'meta-inf/com/google/android/update-binary'" error when I try installing zip with TWRP and when I try sideloading. Any idea why?
Click to expand...
Click to collapse
Which zip? The stock ROM zip? You can't flash it via TWRP. You have to boot into bootloader mode, connect to a computer, and flash via fastboot or one of those "easy flasher" tools.

jogawa said:
I just got my xt1644 (G4 Plus, US version) yesterday and was trying to get root.
I got through successfully:
1) Unlocking bootloader.
2) Flashing TWRP.
3) Flashing the boot.img from the Root-motog4-athena-xt1641-xt1643.zip file (maybe a mistake, but read on).
4) Flashing SuperSU.
So then, I HAD root, but no WiFi. Seemingly others had this problem, so I added the ro.securestorage.support=false to the build.prop.
Nope. Still no WiFi. So I tried to change the build.prop BACK by deleting that line. Then, on the next boot, it stays in the "Your bootloader is unlocked" screen and does not boot to system.
I DO have bootloader access, and TWRP still works.
So, if anyone has:
1) A stock build.prop for the xt1644, or
2) New ideas, or
3) Access to the stock rom for the xt1644, which I cannot fiind,
PLEASE let me know.
Thanks!
J
Click to expand...
Click to collapse
Stock roms for the 1644 can be found here https://www.androidfilehost.com/?a=show&w=files&flid=72578

Luniz2k1 said:
Stock roms for the 1644 can be found here https://www.androidfilehost.com/?a=show&w=files&flid=72578
Click to expand...
Click to collapse
Read post #2.
Also, "ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip" is not for the US models. It's for the Indian model.

guys help me i have moto g4 plus 32 gb(india) and i flashed this firmware but now my fingerprint doesnt work and network also i have to erase the modem1 &2 then i flash modem NON-HLOS.bin after that my network works but no fingerprint ???
\XT1626-XT1640-XT1641_ATHENE_6.0.1_MPJ24.139-23.1_cid50_subsidy-DEFAULT_CFC\
w Folder>fastboot getvar all
(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: ZY2238ZFWQ
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 3559230000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Aug 7 21:45:14 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-23.1/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.24.1.athene.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband[0]: M8952_70004.04.03.32R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gcf01273 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld52) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Thu Apr 28 13:04:48 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 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin

Luniz2k1 said:
Stock roms for the 1644 can be found here https://www.androidfilehost.com/?a=show&w=files&flid=72578
Click to expand...
Click to collapse
Any way of knowing if the file that was just uploaded on Oct 20 is for XT1644?

Based on the name it seems to be the one that I am using now in my XT1644. But I got my file from the other place...

I just bought a XT1644 off ebay for cheap that isn't reading the sim and also isn't able to work with wi-fi either. I am hoping that it's also a case of incorrect firmware having been flashed on it. Keep your fingers crossed for me. LOL

doctor_evil said:
I just bought a XT1644 off ebay for cheap that isn't reading the sim and also isn't able to work with wi-fi either. I am hoping that it's also a case of incorrect firmware having been flashed on it. Keep your fingers crossed for me. LOL
Click to expand...
Click to collapse
Hope is not that one that the owner was over here trying every possible solution without success...

doctor_evil said:
I just bought a XT1644 off ebay for cheap that isn't reading the sim and also isn't able to work with wi-fi either. I am hoping that it's also a case of incorrect firmware having been flashed on it. Keep your fingers crossed for me. LOL
Click to expand...
Click to collapse
Did you use PayPal? If the owner didn't warn you about the problem and listed it as a working phone then you can get a refund and return it. If you didn't use PayPal you may be stuck with it.

SoNic67 said:
Hope is not that one that the owner was over here trying every possible solution without success...
Click to expand...
Click to collapse
The seller appeared to specialize in used phones, possibly a pawn broker, or a cell phone reseller that does trade-ins. Those are usually the best kind of sellers, as they know enough to see there is a problem and will document it and price it accordingly, but they don't have the time or patience to fool with actually trying to fix the issue.
I will post back with my success or failure. I caused a original Gen Moto G to behave in the exact same fashion when I flashed the wrong firmware on it, and I was able to fix that one with a little trial and error. I learned a valuable lesson on being more careful, and that it was possible to just flash the radio from the firmware zip files instead of flashing everything.
---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------
pastorbob62 said:
Did you use PayPal? If the owner didn't warn you about the problem and listed it as a working phone then you can get a refund and return it. If you didn't use PayPal you may be stuck with it.
Click to expand...
Click to collapse
The issue was documented in the ebay listing, with photos showing the blank IMEI info. I've had success in fixing this exact issue on a original gen Moto G after I accidentally flashed the wrong version of the firmware on it. I wound up using the UK radio for it to unbrick that one's cell radio.

Yeah, it needs to be the exact same radio.
Moto has a backup partition for bootloader and radio, and on flashing wrong ones it restores the "correct" one when booting with factory Android firmware. That's why after flashing TWRP, booting all the way into stock Android, it will be reverted to the normal bootloader. That's why we can flash LA.BR (Latin America / Brasil) firmware on our US phones - the baseband is "corrected" at the boot time.
But if you boot with a different that stock firmware, after flashing the wrong radio, than the "backup" capability is lost and subsequent firmwares need to have the exact original radio. And the "repair flash" of the baseband (radio) needs to be done with NON-stock firmware, because that one will "revert" the firmware to the old, wrong, one.
Don't forget, besides the software differences between models, there are also hardware ones.

I got it in the mail today. I flashed it with the ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml version of the firmware, and it fixed the issue. It did give me an error about flashing the recovery, which leads me to believe that it probably had a slightly newer version of the firmware installed. It did come minus the back cover. Does anyone know a good US seller with OEM replacement back covers for the XT1644? I ordered one from a chinese seller on ebay but it's going to take a long time to get here. I bought a nice looking Hybrid case to put on it, but not sure if it would be safe to use it without the back in the hybrid case. I worry about moisture getting into the phone. I do carry my phones in a holster on my belt instead of keeping them in a pocket though. So far I really like the Moto G4 Plus it's much nicer than my 2nd Gen Moto X, and much thinner and lighter.

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.

Difficulties to remove HARDBRICK from MOTO G4 PLUS

Hi guys, I'm new here and I just wanted to know if someone else have had this issue too and knew how to solve it.
Yesterday I was playing pool on my phone when suddenly it turned off. I though the battery was very low but I had barely charged it. When I was trying to turn it on it didn't respond, I connected the charger and noticed that the only thing that was working was the LED and the screen never turned on again, I realized that it was a hardbrick.
I guess the cause was that a few days ago I changed the kernel, I installed Elemental X kernel, but I didn't like how it was working on my device so I restored the backup with the RR ROM I always use and everything was normal until yesterday.
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
I use a zip file as help through adb commands on my laptop and the Fastboot Flash Mode (Secure) on my device.
I don't know what else to do and the problem is unknown for now.
Would it be the bootloader?
Is there a problem if the OEM is locked?
Is the non-existent IMEI interfering?
Am I doing things right?
What else should I do?
PS: It's obvious that I'm desperate and I know that is possible to save it.
Thanks for reading I hope someone answer.

Caney said:
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
Click to expand...
Click to collapse
That's not good, flashing wrong firmware can be dangerous to losing fingerprint and losing IMEI.
Get latest December's patch ROM from link thred and try to flash it. : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work

The device is in Fastboot Flash Mode (Secure), is it necessary to do that?

Caney said:
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Click to expand...
Click to collapse
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it

stehaworth said:
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
Click to expand...
Click to collapse
stehaworth said:
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
Click to expand...
Click to collapse
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.

Caney said:
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Click to expand...
Click to collapse
Tbh.... I'm not too sure... But I would start at looking into flashing full Moto stock image via fastboot (see other thread for details)

Hey, I think I have lock my bootloader accidentally :'c When I try to put the commands to flash firmware it throws me this:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
error: cannot load 'gpt.bin'
How do I unlock it?

You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all

C:\Users\hp>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 5
(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: b61bc8aa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 57A9A70100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.291s

@Caney from this data, i can see bootloader version is old, so you can try blank-flash with September's gpt and bootloader.
Follow (link below) thread for it, and where it says about download gpt and Bootloader files, go for September's one (2nd link there)...
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
When you get bootloader (after blank-flash), flash December's update.

____Mdd said:
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
Click to expand...
Click to collapse
Why isn't that good?

Caney said:
Why isn't that good?
Click to expand...
Click to collapse
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...

____Mdd said:
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
Click to expand...
Click to collapse
Oooh man, can you please attach the link of that gpt here? I don't find it.

Caney said:
Oooh man, can you please attach the link of that gpt here? I don't find it.
Click to expand...
Click to collapse
GPT and bootloader of the September 2017 stock ROM update (NPJS25.93-14-10) - bootloader version B1:06. https://drive.google.com/open?id=0B-GUyOfb8Ogzc25FdW1WUDBMS1U
GPT and bootloader of the December 2017 stock ROM update (NPJS25.93-14-13) - bootloader version B1:07.
https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
However, I would caution against just using these files, and suggest that you update fully by flashing the entire stock September or December 2017 ROM. Your bootloader is from the November/December 2016 firmware (B1:03) so just updating your bootloader isn't a good idea, especially when it comes to OTA updates.
Alternatively, if you want to reflash the stock ROM that has the same bootloader version as your reported bootloader, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369

I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?

Caney said:
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Click to expand...
Click to collapse
Are you following a guide to help you flash?
Generally for any flashing via fastboot (e.g. for stock ROMs or for TWRP)
1)Install the ADB and Motorola drivers as directed by the guide.
1a)Extract the stock ROM zip file (should be about 2 GB in size extracted), copy all the files to your ADB folder (so they're on the same level as your adb.exe and fastboot.exe).
2)Reboot your device to the bootloader (fastboot mode) and connect to your computer via USB. Preferably this should be the same cable as came with your device or another high quality data + power USB cable.
3)Open the ADB terminal on your computer and verify that your device is communicating by typing 'fastboot devices' in the ADB terminal, without quotes. This should return your device's serial number.
4)If so, then proceed with flashing as per the guide's fastboot commands. They are the same as the stock ROMs for Moto G4/Plus devices have followed the same layout (7 sparsechunks for system, for example). If you do not wish to re-lock your bootloader, then do not use the two OEM lock begin or the OEM lock commands. If you wish to try to keep your data, then you can omit fastboot erase userdata. However, with your device in the state it is, it may be worth thinking about a fresh start and erasing your userdata.
For omitting bootloader re-locking and trying to preserve your data (though be aware you may have to wipe anyway, the following fastboot commands should suffice.
Code:
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
You can either edit a flashing script to mirror these commands and use the script or enter the commands, individually and in order, by copypasting each line into the ADB terminal, then executing. Ideally, you want to see [OKAY] before you proceed. You may see errors about 'Image signed with bad key' if you're actually still unlocked, that's normal.
However, if you see any other errors, such as pre-flash validation or security downgrade, then you will need to use a newer stock ROM. Depending on which blankflash you used, the September 2017 or December 2017 stock ROMs would be suitable candidates.

This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.

Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
Click to expand...
Click to collapse
After flashing bootloader file from September ROM, your bootloader will be automatiically updated to B1.06 and same apply for December ROM.
But you have used the blank flash file so it is recommended to downloading the June 2017 fastboot ROM and flashing that in fastboot.
Caney said:
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
As of Windows PowerShell of WIndows 10 still it doesn't fully supported for all Commands and Features so Its better to use CMD or ADB.

Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
Then you may wish to try manually flashing each command individually, and in order, ensuring you see [OKAY] before continuing. The script may proceed too quickly to see if it's all worked, so manually flashing is another option. You could always add 'pause' before 'reboot' in the script (without quotes) to let you review the flash before rebooting.
As for Powershell instead of cmd, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/help/installing-twrp-using-powershell-t3727761/
As for updating bootloaders, I would recommend it - your bootloader is a crucially important piece of firmware and should stay at the same patch level as your system/device firmware. This should reduce the number of complications you may face and also ensure that OTA updates go more smoothly.
Be aware that the B1:06 bootloader in the June 2017 and September 2017 security patches (NPJS25.93-14-8 and NPJS25.93-14-10) close a bootloader vulnerability, which makes downgrading to an older stock ROM even more risky as it appears Motorola does not like you downgrading. Strictly speaking, it's not the act of downgrading, but the act of taking an OTA update whilst downgraded - the mismatch between your newer bootloader patch level and the older stock ROM can hard brick your device should you attempt to install an OTA update.
Furthermore, with the December 2017 stock ROM patch, bootloaders are updated to B1:07, meaning our current latest blankflash is not likely to work (blankflashes older than your current bootloader, corrupted or not, do not appear to be permitted to flash to your bootloader). So be careful when updating and flashing anything to your device if you choose to update to the December 2017 patch.

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 )