Develop Bugs

Moto G5 stuck in bootloop

hi friends my moto g5 xt1677 is stuck in bootloop,able to access fastboot and recovery mode.I don't want to lose my data so is there any way I can get back my data.I have heard that if i update it to the latest security patch or current security patch i may be able to start my phone. I had december security patch installed.If anyone is having december ota file or february ota file please send the link.I am able to boot in recovery mode
recovery mode version below
motorola/cerdric_retail/cedric 8.1.0/OPPS28.85-19-2/73f5
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=07 FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3222CC4J
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc4
(bootloader) uid: 2A7E7F7700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358222070469919
(bootloader) meid:
(bootloader) date: 03-08-2017
(bootloader) sku: XT1677
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Dec 20 6:49:17 UTC 2018"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-ga87df5f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Dec 20 00:55:53 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3213759-dirty
(bootloader) devcfg.git: git=3213759-dirty
(bootloader) keymaster.git: git=3213759-dirty
(bootloader) cmnlib.git: git=3213759-dirty
(bootloader) cmnlib64.git: git=3213759-dirty
(bootloader) prov.git: git=3213759-dirty
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: amzin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.247s
C:\adb>

Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
https://mirrors.lolinet.com/firmware/moto/cedric/official/

G5
TheFixItMan said:
Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
can you guide me how to do this
Click to expand...
Click to collapse

G5
TheFixItMan said:
Flash stock firmware via fastboot without erasing user data
If it doesn't boot or bootloops you will have to erase userdata
can you guide me how to do this i dont want to lose my data
Click to expand...
Click to collapse

You could Google flash stock firmware moto g5
I've already provided link to firmware
If your phone bootloops etc you may have no choice but to erase data
Put phone in fastboot mode
Connect phone to PC via USB
Open a terminal/cmd window where you have fastboot files (Google is your friend) and firmware
Type the following in terminal window/cmd
Code:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata (only if you want to erase data or phone bootloops etc)
fastboot oem fb_mode_clear
fastboot reboot

I have problems to find a suitable firmware for my cedric 1676 (EU/Germany). The fastboot-Commands did not work with the rom-Versions out of the "RETAIL"-Folder.
--> Finally I had siccess with a version from the "RetEU"-Folder (perhaps "EU" means European Union?)...
some aditional informations about suitable versions.
https://www.hardreset.info/devices/motorola/motorola-moto-g5/faq/firmware-flash/
Now I want to return to Nougat (downgrade from Oreo to Nougat). I have a few questions:
- Can I use TWRP for downgrade to a Nougat Rom (Carbon Rom)?
- Which TWRP should I use (normal or 64bit)?
- Is there anything else to note?

Mobilettchen said:
I have problems to find a suitable firmware for my cedric 1676 (EU/Germany). The fastboot-Commands did not work with the rom-Versions out of the "RETAIL"-Folder.
--> Finally I had siccess with a version from the "RetEU"-Folder (perhaps "EU" means European Union?)...
some aditional informations about suitable versions.
https://www.hardreset.info/devices/motorola/motorola-moto-g5/faq/firmware-flash/
Now I want to return to Nougat (downgrade from Oreo to Nougat). I have a few questions:
- Can I use TWRP for downgrade to a Nougat Rom (Carbon Rom)?
- Which TWRP should I use (normal or 64bit)?
- Is there anything else to note?
Click to expand...
Click to collapse
Here is the firmware for your device
https://mirrors.lolinet.com/firmware/moto/cedric/official/TEFES/
If you still want to downgrade from oreo to nougat then just don't flash the gpt and bootloader, if you flash the device will hard bricked.
For custom roms you can use carbon ROM.
You need 64 bit twrp to flash.

@riyan65 - many thx for tips & support, and greetings to india
Why do you think that the "TEFES"-Version instead of "RetEU" (or even "RETAIL") ist suitable for European-specific radio bands?

Mobilettchen said:
@riyan65 - many thx for tips & support, and greetings to india
Why do you think that the "TEFES"-Version instead of "RetEU" (or even "RETAIL") ist suitable for European-specific radio bands?
Click to expand...
Click to collapse
For xt1676 the device firmware is TEFES, so I recommend you that firmware, if you want other firmware like retail or reteu you can flash it that also.

