Help me Flash Stock Rom Moto C XT1758
Help me Flash Stock Rom Moto C XT1758
(06-03-2020, 02:53 PM)X3nonWell I tried it on another computer, as you can see in the images, I also tried all the USB ports, I used 4 different cables (including the original one I found, and they were all tested), the battery is practically 100% too, but I got the same results as the previous computer. I know the cable is not bad because it recognizes on the fastboot and I already used these cables on it and it also works perfectly on my old Galaxy Y. Oh and I know that the cable works because the only thing I can access is the fastboot and the two PCs recognize it perfectly the Moto C in fastboot mode.(06-03-2020, 05:25 AM)AndersonSilvaa I tried what you said, but it didn't change the results on the first attempt without pressing any buttons and the second attempt by pressing the minus button.
well, your problem doesn't seem to be from the flashing tool, neither is it from the DA file (cause someone has previously confirmed the DA to work on the same device model). You've tried a different PC and USB cables as you said, which leaves USB port on the phone
you can try changing that then retry flashing the device
(08-03-2020, 05:02 AM)AndersonSilvaa(06-03-2020, 02:53 PM)X3nonWell I tried it on another computer, as you can see in the images, I also tried all the USB ports, I used 4 different cables (including the original one I found, and they were all tested), the battery is practically 100% too, but I got the same results as the previous computer. I know the cable is not bad because it recognizes on the fastboot and I already used these cables on it and it also works perfectly on my old Galaxy Y. Oh and I know that the cable works because the only thing I can access is the fastboot and the two PCs recognize it perfectly the Moto C in fastboot mode.(06-03-2020, 05:25 AM)AndersonSilvaa I tried what you said, but it didn't change the results on the first attempt without pressing any buttons and the second attempt by pressing the minus button.
well, your problem doesn't seem to be from the flashing tool, neither is it from the DA file (cause someone has previously confirmed the DA to work on the same device model). You've tried a different PC and USB cables as you said, which leaves USB port on the phone
you can try changing that then retry flashing the device
(08-03-2020, 05:02 AM)AndersonSilvaa Well I tried it on another computer, as you can see in the images, I also tried all the USB ports, I used 4 different cables (including the original one I found, and they were all tested), the battery is practically 100% too, but I got the same results as the previous computer. I know the cable is not bad because it recognizes on the fastboot and I already used these cables on it and it also works perfectly on my old Galaxy Y. Oh and I know that the cable works because the only thing I can access is the fastboot and the two PCs recognize it perfectly the Moto C in fastboot mode.
...
(09-03-2020, 09:04 AM)X3nonBTW?(08-03-2020, 05:02 AM)AndersonSilvaa Well I tried it on another computer, as you can see in the images, I also tried all the USB ports, I used 4 different cables (including the original one I found, and they were all tested), the battery is practically 100% too, but I got the same results as the previous computer. I know the cable is not bad because it recognizes on the fastboot and I already used these cables on it and it also works perfectly on my old Galaxy Y. Oh and I know that the cable works because the only thing I can access is the fastboot and the two PCs recognize it perfectly the Moto C in fastboot mode.
...
retry a different custom settings in miracle thunder, don't select any da or auth file
tick the checkbox beside models, then select your device manufacturer and model from the drop-down boxes
BTW is the bootloader of the phone unlocked?
(09-03-2020, 09:04 AM)X3nonfollowing what you suggested(08-03-2020, 05:02 AM)AndersonSilvaa Well I tried it on another computer, as you can see in the images, I also tried all the USB ports, I used 4 different cables (including the original one I found, and they were all tested), the battery is practically 100% too, but I got the same results as the previous computer. I know the cable is not bad because it recognizes on the fastboot and I already used these cables on it and it also works perfectly on my old Galaxy Y. Oh and I know that the cable works because the only thing I can access is the fastboot and the two PCs recognize it perfectly the Moto C in fastboot mode.
...
retry a different custom settings in miracle thunder, don't select any da or auth file
tick the checkbox beside models, then select your device manufacturer and model from the drop-down boxes
BTW is the bootloader of the phone unlocked?
(09-03-2020, 05:58 AM)innageeI can't unlock the bootloader and then I can't flash anything. And I also didn't find XT1758 rom for RSD or commands to flash files one by one(08-03-2020, 05:02 AM)AndersonSilvaa(06-03-2020, 02:53 PM)X3nonWell I tried it on another computer, as you can see in the images, I also tried all the USB ports, I used 4 different cables (including the original one I found, and they were all tested), the battery is practically 100% too, but I got the same results as the previous computer. I know the cable is not bad because it recognizes on the fastboot and I already used these cables on it and it also works perfectly on my old Galaxy Y. Oh and I know that the cable works because the only thing I can access is the fastboot and the two PCs recognize it perfectly the Moto C in fastboot mode.(06-03-2020, 05:25 AM)AndersonSilvaa I tried what you said, but it didn't change the results on the first attempt without pressing any buttons and the second attempt by pressing the minus button.
well, your problem doesn't seem to be from the flashing tool, neither is it from the DA file (cause someone has previously confirmed the DA to work on the same device model). You've tried a different PC and USB cables as you said, which leaves USB port on the phone
you can try changing that then retry flashing the device
Have you tried flashing any image via fastboot? If yes, what error did you encounter?
(10-03-2020, 04:14 AM)AndersonSilvaa I can't unlock the bootloader and then I can't flash anything. And I also didn't find XT1758 rom for RSD or commands to flash files one by one
(10-03-2020, 10:56 AM)X3nonSorry for the delay, I was very busy and tested different versions of the RSD and also firmware, but I was not successful, the RSD itself does not even recognize the device. But fastboot works just like you in the previous images.(10-03-2020, 04:14 AM)AndersonSilvaa I can't unlock the bootloader and then I can't flash anything. And I also didn't find XT1758 rom for RSD or commands to flash files one by one
the firmwares @ https://mirrors.lolinet.com/firmware/mot.../official/ should be RSD compatible, you can try it out with RSD
you won't be able to manually flash files one by one in fastboot on a locked bootloader except you're using RSDlite tool
(10-03-2020, 10:56 AM)X3nonI'm not sure, but I think it might help:(10-03-2020, 04:14 AM)AndersonSilvaa I can't unlock the bootloader and then I can't flash anything. And I also didn't find XT1758 rom for RSD or commands to flash files one by one
the firmwares @ https://mirrors.lolinet.com/firmware/mot.../official/ should be RSD compatible, you can try it out with RSD
you won't be able to manually flash files one by one in fastboot on a locked bootloader except you're using RSDlite tool
$ fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2480000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:efuse: 80000
(bootloader) partition-type:efuse: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-size:oemkeystore: 200000
(bootloader) partition-type:oemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) ro.carrier: trueth
(bootloader) radio: 5
(bootloader) kernel.version[0]: Linux version 3.18.35+
(bootloader) kernel.version[1]: (hanhongbo@dell-PowerEdge-R730)
(bootloader) kernel.version[2]: gcc version 4.8 (GCC)
(bootloader) kernel.version[3]: 1 SMP PREEMPT
(bootloader) kernel.version[4]: 2017-11-15:19:14:20
(bootloader) ro.build.fingerprint[1]: motorola/namath_58/namath:7.0/NRD
(bootloader) ro.build.fingerprint[2]: D90M.003/1510743882:user/release-
(bootloader) ro.build.fingerprint[3]: -keys
(bootloader) ro.build.version.mtk[1]: alps-mp-n0.mp1-V1.0.2_wt6737m.65.
(bootloader) ro.build.version.mtk[2]: .n_P89
(bootloader) ro.build.version.full[1]: Blur_Version.25.21.03.namath_58.
(bootloader) ro.build.version.full[2]: trueth.en.US
(bootloader) imei1: 356497085328530
(bootloader) imei2: 356497085328548
(bootloader) boot reason: wdt_by_pass_pwk
(bootloader) hwrev: M11
(bootloader) CID: 0x0032
(bootloader) SKU: XT1758
(bootloader) CPU: "MT6735"
(bootloader) serialno: ZW322HF7ZH
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) securestate: no
(bootloader) hwsecure: yes
(bootloader) kernel: lk
(bootloader) board: WT98736B32_EA1
(bootloader) product: WT98736B32_EA1
(bootloader) Ram size: 1GB
(bootloader) emmc: KMFN60012M_B214
(bootloader) storage-type: emmc
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.006s
(16-03-2020, 05:19 AM)AndersonSilvaa Sorry for the delay, I was very busy and tested different versions of the RSD and also firmware, but I was not successful, the RSD itself does not even recognize the device. But fastboot works just like you in the previous images.
(16-03-2020, 05:32 AM)AndersonSilvaa I'm not sure, but I think it might help:
...
(bootloader) ro.carrier: trueth
...