Database Users

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.

XT1580 - Persistant bootloop - help

Hi Guys,
So Tuesday morning woke up to my phone cycling through the "M - powered by android" screen. Have absolutely no idea why, though previous to placing it on the charger it had gotten down to 4% battery and I switched it off.
Anyway I have tried during the week to resuscitate the phone with many different methods posted here but still can not get it past the M logo loop
History of phone is:
March: 64GB model arrives with 6.0 reinstalled
Unlocked and Rooted the phone in March and installed TWRP
Made own recovery/backup in July - can't rember why but it seemed like a great idea at the time
At end of September Flashed phone to 7.0 - no problems there
Running fine until
Tuesday morning 1/11 from nowhere bootloop from hell hits
So in past 4 days I've tried in order (and some repeatedly):
Turning off, switching back on
Turning off, leave phone for an hour, switching back on
Turning off overnight > switching on
wiping caches
Wiping caches from cold start
draining completely flat > complete charge > wipe data from cold start > boot Still boot loop
Quickboot menu booting into recovery > TWRP > tried recovery (went fine but still bootloop)
Quickboot menu booting into recovery > TWRP > tried flashing 7.0 again (also went fine still bootloop)
Quickboot menu booting into recovery > TWRP > tried flashing 6.0 stock (also went fine still bootloop)
From quickboot menu tried RSD Lite stock flash - (failed at 3/29 gpt.bin)
From quickboot menu manually tried flashing 6.0 stock EU rom (as per instructions here using mfastboot and cmd window in windows 8 64 bit - flashed ok but still boot loop)
From quickboot menu manually tried flashing 6.0 stock MX rom
From Quickboot menu Manually tried flashing EU and MX 6.0 stock roms including the recovery command line (so now I don't have TWRP on the phone, though I am sure it will flash back easy enough).
After reading countless threads, I really thought by the time a manual flashing stock the phone would be working by now. Have I missed something obvious? Is there something else I should do? It seems stuck somewhere just before it boots - like if the boot partition in windows looses its boot flag.
Any ideas as to what to do next appreciated

In case it helps any the retvar details are:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8994-A8.56
(bootloader) product: kinzie
(bootloader) board: kinzie
(bootloader) secure: yes
(bootloader) hwrev: 0x8301
(bootloader) radio: 0x2
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S16 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x4
(bootloader) cpu: MSM8994
(bootloader) serialno: ZY223#####
(bootloader) cid: 0x0007
(bootloader) channelid: 0x51
(bootloader) uid: A531EC011B000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358962########
(bootloader) meid:
(bootloader) date: 01-23-2017
(bootloader) sku: XT1580
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Oct 19 23:21:52 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/kinzie_reteu/kinzie_uds:7
(bootloader) ro.build.fingerprint[1]: .0/NPKS25.200-12-4/4:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.201.4.kinzie_rete
(bootloader) ro.build.version.full[1]: u.reteu.en.EU
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8994_1255341.44.01.95.01R KINZIE_ROW_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ga0e0551 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT M
(bootloader) kernel.version[3]: on Jul 10 09:14:29 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VA8.56-0-g7c62395
(bootloader) rpm.git: git=fa49dab
(bootloader) tz.git: git=MBM-NG-VA8.56-1-gf12946f
(bootloader) hyp.git: git=MBM-NG-VA8.56-1-gf12946f
(bootloader) sdi.git: git=298d574-dirty
(bootloader) pmic.git: git=MBM-NG-VA8.56-0-g7c62395
(bootloader) aboot.git: git=MBM-NG-VA8.56-0-g09a6e4e
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: retapac

Ok so I've been doing some more flashing - the flash process works fine no errors. I've put TWRP back on and it works fine when accessed via fastmoot menu then into recovery.
Frustratingly despite all recoveries flashing fine (logo's updating correctly as per version etc) it will not get past boot. Makes me think this phone is headed for the bin.
Is there a way to test the pre-boot memory or a tool to see what is going on at that stage of the boot process? perhaps a tool to check the hardware is working properly?
Cheers again
Val

Check my last 20-30 post, in one of them you'll find possible solution.
I've had similar problem - it's faulty file system on one of the partitions, exactly few first bytes which for some reason can't get formated, factory flash doesn't fix it either.
All you need to do is fill up partition which zeroes.

Hi TeddyBeers,
Thank you for your response.
been through the last 20-30 odd posts. Is this the instructions in the post you are referring to?
" In most cases it's MISC partition.
To fix it need to run this command from adb
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
or just through TWRP ->Advanced -> Terminal Emulator
Code:
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
If this doesn't help (like in my case) than overwrite system and data partition - THIS WILL DELETE ROM AND ALL DATA
For system partition
ADB
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/system
TWRP ->Advanced -> Terminal Emulator
Code:
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/system
For data partition
ADB
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/data
TWRP ->Advanced -> Terminal Emulator
Code:
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/data"
After zeroing all these partitions, which instruction do you recommend flashing with - ie mfastboot, Sideload, reflash TWRP and then install?
Cheers
Val

So a brief update - Tried the flashing zeros as per Teddybeers suggestion using terminal in TWRP. Still same result, phone is responsive to flashing from fastboot (and twrp after reinstalling TWRP) but phone will not get past the boot logo before re-starting and repeating
My thoughts (and googling) is leading me to think blank-flashing the phone is the only way to go.
The only guide I have been able to find suggests RSDlite. As I can't see the phone using RSDlite, is there a way to blank flash from fastboot mode? Or TWRP?
Cheers as always

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.

Moto E4 XT1765 (MetroPcs) Super Hard-Bricked?

Hello Everyone, I was attempting root and well alot of things didn't go as planned and as a result I have no recovery, oem-lock as been enabled and I'm only able to boot into fastboot. a "fastboot getvar all" is as follows
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BA.26(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: d6a09b30
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(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) poweroffalarm: 1
(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) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VBA.26-0-g87d0ac5
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.323s
Is there anyway back from this? Or is it looking like "get another off ebay, and don't be so [email protected] careless!" Thanks in advance.

tboned82 said:
Hello Everyone, I was attempting root and well alot of things didn't go as planned and as a result I have no recovery, oem-lock as been enabled and I'm only able to boot into fastboot. a "fastboot getvar all" is as follows
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BA.26(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: d6a09b30
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(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) poweroffalarm: 1
(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) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VBA.26-0-g87d0ac5
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.323s
Is there anyway back from this? Or is it looking like "get another off ebay, and don't be so [email protected] careless!" Thanks in advance.
Click to expand...
Click to collapse
Might start here. I'm not sure and can't look right now myself.
http://www.spflite.com/Index.html?Downloads.html
Sent from my [device_name] using XDA-Developers Legacy app

@tboned82
You haven't unlocked the bootloader. OEM lock is not the proper command. You can't just do oem unlock either. You have to get an unlock code from Motorola. You haven't said what you actually did, what happened, what guide you followed, how far you got, nothing.
You have to give some info before anyone can help you.

madbat99 said:
@tboned82
You haven't unlocked the bootloader. OEM lock is not the proper command. You can't just do oem unlock either. You have to get an unlock code from Motorola. You haven't said what you actually did, what happened, what guide you followed, how far you got, nothing.
You have to give some info before anyone can help you.
Click to expand...
Click to collapse
Oh but I have unlocked the bootloader, I got a code and everything I followed all the instructions on this guide
HTML:
https://forum.xda-developers.com/moto-e4/moto-e4-qualcomm-roms-kernels-recoveries--other-development/guide-xt1766-stock-firmware-restoration-t3775347
as well as this one as well
HTML:
https://forum.xda-developers.com/moto-e4/how-to/complete-noob-guide-to-rooting-metropcs-t3701234
I ran into trouble when I formatted /data partition (just wiped it clean, without a way to boot into the system) I then followed the guide in the first link and I'm where I'm at now it's when I downloaded the files from the first link and started issuing the given commands in when oem-unlock when away and it was locked again. But yes I did have the device oem unlocked at one point.

whodisname said:
Might start here. I'm not sure and can't look right now myself.
http://www.spflite.com/Index.html?Downloads.html
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have done this, without success...I'm just using windows in a Virtual enviroment, though I'm able to access fastboot commands in both my virtualized windows enviroment and my native Manjaro one as well.

tboned82 said:
I have done this, without success...I'm just using windows in a Virtual enviroment, though I'm able to access fastboot commands in both my virtualized windows enviroment and my native Manjaro one as well.
Click to expand...
Click to collapse
Glad you started a thread on this. There is a way out of this.
@kartik verma has a guide that can help you out on this. Since your bootloader is locked again it won't matter if you run the command to lock it back. However, with our variant you might have some trouble, so READ CAREFULLY steps 1-3.
https://forum.xda-developers.com/moto-e4/how-to/moto-e4-guide-stock-firmware-restore-t3661684
Things You Should Know Going Into It:
1. On our variant when you try to erase anything via fastboot is will say "PERMISSION DENIED". Run the command anyway and see what I mean - so you can effectively skip the ERASE PART of the guide. Instead, go straight to reinstalling over the files already there. It does that even when the bootloader is unlocked, and I have no idea why.
2. Download the firmware officially from Motorola from here:https://firmware.center/firmware/Motorola/Moto E4/Stock/ From there, download the following PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml.zip. It's the earliest one I know of that came on my phone that will not give you any problems flashing Magisk v14 later once you restore. Very important.
3. Extract the firmware to a single folder to your desktop. Makes it easier navigating later.
4. Download Minimal ADB and Fastboot. Don't use any other Fastboot. Trust and believe, its easier; Save Minimal ADB and Fastboot to your C:/ Drive.
5. In order to flash the files accordingly, you are going to have to pull firmware individual files (i.e. boot.img and system sparschunk files) to the Minimal ADB folder. Keep track of them.
6. You really only need to follow steps 1-3. Don't go past there.
---------- Post added at 03:52 AM ---------- Previous post was at 03:45 AM ----------
In my case when my phone hard bricked (wouldn't boot past recovery splash or the N/A splash) I could still get to fastboot. I flashed boot.img, and ALL of the system sparse chunk files. That brought me back enough to load recovery and delete everything and flash anew. However, If you think you've deleted the system, plus your bootloader is locked again you're probably going to have to reflash all of those files. I'd say as long as you have fast boot, reflash through fastboot boot.img, and every single system_sparsechunk files. Reboot and see what happens. If it doesn't work, keep on flashing until you re-restore the phone completely. If you start getting errors, refer to the rest of kartik's guide. (Steps 4- to completion) and ask me questions. There really isn't a definitive one size fits all variants for this phone - ours is special.
---------- Post added at 04:06 AM ---------- Previous post was at 03:52 AM ----------
Here is my getvar for you to see in comparison (I blocked off sensitive info like my IMEI and UID)
Code:
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-msm8917-BA.09(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: ZY224GRCFF
(bootloader) cid: 0x0016
(bootloader) channelid: 0x8e
(bootloader) uid: ********00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *classified by order of your government*
(bootloader) meid:
(bootloader) date: 09-13-2017
(bootloader) sku: XT1765
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/perry_metropcs_c/perry:7.
(bootloader) ro.build.fingerprint[1]: 1.1/NCQ26.69-46/46:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.46.perry_metro
(bootloader) ro.build.version.full[1]: pcs_c.MetroPCS.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8917TMO_18.08.04.12R PERRY_NA_UMTS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g9acc907-0000
(bootloader) kernel.version[1]: 6-g486eb8a ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 20 09:51:52 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VBA.09-0-ge2011ab
(bootloader) rpm.git: git=MBM-NG-VBA.09-0-gc6ac81e
(bootloader) tz.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) devcfg.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) keymaster.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) cmnlib.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) cmnlib64.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) prov.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) aboot.git: git=MBM-NG-VBA.09-0-gcae5764-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs

Well I was hoping to return with a success story, unfortunately that's not the case, I have tried many times on both my Linux and virtualized Windows environment of flashing files from the provided link without luck, as a result of the oem_lock bit being mysteriously reset, (actually upon googling "Failed to initialize partition table" I've found many results, mostly relating to the Moto G4 with others experiencing the same mysterious relocking issue I have)
Since I was getting nowhere very slowly via Fastboot I had started looking elsewhere for a solution and came upon Blankflash (initialized my issuing "fastboot oem blankflash" and operated via the "Qpst" Software squite) which looks very promising except for our stock (and most others actually) firmware files not including the necessary prog_emmc_firehose_8917.mbn files nor the rawprogram.xml files either (
HTML:
https://forum.xda-developers.com/watch-2/development/rom-bootloader-recover-huawei-watch-2-t3624657/post72744084#post72744084
short but alot of useful information on this method... and despite the generic naming of the firehose.mbn files I found they are very device specific I'm currently looking to see if there's a way to extract the information required from the stock Moto Firmware we currently have access to and covert them to the format required my Qfil, but information on flashing through the Qualcomm software is hard to track down.
Through my research I also came across some very interesting exploits that would also solve the flashing issues I'm having https://alephsecurity.com/2018/01/22/qualcomm-edl-2/ but (in my opinion) the methods of carrying out the exploits isn't explained very well, and as I don't understand assembly language am hesitant to experiment with.
My Questions
1. Does anyone have experience flashing through the Qpst suite and be able and willing to help with this?
2. Anyone with enough knowledge of assembly/programming to be able to write code for my device that'll disable the boot locking bit enabling me to flash the already provided Moto Firmware via Fastboot?
Thanks for anyone that takes their time into looking into this for me

tboned82 said:
Well I was hoping to return with a success story, unfortunately that's not the case, I have tried many times on both my Linux and virtualized Windows environment of flashing files from the provided link without luck, as a result of the oem_lock bit being mysteriously reset, (actually upon googling "Failed to initialize partition table" I've found many results, mostly relating to the Moto G4 with others experiencing the same mysterious relocking issue I have)
Since I was getting nowhere very slowly via Fastboot I had started looking elsewhere for a solution and came upon Blankflash (initialized my issuing "fastboot oem blankflash" and operated via the "Qpst" Software squite) which looks very promising except for our stock (and most others actually) firmware files not including the necessary prog_emmc_firehose_8917.mbn files nor the rawprogram.xml files either (
HTML:
https://forum.xda-developers.com/watch-2/development/rom-bootloader-recover-huawei-watch-2-t3624657/post72744084#post72744084
short but alot of useful information on this method... and despite the generic naming of the firehose.mbn files I found they are very device specific I'm currently looking to see if there's a way to extract the information required from the stock Moto Firmware we currently have access to and covert them to the format required my Qfil, but information on flashing through the Qualcomm software is hard to track down.
Through my research I also came across some very interesting exploits that would also solve the flashing issues I'm having https://alephsecurity.com/2018/01/22/qualcomm-edl-2/ but (in my opinion) the methods of carrying out the exploits isn't explained very well, and as I don't understand assembly language am hesitant to experiment with.
My Questions
1. Does anyone have experience flashing through the Qpst suite and be able and willing to help with this?
2. Anyone with enough knowledge of assembly/programming to be able to write code for my device that'll disable the boot locking bit enabling me to flash the already provided Moto Firmware via Fastboot?
Thanks for anyone that takes their time into looking into this for me
Click to expand...
Click to collapse
I'm just getting a notification about this now. Sorry about that. Did you ever unbrick the phone?
To answer your questions, I'm not hip to the Qpst suite. If flashing everything back in Command Prompt on windows didn't work, you may have very well bricked it.

Articul8Madness said:
I'm just getting a notification about this now. Sorry about that. Did you ever unbrick the phone?
To answer your questions, I'm not hip to the Qpst suite. If flashing everything back in Command Prompt on windows didn't work, you may have very well bricked it.
Click to expand...
Click to collapse
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success

Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
Click to expand...
Click to collapse
I'll try.
Please, in GREAT DETAIL, tell me everything you did to brick it. Step by step. And if you can, tell me the original baseband on the phone. Once I have that I can tell you better how to proceed.

Moto E4 XT 1765 hard brick
Articul8Madness said:
I'll try.
Please, in GREAT DETAIL, tell me everything you did to brick it. Step by step. And if you can, tell me the original baseband on the phone. Once I have that I can tell you better how to proceed.
Click to expand...
Click to collapse
i have unlock boot loader working fine on stock firmware version
NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool
plz help me out this headache

Mirani said:
i have unlock boot loader working fine on stock firmware version
NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool
plz help me out this headache
Click to expand...
Click to collapse
Let me see if I have this correctly.
You had a stock rom on your phone which you mentioned NCQ.
Then you connected your phone to the wifi.
Then you of your own volition took an update.
This update erased whatever you did trying to get root.
Then your phone bricked.
Now when you attach it to a PC it is showing HS_USB_Qdloader 9008
Is that right?
You need to pull the following firmware and try and flash it...PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml
I've never heard of your firmware. Try that firmware and flash it piece by piece and see if that gets you back working.

Hello, the same problem xt1765 metropcs HS_USB_Qdloader 9008, with that tool will get the firmware? Does not enter fastboot, help

If The phone does not enter fastboot mode you can only fix it by flashin the original stock firmware using SP flash tools and thr correct scatter fileusing format all including formatting the bootloader

TheLastAlphaUK said:
If The phone does not enter fastboot mode you can only fix it by flashin the original stock firmware using SP flash tools and thr correct scatter fileusing format all including formatting the bootloader
Click to expand...
Click to collapse
Again you are answering people with facts about the mediatek version, these ones have the Qualcomm version, therefore, SPflash tool does not apply

My bad cant I use the ADB sideload or update commands to reflash a stock firmware package. ? In kinda in a rush trying to answer all these questions I will look at it when I can sorry

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).