riyan65 said:
For xt1676 the device firmware is TEFES, so I recommend you that firmware, if you want other firmware like retail or reteu you can flash it that also.
Click to expand...
Click to collapse
OK - But TEFES is just *one* Software Channel, supporting the Cedric, in a specific Country. (NOT EU). I try it out. After Flashing the "Lenovo Moto Smart Assistent" did not recocnize my Cedric (no entry on "Software Chanel"). Retail is working on my phone

Mobilettchen said:
OK - But TEFES is just *one* Software Channel, supporting the Cedric, in a specific Country. (NOT EU). I try it out. After Flashing the "Lenovo Moto Smart Assistent" did not recocnize my Cedric (no entry on "Software Chanel"). Retail is working on my phone
Click to expand...
Click to collapse
Oh sorry I forgot to tell that, which ever software channel you flash nothing will happen as the device is not going to receive any more software updates so it does not affect any thing, as for cellular every firmware will work for every country.

Errors re-locking bootloader. xt1676 DS

Hi. I'm trying to block the BL again but I can't. By fastboot he tells me about allow oem, not being selectable in the developer menu he also tells me about oem not signed. The system version is XT1676_CEDRIC_RETEU_DS_8.1.0_OPPS28.85-13-6 I want to block it again since I probably sell it. Thank you.
?

takoa said:
Hi. I'm trying to block the BL again but I can't. By fastboot he tells me about allow oem, not being selectable in the developer menu he also tells me about oem not signed. The system version is XT1676_CEDRIC_RETEU_DS_8.1.0_OPPS28.85-13-6 I want to block it again since I probably sell it. Thank you.
?
Click to expand...
Click to collapse
How to re-lock bootloader
Code:
fastboot oem lock
fastboot oem lock
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 system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
The device will restart
Now reflash the entire firmware
Code:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

Thanks for the quick reply
Entering the fastboot oem lock command tells me ...
Check 'Allow OEM Unlock' in Developer Options
:crying:

takoa said:
Thanks for the quick reply
Entering the fastboot oem lock command tells me ...
Check 'Allow OEM Unlock' in Developer Options
:crying:
Click to expand...
Click to collapse
Assuming you are on stock rom
These steps may vary slightly as I don't have this device
Goto phone settings
Select About phone
Software information
More
Tap build number until it tells you you're a developer
Go back to settings menu
Now you can select developer options
Enable oem unlock and also enable USB debugging
Or Flash stock rom firmware first and then do the steps

Yes. Stock
oem unlock appears but is not selectable

takoa said:
Yes. Stock
oem unlock appears but is not selectable
Click to expand...
Click to collapse
It's probably greyed out as your bootloader is already unlocked - you're meant to enable it before you unlock the device
What happens when you type in fastboot mode
fastboot oem unlock
You may get a message to accept on the phone
You can also try re-flashing stock firmware via fastboot and then attempt to lock the bootloader

F:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 0ACE9A1B00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: **************
(bootloader) meid:
(bootloader) date: 11-07-2017
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 23:45:33 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.69.01R CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.183s
F:\adb>fastboot oem read_sv
...
(bootloader) Note: 0xFFFFFFFF indicates SV fuse read failure
(bootloader) BOOTLOADER = 0x2
(bootloader) RPM = 0x0
(bootloader) TZ = 0x0
(bootloader) AP = 0xB
(bootloader) MODEM = 0x0
(bootloader) MODEM JTAG = 0x1
(bootloader) boot = 0xB
(bootloader) recovery = 0xB
(bootloader) oem = 0xB
(bootloader) system = 0xB
OKAY [ 0.032s]
finished. total time: 0.033s
F:\adb>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.010s]
finished. total time: 0.011s
F:\adb>fastboot oem unlock
...
(bootloader) invalid boot state
OKAY [ 0.005s]
finished. total time: 0.006s
F:\adb>fastboot flashing unlock
...
(bootloader) Already unlocked for flashing.
OKAY [ 0.006s]
finished. total time: 0.008s
F:\adb>fastboot flashing unlock_critical
...
(bootloader) Not supported. Must use OEM signed bootloader.
OKAY [ 0.011s]
finished. total time: 0.014s
F:\adb>fastboot flashing get_unlock_ability
...
(bootloader) Flashing Android images permitted
OKAY [ 0.007s]
finished. total time: 0.009s

