Sample Header Ad - 728x90

Recover bricked unrooted Moto G5 (bootloop)

1 vote
1 answer
458 views
My Moto G5 got stuck right after booting into Android, screen frozen at my Andorid home screen and was not responding. It was charging but battery was dead, like 1%. Don't know if that caused the issue. I had to remove the battery to turn it off. After that it never booted again: does start up animations, then asks the PIN, then remains stuck on Motorola logo.I suspect it is bricked? I **really** want to recover data but sadly it is not rooted, with no custom recovery. Just plain stock Android. I am able to enter fastboot and adb (with Stock recovery). Here's the getvar output
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: 7
(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: MSM8937
(bootloader) serialno: ZY32256S53
(bootloader) cid: 0x0032
(bootloader) channelid: 0x5b
(bootloader) uid: 153EB23800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxx
(bootloader) meid:
(bootloader) date: 06-13-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan  1  0: 6:47 UTC 1970"
(bootloader) ro.build.fingerprint: motorola/cedric_timit/cedric:8.1.0
(bootloader) ro.build.fingerprint: /OPP28.85-13/789a:user/release-key
(bootloader) ro.build.fingerprint: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: Blur_Version.28.41.12.cedric_timi
(bootloader) ro.build.version.full: t.timit.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_22.29.02.69R CEDRIC_EMEA_CUST
(bootloader) kernel.version: Linux version 3.18.71-perf-ga19fa3e (hud
(bootloader) kernel.version: soncm@ilclbld34) (gcc version 4.8 (GCC)
(bootloader) kernel.version: ) #1 SMP PREEMPT Fri Aug 17 09:23:26 CDT
(bootloader) kernel.version:  2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=MBM-NG-VB8.31-0-gbd76357-dirty
(bootloader) tz.git: git=MBM-NG-VB8.31-1-g26cc248
(bootloader) devcfg.git: git=MBM-NG-VB8.31-1-g26cc248
(bootloader) keymaster.git: git=MBM-NG-VB8.31-1-g26cc248
(bootloader) cmnlib.git: git=MBM-NG-VB8.31-1-g26cc248
(bootloader) cmnlib64.git: git=MBM-NG-VB8.31-1-g26cc248
(bootloader) prov.git: git=MBM-NG-VB8.31-1-g26cc248
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: timit
(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.062s
Is there any way to find out what is causing Android not to boot? which file/partition got corrupted, if any? I understand that there are several "images" in a Stock ROM, such as gpt.img, boot.img, oem.img... I am not sure about flashing these because I don't want to lose my data forever
Asked by likeeatingpizza (11 rep)
Nov 7, 2023, 07:33 PM
Last activity: Nov 11, 2023, 12:44 PM