Motorola Moto E — XT1021 brickado em 5.0.2

  • Respostas:0
Pablo Vieira de Souza
  • Posts no fórum: 3

12/11/2016, 04:43:12 via Web

Povo, estou com um XT1021 velho de guerra que simplesmente parou de funcionar... Acabou a bateria, quando carreguei já entrou em bootloop, seguido de um Android com tampa aberta...

Tentei de todas as formas flashear a firmware, mas ele sempre dá erros, e não consigo resolver...

Se dou um "mfastboot getvar all", ele retorna:

(bootloader) version: 0.5
(bootloader) version-bootloader: 500C
(bootloader) product: condor
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x1
(bootloader) emmc: 4GB Micron REV=06 PRV=12 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8210 CS
(bootloader) serialno: 0428519726
(bootloader) cid: 0x000C
(bootloader) channelid: 0x09
(bootloader) uid: 3579FF0312000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 299892736
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359315051028404
(bootloader) meid:
(bootloader) date: 2014-07-03
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 1:48: 8 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/condor_retbr/condor_umts:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXC22.46-32/30:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.32.condor_retb
(bootloader) ro.build.version.full[1]: r.retbr.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g5bed184 (hudsoncm@
(bootloader) kernel.version[1]: ilclbld29) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jan 23 21:01:50 CST 2015
(bootloader) sdi.git: git=MBM-NG-V50.0C-0-g3ccd862
(bootloader) sbl1.git: git=MBM-NG-V50.0C-0-g646e13f
(bootloader) rpm.git: git=MBM-NG-V50.0C-0-gcebb121
(bootloader) tz.git: git=MBM-NG-V50.0C-0-g65c6b0f
(bootloader) aboot.git: git=MBM-NG-V50.0C-0-g2259fb8
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: tefbr
all: listed above
finished. total time: 0.061s

Porém qualquer comando pra flashear a firmware stock de volta, resulta em:

mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.055s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.

(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 5.575s

Ou isso:

mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (7672 KB)...
OKAY [ 0.270s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.250s

Alguém tem alguma idéia? Ou morreu mesmo?

Responder