and ...
C:\Users\***********\Desktop\adb\XT1676_CEDRIC_RETEU_DS_8.1.0_OPPS28.85-13-6_cid50_subs
idy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot flash oem oem.img
target reported max download size of 535822336 bytes
sending 'oem' (148900 KB)...
OKAY [ 5.507s]
writing 'oem'...
OKAY [ 1.888s]
finished. total time: 7.426s
:silly:

I would Re-flash the entire stock firmware including gpt & bootloader and then try again
You can also try and flash magisk and then see if you can enable oem unlock again

I finally got it ¡¡¡ :victory:
I downgrade to nougat and installed magisk FROM twrp and was able to select oem unlock in developer options.
Maybe the downgrade was not necessary but despair made me try and risk.
THANK YOU VERY MUCH AGAIN. :good:

XT1922-2 JETER softbricked (newbie)

Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.

Here's all the variables if that's helpful:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-aljeter_retail-b1f322d35c1-2
(bootloader) version-bootloader[1]: 00404
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZL4223V3D5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 3572CA9F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 08-29-2018
(bootloader) sku: XT1922-2
(bootloader) carrier_sku: XT1922-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 5 11:34:57 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter_n/aljeter_n:9/PPP
(bootloader) ro.build.fingerprint[1]: S29.55-35-18-7/6a0d0:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.7.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: M8937_34.42.05.98R JETER_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g3e480e17e11
(bootloader) kernel.version[1]: f-04280-g407726838ebf ([email protected]
(bootloader) kernel.version[2]: 8) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Sat Apr 4 12:
(bootloader) kernel.version[4]: 24:37 CDT 2020
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-0d2031d6b9-200404
(bootloader) rpm.git: MBM-2.1-aljeter_retail-af31f6ae-200404
(bootloader) tz.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) prov.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) aboot.git: MBM-2.1-aljeter_retail-b1f322d35c1-200404
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: eegb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.152s
Click to expand...
Click to collapse

xt123xt said:
Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.
Click to expand...
Click to collapse
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Ruben8ap said:
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
Click to expand...
Click to collapse
Thank you for your reply.
It gave me an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system aljeter.zip
target reported max download size of 535822336 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 411641469 is not a multiple of the block size 4096
sending sparse 'system' 1/3 (523260 KB)...
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
OKAY [ 17.139s]
writing 'system' 1/3...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.145s
Click to expand...
Click to collapse

Try these https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETEU/

I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.

xt123xt said:
I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.
Click to expand...
Click to collapse
Download this file --> https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Then you open the CMD and put in fastboot devices and the phone code should appear, of course the phone should already be in fastboot mode for that moment.
If everything is in order you should copy these commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Just select all then copy and paste them into the CMD and the stock installation process will start :fingers-crossed:

I suppose you've saved my phone. Thank you very much!

Hi, I carried out the instruction as given above by Ruben8ap, on my XT1922-2 Aljeter Moto G6 Play phone, and have recovered my phone, so I can boot into the OS, but I have lost access to Fastboot and TWRP, etc. So, I now have a phone that is stuck with this OS and no way of gaining root access or anything else. My bootloader says AP Fastboot Flash Mode (Secure). I cannot flash anything from the stock recovery on the SD card. Can anyone advise how I can get out of this state?

XT-1675 with locked bootloader [HELP]

Hi,
I have a cedric xt-1675 with locked bootloader (i have a key to unlock and i tried unlocking it through fastboot it says its disable) and when I try to load into recovery mode it gave me error
FAILED TO PASS VALIDATION. BACKUP TO FASTBOOT
BOOTUP FAILED
I tried flashing firmware through fastboot white doing mfastboot flash partition gpt.bin
C:\Users\Abdul Rafy\Desktop\New folder\ar\boot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.077s
all other flash commands works fine except mfastboot flash partition gpt.bin
Thanks

You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options

TheFixItMan said:
You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options
Click to expand...
Click to collapse
thanks for the reply, I never have unlocked my device before it has locked bootloader since start. anyway, I have tried "fastboot oem unlock UNLOCK_KEY" it says enable oem unlocking from developer option and the problem is i couldn't get into phone not even into recovery just fastboot. It used to get stuck at moto logo but now when I try to boot normally it says
Failed to verify hab image boot
failed to validate boot image
Error: Failed to pass validation. backup to fastboot
Boot up failed
and if I try to go into recovery, it says
Failed to verify hab image recovery
failed to validate recovery image
Error: Failed to pass validation. backup to fastboot
Boot up failed
another thing I did try Software repair assistant but it gave me error on 47%

Here the getvar just in case:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A4 FV=00000000000000A4
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x4e
(bootloader) uid: 0295944600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Last time flashing failed
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 03-07-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 8: 2: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-19-4-2/3447de:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.301.2.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_46.42.02.75R CEDRIC_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0001
(bootloader) kernel.version[1]: 6-g6e15bdb ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Mar
(bootloader) kernel.version[3]: 4 18:13:35 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3f87a46
(bootloader) devcfg.git: git=3f87a46
(bootloader) keymaster.git: git=3f87a46
(bootloader) cmnlib.git: git=3f87a46
(bootloader) cmnlib64.git: git=3f87a46
(bootloader) prov.git: git=3f87a46
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tescogb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above

This is because the boot.img you flashed is not signed by Motorola and its failing to pass verification
If you were trying to unlock the bootloader you should have followed the correct process and enabled adb and oem unlock from the dev options
Never flash firmware on a locked bootloader - if it goes wrong you have no chance of correcting it
You basically have two options now
Try and find firmware that will flash fully on your device
Firmware can be found here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Code:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Or take to a repair shop for either a motherboard replacement or if possible flashing with a jtag

Cedric XT-1676 firmware error:

ERROR: This package requires from an Android 8.1 stock ROM build.
Such a bug prevents me from updating the lineage-18.1-20220116-microG-cedric.zip image to a newer version,
e.g. lineage-18.1-20220301-microG-cedric.zip
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZYxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: AADB0F5700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-20-2018
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:17:47 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.69.01u CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.061s
I installed the stock rom via fastboot from the image:
CEDRIC_OPPS28.85_13_6_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
using this commands:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I installed TWRP, wiped the / system partition, / data, / cache,
then I installed lineage-18.1-20220116-microG-cedric.zip + Magisk.
the system is working fine.
However, the update to lineage-18.1-20220301-microG-cedric.zip stops on a bug with the firmware version.
I download lineage images from here:
cedric
Cheers

Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com

TheFixItMan said:
Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Click to expand...
Click to collapse
Thank you very much for that firmware link... I was ready to give up.
Oddly, the official Motorola Repair tool does not install a Lineage-friendly version of the stock firmware.
If it helps any other noob, I used this site to install the stock firmware:
Install Stock Firmware on Moto G5 via Fastboot Commands
In this comprehensive tutorial, we will show you how to install stock firmware on Motorola Moto G5 via Fastboot commands and unbrick it.
www.droidwin.com

Hi
I Installed via fastboot:
CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
After this operation, my Cedric does not have a unique IMEI number.
As a result, the SIM card does not work at all, I can only make emergency calls.
fastboot getvar all 2>&1| grep -i imei
(bootloader) imei: 356476085352435
I tried to fix IMEI according to this thread:
Moto G5 Cedric - Repair Imei = 0
After being in a LineageOS ROM, I decided to reinstall the Stock Firmware od Moto G5 Cedric through ADB, but after that the phone signal was lost, and both IMEI appear in 0, Has anyone else had that problem, or know the solution?
forum.xda-developers.com
I did several times (after installing stock ROM, after installing LineageOS, after installing LineageOS-microg):
fastboot erase modemst1; fastboot erase modemst2 ; fastboot erase cache
Erasing 'modemst1' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'modemst2' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'cache' OKAY [ 0.017s]
Finished. Total time: 0.020s
However, to no avail, the phone has no IMEI number on any SIM card.
It seems the XT1676 European version is more resistant to IMEI repair attempts.
Cheers

My IMEI was also zeroed by the stock ROM.
I tried using the recommendations in the following link, but I was ultimately unable to recover the IMEI from within the stock rom. Flashing LOS worked.
Moto g5 plus IMEI 0 after flashing anything? Read on!
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required! Prerequisites: U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on...
forum.xda-developers.com

Same here. Unable to recover IMEI for XT1676. The suggested procedure just does not work in this phone version with latest stock ROM OPP28.85-19-4-2.