LOCKED BOOTLOADER AND NO OS AND NO TWRP! IN MOTO G9 PLAY - Moto G9 Play Questions & Answers

I need help pls with my Moto g9 play deviceeeee
its LOCKED BOOTLOADER AND NO OS IS THERE AND NO TWRP
WHAT I DO PLS

YxD8m said:
I need help pls with my Moto g9 play deviceeeee
its LOCKED BOOTLOADER AND NO OS IS THERE AND NO TWRP
WHAT I DO PLS
Click to expand...
Click to collapse
What does getvar all say?
remove imei before posting
Code:
fastboot getvar all

sd_shadow said:
¿Qué dice getvar?
eliminar imei antes de publicar
Code:
fastboot getvar all
Click to expand...
Click to collapse
fastboot getvar all
(gestor de arranque) kernel: uefi
(gestor de arranque) version-bootloader: MBM-3.0-guamp_retail-35fd040673-210528
(gestor de arranque) producto: guamp
(gestor de arranque) placa: guamp
(gestor de arranque) seguro: sí
(gestor de arranque) hwrev: PVT
(gestor de arranque) radio: LATAM
(gestor de arranque) tipo de almacenamiento: eMMC
(gestor de arranque) emmc: 64GB MICRON G1J9R8 RV=08 PV=10 FV=0000000000000204
(gestor de arranque) ufs: N / A
(gestor de arranque) ram: 4GB MICRON LP4x DIE=32Gb M5-M8=FF 06 00 18
(gestor de arranque) cpu: SM_KAMORTA_H 1.0
(gestor de arranque) serialno: ZY32C2PD8H
(gestor de arranque) cid: 0x0032
(gestor de arranque) channelid: 0x1a
(gestor de arranque) uid: 2240CC37
(gestor de arranque) securestate: flashing_locked
(gestor de arranque) modos de fábrica: deshabilitado
(gestor de arranque) verity-state: aplicación (0)
(bootloader) iswarrantyvoid: sí
(gestor de arranque) tamaño máximo de descarga: 804466688
(gestor de arranque) motivo: tecla para bajar el volumen presionada
(gestor de arranque) imei:
(gestor de arranque) imei2:
(gestor de arranque) meid:
(gestor de arranque) fecha: 05-04-2021
(gestor de arranque) sku: XT2083-1
(gestor de arranque) carrier_sku: XT2083-1
(gestor de arranque) battid: SB18C77591
(gestor de arranque) voltaje de la batería: 3682
(gestor de arranque) iccid:
(gestor de arranque) cust_md5:
(gestor de arranque) tamaño máximo-escaso: 268435456
(gestor de arranque) poweroffalarm: 0
(gestor de arranque) ro.carrier: retar
(gestor de arranque) ro.build.fingerprint[0]: motorola/guamp_retail/guamp:10/QPX
(gestor de arranque) ro.build.fingerprint[1]: S30.30-Q3-38-69-1/1d4fe6:user/rele
(gestor de arranque) ro.build.fingerprint[2]: ase-keys
(gestor de arranque) ro.build.version.qcom: LA. UM.8.15.r1-05300-KAMORTA.0
(gestor de arranque) versión-banda base: HA10_11.167.01.76R GUAMP_LATAM_CUST
(bootloader) kernel.version[0]: Linux versión 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang versión 8.0.16 para Y
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Sun May 2 05:51
(gestor de arranque) kernel.version[3]: :13 CDT 2021
(gestor de arranque) git:xbl: MBM-3.0-guamp_retail-0ed29cb2f-210528
(gestor de arranque) git:xbl_config: MBM-3.0-guamp_retail-0ed29cb2f-210528
(gestor de arranque) git:abl: MBM-3.0-guamp_retail-35fd040673-210528
(gestor de arranque) git:rpm: MBM-3.0-guamp_retail-834e250-210528
(gestor de arranque) git:tz: MBM-3.0-guamp_retail-8e81fa53-210528
(gestor de arranque) git:hyp: MBM-3.0-guamp_retail-8e81fa53-210528
(gestor de arranque) git:devcfg: MBM-3.0-guamp_retail-8e81fa53-210528
(gestor de arranque) git:keymaster: MBM-3.0-guamp_retail-4b08852-210528
(gestor de arranque) git:storsec: MBM-3.0-guamp_retail-4b08852-210528
(gestor de arranque) git:uefisecapp: MBM-3.0-guamp_retail-4b08852-210528
(gestor de arranque) gitrov: MBM-3.0-guamp_retail-8e81fa53-210528
(gestor de arranque) git:qupfw: MBM-3.0-guamp_retail-2e25c72-210528
(gestor de arranque) frp-state: protegido (144)
(gestor de arranque) ranura de corriente: a
(gestor de arranque) running-bl-slot: _a/_a
(gestor de arranque) running-boot-lun: 0
(gestor de arranque) número de ranuras: 2
(gestor de arranque) ranura correcta:_a: no
(gestor de arranque) ranura correcta:_b: no
(gestor de arranque) slot-unbootable:_a: no
(gestor de arranque) slot-unbootable:_b: no
(gestor de arranque) slot-retry-count:_a: 7
(gestor de arranque) slot-retry-count:_b: 0
(gestor de arranque) tamaño de bloque lógico: 0x200
(gestor de arranque) erase-block-size: 0x200
(gestor de arranque) is-userspace: no
(gestor de arranque) pcb-part-no: SB28C82497
(gestor de arranque) pantalla principal: tm_icnl9911s_video_display
(gestor de arranque) pantalla secundaria:
todos: enumerados anteriormente
terminado. tiempo total: 1.109s

ryu89 said:
Code:
producto: guamp
radio: LATAM
securestate: flashing_locked
iswarrantyvoid: sí
sku: XT2083-1
ro.carrier: retar
ro.build.fingerprint[0]: motorola/guamp_retail/guamp:10/QPXS30.30-Q3-38-69-1/1d4fe6:user/release-keys
is-userspace: no
Click to expand...
Click to collapse
So it says the bootloader is locked, did you lock it or did it change after trying to flash?

sd_shadow said:
So it says the bootloader is locked, did you lock it or did it change after trying to flash?
Click to expand...
Click to collapse
boot crash on wrong version of android 10 instead of android 11

How can I find the test points on this Moto G9 Play device?

Have you tried Lenovo Moto Smart Assistant? And why do you need a test point for flashing, since your phone has the bootloader still locked?
From what I remember, test points on Moto devices were useful only for ramdump and some other things not related to a corrupted system.

Related

[Q] bloquer sur bootloader

Bonjour
je suis bloquer sur le bootloader aucune commande ne reagit voici une capture d'ecran
HTC ONE
brams-1 said:
Bonjour
je suis bloquer sur le bootloader aucune commande ne reagit voici une capture d'ecran
HTC ONE
Click to expand...
Click to collapse
Est Que vous avez deja essayer du rooter? Ou utilisez un RUU
a box of kittens said:
Est Que vous avez deja essayer du rooter? Ou utilisez un RUU
Click to expand...
Click to collapse
oui j'ai essayé les deux et ça ne fonctionne pas
Est vous avez adb/fastboot sur l'ordinateur? Si non je pourrais vous donnez un lien pour les deux..tu en as besoin!
oui je les ai installer je ne sais pas quoi faire
Hmm ... Mettez "fastboot getvar cid" et Mettez ici les resultats..est que vous voulez que le portable marche encore? Ou le rooter Si just marcher... Faisons le RUU
a box of kittens said:
Est vous avez adb/fastboot sur l'ordinateur? Si non je pourrais vous donnez un lien pour les deux..tu en as besoin!
Click to expand...
Click to collapse
oui je les ai installer et je ne sais Pas Quoi faire
brams-1 said:
oui je les ai installer et je ne sais Pas Quoi faire
Click to expand...
Click to collapse
voici le resultat
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT33WW901301
(bootloader) imei: 3
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3805mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.054s
Si vous plait... Supprimer le numero d'imei... Il faut le garder juste a toi
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Cest pas le developer edition nestce pas?
a box of kittens said:
Hmm ... Mettez "fastboot getvar cid" et Mettez ici les resultats..est que vous voulez que le portable marche encore? Ou le rooter Si just marcher... Faisons le RUU
Click to expand...
Click to collapse
je veux que le portable marche encore
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT33WW901301
(bootloader) imei: 3
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3805mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.054s
Suprrimez le numero d'imei!! Il ne faut pas laisser les gens le voir
a box of kittens said:
Si vous plait... Supprimer le numero d'imei... Il faut le garder juste a toi
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Cest pas le developer edition nestce pas?
Click to expand...
Click to collapse
Non Cest pas le developer edition
Stop posting in french here, please.
Posting in foreign language is only allowed if translation is provided in same post. So if you continue to post in french without english translation, this thread will be closed.
jotha said:
Stop posting in french here, please.
Posting in foreign language is only allowed if translation is provided in same post. So if you continue to post in french without english translation, this thread will be closed.
Click to expand...
Click to collapse
desoler I'm not very good at English
brams-1 said:
desoler I'm not very good at English
Click to expand...
Click to collapse
...and the other 5 million users aren't very good in french.
So please use google translate or whatever and provide (even a bad) translation with every post.
jotha said:
...and the other 5 million users aren't very good in french.
So please use google translate or whatever and provide (even a bad) translation with every post.
Click to expand...
Click to collapse
It's not wrong
Okay so lets do this in English or you can email me
a box of kittens said:
Okay so lets do this in English or you can email me
Click to expand...
Click to collapse
Thank you for your help i give u m'y mail un MP
brams-1 said:
Thank you for your help i give u m'y mail un MP
Click to expand...
Click to collapse
Problem resolve thank you
brams-1 said:
Problem resolve thank you
Click to expand...
Click to collapse
I have the same probleme.
Can you help me?

Moto G XT1069 HARD BRICK

Hello, my phone don't flash a new recovery, rom stock, or antoher flashable in fastboot mode (My Bootloader is unlock and i has root).
i try erase userdata and i get the "Failed", i try erase Cache, Dalvik Cache, system and i get the "sucess message" but nothing change :crying:
I don't know what's happened, Please Help Me.
My cel is dead ? i can save it ?
Sorry for my bad english, i'm brazilian.
GnR_xXTurner said:
Hello, my phone don't flash a new recovery, rom stock, or antoher flashable in fastboot mode (My Bootloader is unlock and i has root).
i try erase userdata and i get the "Failed", i try erase Cache, Dalvik Cache, system and i get the "sucess message" but nothing change :crying:
I don't know what's happened, Please Help Me.
My cel is dead ? i can save it ?
Sorry for my bad english, i'm brazilian.
Click to expand...
Click to collapse
Eu Também sou do brasil e tenho um XT1069, Talvez eu possa te ajudar :highfive:
---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------
GnR_xXTurner said:
Hello, my phone don't flash a new recovery, rom stock, or antoher flashable in fastboot mode (My Bootloader is unlock and i has root).
i try erase userdata and i get the "Failed", i try erase Cache, Dalvik Cache, system and i get the "sucess message" but nothing change :crying:
I don't know what's happened, Please Help Me.
My cel is dead ? i can save it ?
Sorry for my bad english, i'm brazilian.
Click to expand...
Click to collapse
Você consegue entrar em modo recovery ? pelo TWRP ou algo assim ?
LudwigFerdinand18 said:
Eu Também sou do brasil e tenho um XT1069, Talvez eu possa te ajudar :highfive:
---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------
Você consegue entrar em modo recovery ? pelo TWRP ou algo assim ?
Click to expand...
Click to collapse
Entao eu consigo entrar no TWRP mas não consigo fazer muita coisa lá
GnR_xXTurner said:
Entao eu consigo entrar no TWRP mas não consigo fazer muita coisa lá
Click to expand...
Click to collapse
Explica pra mim que tipo de erro acontece, é só ao zerar o Userdata ? os Outros Wipes faz normal ?
se você der o flash da rom STOCK ela não funciona ?
Eu posso zerar meu celular e fazer o backup da partição e passar pra você e você subistitui no seu, esse método é quase 100% de certeza q vai voltar a funcionar, mais preciso saber o que se passa pois talvez não seja algo tão sério para fazer esse transplante
LudwigFerdinand18 said:
Explica pra mim que tipo de erro acontece, é só ao zerar o Userdata ? os Outros Wipes faz normal ?
se você der o flash da rom STOCK ela não funciona ?
Eu posso zerar meu celular e fazer o backup da partição e passar pra você e você subistitui no seu, esse método é quase 100% de certeza q vai voltar a funcionar, mais preciso saber o que se passa pois talvez não seja algo tão sério para fazer esse transplante
Click to expand...
Click to collapse
Então, no fastboot quando eu do o comando GETVAR ALL, ele me diz que esta no Android 5.0.2 eu tento instalar uma Rom abaixo ou acima e eu tenho sucesso, mas nada muda, é como se a memoria estivesse recebendo o comando mas não executando o mesmo mas ela retorna a mensagem de sucesso, no TWRP quando eu coloco "Fomart DATA" ele fica formatando e nunca sai disso, eu tento dar Wipe "Internal Storage" e da Failed, os outros Wipes eu consigo dar de boa, mas acho que nada muda também, eu já tentei instalar um rom pelo TWRP, tudo ocorre ok, mas nada muda tbm, se você puder me passar o backup eu agradeço muito mesmo :highfive:, por que acho que é a única salvação.
GnR_xXTurner said:
Então, no fastboot quando eu do o comando GETVAR ALL, ele me diz que esta no Android 5.0.2 eu tento instalar uma Rom abaixo ou acima e eu tenho sucesso, mas nada muda, é como se a memoria estivesse recebendo o comando mas não executando o mesmo mas ela retorna a mensagem de sucesso, no TWRP quando eu coloco "Fomart DATA" ele fica formatando e nunca sai disso, eu tento dar Wipe "Internal Storage" e da Failed, os outros Wipes eu consigo dar de boa, mas acho que nada muda também, eu já tentei instalar um rom pelo TWRP, tudo ocorre ok, mas nada muda tbm, se você puder me passar o backup eu agradeço muito mesmo :highfive:, por que acho que é a única salvação.
Click to expand...
Click to collapse
Eu comecei a pensar agora que seu cartão onde fica armazenado foi pro pau, igual quando os cartões SD ficam só no modo leitura, faça um teste, eu vou fazer o UPLOAD da minha partição recovery e você tenta flashear e vê se muda algo de versão
Segue Esses Passos :
Pluga o celular no PC em modo recovery e extrai poe o Arquivo recovery.img que eu tirei do meu celular no seu cartão SD
Você vai precisar ter o Adb e fastboot, pelo computador no prompt você vai entrar no adb shell
Segue os comandos :
dd if=/sdcard1/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery
e Veja se a versão do TWRP Mudou algo :good:
se mudar é pq ainda tem salvação ... pq se não vai ser foda hem mano
LudwigFerdinand18 said:
Eu comecei a pensar agora que seu cartão onde fica armazenado foi pro pau, igual quando os cartões SD ficam só no modo leitura, faça um teste, eu vou fazer o UPLOAD da minha partição recovery e você tenta flashear e vê se muda algo de versão
Segue Esses Passos :
Pluga o celular no PC em modo recovery e extrai poe o Arquivo recovery.img que eu tirei do meu celular no seu cartão SD
Você vai precisar ter o Adb e fastboot, pelo computador no prompt você vai entrar no adb shell
Segue os comandos :
dd if=/sdcard1/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery
e Veja se a versão do TWRP Mudou algo :good:
se mudar é pq ainda tem salvação ... pq se não vai ser foda hem mano
Click to expand...
Click to collapse
Ok vou tentar fazer isso, Obrigado pela ajuda até agora, obrigado mesmo. já respondo o resultado aqui. :highfive:
GnR_xXTurner said:
Ok vou tentar fazer isso, Obrigado pela ajuda até agora, obrigado mesmo. já respondo o resultado aqui. :highfive:
Click to expand...
Click to collapse
O resultado no Cmd é esse ~ # ←[6n dd if=/sdcard1/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/r
ecovery
dd if=/sdcard1/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recov
ery
20560+0 records in
20560+0 records out
10526720 bytes (10.0MB) copied, 1.469727 seconds, 6.8MB/s
Porem n mudou a versão :crying:
GnR_xXTurner said:
O resultado no Cmd é esse ~ # ←[6n dd if=/sdcard1/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/r
ecovery
dd if=/sdcard1/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recov
ery
20560+0 records in
20560+0 records out
10526720 bytes (10.0MB) copied, 1.469727 seconds, 6.8MB/s
Porem n mudou a versão :crying:
Click to expand...
Click to collapse
roda esse comando pra mim
adb shell
getprop ro.boot.write_protect
o valor retornado é 0 ou 1 ?
LudwigFerdinand18 said:
roda esse comando pra mim
adb shell
getprop ro.boot.write_protect
o valor retornado é 0 ou 1 ?
Click to expand...
Click to collapse
~ # ←[6ngetprop ro.boot.write_protect
getprop ro.boot.write_protect
0
Pelo jeito o sistema não está protegido, acho que deve ser a memoria em, eu baixei um backup do system , data e boot do XT1069 e tentei instalar pelo TWRP, eu consegui instalar o System e boot, data deu failed, mas ainda não iniciou, sera que é algum problema de hardware ? será que tem algum comando que eu possa testar ?
MOD EDIT - Friendly reminder to post in English
Apparently the system is not protected, I think that should be the memory in, I downloaded a backup of the system, date and boot XT1069 and tried to install the TWRP, I managed to install the system and boot date has failed, but not yet started , will be that it is a hardware problem? does it have any command that I can test?
GnR_xXTurner said:
~ # ←[6ngetprop ro.boot.write_protect
getprop ro.boot.write_protect
0
Pelo jeito o sistema não está protegido, acho que deve ser a memoria em, eu baixei um backup do system , data e boot do XT1069 e tentei instalar pelo TWRP, eu consegui instalar o System e boot, data deu failed, mas ainda não iniciou, sera que é algum problema de hardware ? será que tem algum comando que eu possa testar ?
Click to expand...
Click to collapse
Você poderia tentar usar o comando mkfs para checar mais o problema é que nem montar o volume você consegue eu acho ...
vou tentar montar o comando pra você tentar rodar ai
GnR_xXTurner said:
~ # ←[6ngetprop ro.boot.write_protect
getprop ro.boot.write_protect
0
Pelo jeito o sistema não está protegido, acho que deve ser a memoria em, eu baixei um backup do system , data e boot do XT1069 e tentei instalar pelo TWRP, eu consegui instalar o System e boot, data deu failed, mas ainda não iniciou, sera que é algum problema de hardware ? será que tem algum comando que eu possa testar ?
Click to expand...
Click to collapse
[af.resampler.quality]: [255]
[com.qc.hardware]: [true]
[dalvik.vm.dexopt-flags]: [m=y]
[dalvik.vm.heapgrowthlimit]: [64m]
[dalvik.vm.heapmaxfree]: [8m]
[dalvik.vm.heapminfree]: [2m]
[dalvik.vm.heapsize]: [256m]
[dalvik.vm.heapstartsize]: [8m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.composition.type]: [dyn]
[debug.egl.hw]: [1]
[debug.enabletr]: [0]
[debug.mdpcomp.logs]: [0]
[debug.sf.fb_always_on]: [1]
[debug.sf.hw]: [1]
[init.svc.adbd]: [running]
[init.svc.recovery]: [running]
[init.svc.ueventd]: [running]
[keyguard.no_require_sim]: [true]
[lpa.decode]: [false]
[media.stagefright.enable-aac]: [true]
[media.stagefright.enable-fma2dp]: [true]
[media.stagefright.enable-http]: [true]
[media.stagefright.enable-player]: [true]
[media.stagefright.enable-qcp]: [true]
[media.stagefright.enable-scan]: [true]
[mmp.enable.3g2]: [true]
[mtp.crash_check]: [0]
[net.bt.name]: [Android]
[net.change]: [net.bt.name]
[persist.audio.fluence.mode]: [endfire]
[persist.audio.fluence.voicecall]: [true]
[persist.audio.handset.mic]: [digital]
[persist.audio.lowlatency.rec]: [false]
[persist.audio.vr.enable]: [false]
[persist.fuse_sdcard]: [true]
[persist.gps.qc_nlp_in_use]: [0]
[persist.hwc.mdpcomp.enable]: [true]
[persist.radio.apm_sim_not_pwdn]: [1]
[persist.radio.call_type]: [1]
[persist.radio.dfr_mode_set]: [1]
[persist.radio.no_wait_for_card]: [1]
[persist.rild.nitz_long_ons_0]: []
[persist.rild.nitz_long_ons_1]: []
[persist.rild.nitz_long_ons_2]: []
[persist.rild.nitz_long_ons_3]: []
[persist.rild.nitz_plmn]: []
[persist.rild.nitz_short_ons_0]: []
[persist.rild.nitz_short_ons_1]: []
[persist.rild.nitz_short_ons_2]: []
[persist.rild.nitz_short_ons_3]: []
[persist.sys.qc.sub.rdump.max]: [20]
[persist.sys.qc.sub.rdump.on]: [1]
[persist.sys.qc.sub.rstrtlvl]: [3]
[persist.sys.root_access]: [1]
[persist.sys.ui.hw]: [true]
[persist.sys.usb.config]: [adb]
[persist.timed.enable]: [true]
[qcom.bt.le_dev_pwr_class]: [1]
[qcom.hw.aac.encoder]: [true]
[ril.subscription.types]: [NV,RUIM]
[rild.libargs]: [-d /dev/smd0]
[rild.libpath]: [/system/vendor/lib/libril-qc-qmi-1.so]
[ro.allow.mock.location]: [1]
[ro.audio.fm_max_volume]: [4096]
[ro.baseband]: [msm]
[ro.bluetooth.hfp.ver]: [1.6]
[ro.bluetooth.remote.autoconnect]: [true]
[ro.bluetooth.request.master]: [true]
[ro.board.platform]: [msm8226]
[ro.boot.baseband]: [msm]
[ro.boot.bootloader]: [0x4882]
[ro.boot.carrier]: [retbr]
[ro.boot.cid]: [0xC]
[ro.boot.device]: [titan]
[ro.boot.emmc]: [true]
[ro.boot.fsg-id]: []
[ro.boot.hardware]: [qcom]
[ro.boot.hwrev]: [0x8400]
[ro.boot.mode]: [normal]
[ro.boot.powerup_reason]: [0x00100000]
[ro.boot.radio]: [0x7]
[ro.boot.secure_hardware]: [1]
[ro.boot.serialno]: [0430070903]
[ro.boot.write_protect]: [0]
[ro.bootloader]: [0x4882]
[ro.bootmode]: [normal]
[ro.build.characteristics]: [default]
[ro.build.date.utc]: [1406670206]
[ro.build.date]: [Tue Jul 29 16:43:26 CDT 2014]
[ro.build.description]: [titan_retbr_dstv-user 4.4.4 KXB21.85-18 24 release-keys
]
[ro.build.display.id]: [KXB21.85-18]
[ro.build.fingerprint]: [motorola/titan_retbr_dstv/titan_udstv:4.4.4/KXB21.85-18
/24:user/release-keys]
[ro.build.host]: [ilclbld34]
[ro.build.id]: [KXB21.85-18]
[ro.build.product]: [titan_udstv]
[ro.build.selinux]: [1]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [hudsoncm]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [24]
[ro.build.version.release]: [4.4.4]
[ro.build.version.sdk]: [19]
[ro.carrier]: [unknown]
[ro.cm.version]: [UNOFFICIAL-Titan]
[ro.com.android.dataroaming]: [false]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.com.android.wifi-watchlist]: [GoogleGuest]
[ro.com.google.clientidbase]: [android-google]
[ro.config.alarm_alert]: [Oxygen.ogg]
[ro.config.notification_sound]: [Moto.ogg]
[ro.config.ringtone]: [Moto.ogg]
[ro.config.vc_call_vol_steps]: [7]
[ro.crypto.fuse_sdcard]: [true]
[ro.debuggable]: [1]
[ro.emmc]: [0]
[ro.factorytest]: [0]
[ro.hardware]: [qcom]
[ro.hdmi.enable]: [true]
[ro.hw.device]: [titan]
[ro.hw.radio]: [0x1]
[ro.kernel.android.checkjni]: [1]
[ro.modem.no_wdog_chk]: [1]
[ro.modversion]: [UNOFFICIAL-Titan]
[ro.mot.build.customerid]: [RTGB]
[ro.nfc.port]: [I2C]
[ro.opengles.version]: [196608]
[ro.product.board]: [MSM8226]
[ro.product.brand]: [motorola]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [titan_udstv]
[ro.product.manufacturer]: [motorola]
[ro.product.model]: [XT1069]
[ro.product.name]: [titan_retbr_dstv]
[ro.qc.sdk.audio.fluencetype]: [fluence]
[ro.qc.sdk.audio.ssr]: [false]
[ro.qualcomm.bluetooth.sap]: [true]
[ro.qualcomm.bt.hci_transport]: [smd]
[ro.qualcomm.cabl]: [0]
[ro.revision]: [33792]
[ro.ril.transmitpower]: [true]
[ro.rommanager.developerid]: [cyanogenmod]
[ro.secure]: [0]
[ro.serialno]: [0430070903]
[ro.setupwizard.enterprise_mode]: [1]
[ro.sf.lcd_density]: [320]
[ro.telephony.default_network]: [3]
[ro.twrp.boot]: [1]
[ro.twrp.version]: [2.8.0.1]
[ro.url.legal.android_privacy]: [http://www.google.com/intl/%s/mobile/android/ba
sic/privacy.html]
[ro.url.legal]: [http://www.google.com/intl/%s/mobile/android/basic/phone-legal.
html]
[ro.usb.bpt]: [0x2e28]
[ro.usb.bpt_adb]: [0x2e29]
[ro.usb.bpteth]: [0x2e2a]
[ro.usb.bpteth_adb]: [0x2e2b]
[ro.usb.mtp]: [0x2e82]
[ro.usb.mtp_adb]: [0x2e76]
[ro.usb.ptp]: [0x2e83]
[ro.usb.ptp_adb]: [0x2e84]
[ro.use_data_netmgrd]: [true]
[ro.vendor.extension_library]: [/system/lib/libqc-opt.so]
[ro.wifi.channels]: []
[service.adb.root]: [1]
[sys.usb.config]: [adb]
[telephony.lteOnCdmaDevice]: [0]
[telephony.lteOnGsmDevice]: [0]
[tunnel.audiovideo.decode]: [true]
[tunnel.decode]: [true]
[twrp.crash_counter]: [0]
[use.voice.path.for.pcm.voip]: [true]
Relatorio completo caso queira ver
GnR_xXTurner said:
[af.resampler.quality]: [255]
[com.qc.hardware]: [true]
[dalvik.vm.dexopt-flags]: [m=y]
[dalvik.vm.heapgrowthlimit]: [64m]
[dalvik.vm.heapmaxfree]: [8m]
[dalvik.vm.heapminfree]: [2m]
[dalvik.vm.heapsize]: [256m]
[dalvik.vm.heapstartsize]: [8m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.composition.type]: [dyn]
[debug.egl.hw]: [1]
[debug.enabletr]: [0]
[debug.mdpcomp.logs]: [0]
[debug.sf.fb_always_on]: [1]
[debug.sf.hw]: [1]
[init.svc.adbd]: [running]
[init.svc.recovery]: [running]
[init.svc.ueventd]: [running]
[keyguard.no_require_sim]: [true]
[lpa.decode]: [false]
[media.stagefright.enable-aac]: [true]
[media.stagefright.enable-fma2dp]: [true]
[media.stagefright.enable-http]: [true]
[media.stagefright.enable-player]: [true]
[media.stagefright.enable-qcp]: [true]
[media.stagefright.enable-scan]: [true]
[mmp.enable.3g2]: [true]
[mtp.crash_check]: [0]
[net.bt.name]: [Android]
[net.change]: [net.bt.name]
[persist.audio.fluence.mode]: [endfire]
[persist.audio.fluence.voicecall]: [true]
[persist.audio.handset.mic]: [digital]
[persist.audio.lowlatency.rec]: [false]
[persist.audio.vr.enable]: [false]
[persist.fuse_sdcard]: [true]
[persist.gps.qc_nlp_in_use]: [0]
[persist.hwc.mdpcomp.enable]: [true]
[persist.radio.apm_sim_not_pwdn]: [1]
[persist.radio.call_type]: [1]
[persist.radio.dfr_mode_set]: [1]
[persist.radio.no_wait_for_card]: [1]
[persist.rild.nitz_long_ons_0]: []
[persist.rild.nitz_long_ons_1]: []
[persist.rild.nitz_long_ons_2]: []
[persist.rild.nitz_long_ons_3]: []
[persist.rild.nitz_plmn]: []
[persist.rild.nitz_short_ons_0]: []
[persist.rild.nitz_short_ons_1]: []
[persist.rild.nitz_short_ons_2]: []
[persist.rild.nitz_short_ons_3]: []
[persist.sys.qc.sub.rdump.max]: [20]
[persist.sys.qc.sub.rdump.on]: [1]
[persist.sys.qc.sub.rstrtlvl]: [3]
[persist.sys.root_access]: [1]
[persist.sys.ui.hw]: [true]
[persist.sys.usb.config]: [adb]
[persist.timed.enable]: [true]
[qcom.bt.le_dev_pwr_class]: [1]
[qcom.hw.aac.encoder]: [true]
[ril.subscription.types]: [NV,RUIM]
[rild.libargs]: [-d /dev/smd0]
[rild.libpath]: [/system/vendor/lib/libril-qc-qmi-1.so]
[ro.allow.mock.location]: [1]
[ro.audio.fm_max_volume]: [4096]
[ro.baseband]: [msm]
[ro.bluetooth.hfp.ver]: [1.6]
[ro.bluetooth.remote.autoconnect]: [true]
[ro.bluetooth.request.master]: [true]
[ro.board.platform]: [msm8226]
[ro.boot.baseband]: [msm]
[ro.boot.bootloader]: [0x4882]
[ro.boot.carrier]: [retbr]
[ro.boot.cid]: [0xC]
[ro.boot.device]: [titan]
[ro.boot.emmc]: [true]
[ro.boot.fsg-id]: []
[ro.boot.hardware]: [qcom]
[ro.boot.hwrev]: [0x8400]
[ro.boot.mode]: [normal]
[ro.boot.powerup_reason]: [0x00100000]
[ro.boot.radio]: [0x7]
[ro.boot.secure_hardware]: [1]
[ro.boot.serialno]: [0430070903]
[ro.boot.write_protect]: [0]
[ro.bootloader]: [0x4882]
[ro.bootmode]: [normal]
[ro.build.characteristics]: [default]
[ro.build.date.utc]: [1406670206]
[ro.build.date]: [Tue Jul 29 16:43:26 CDT 2014]
[ro.build.description]: [titan_retbr_dstv-user 4.4.4 KXB21.85-18 24 release-keys
]
[ro.build.display.id]: [KXB21.85-18]
[ro.build.fingerprint]: [motorola/titan_retbr_dstv/titan_udstv:4.4.4/KXB21.85-18
/24:user/release-keys]
[ro.build.host]: [ilclbld34]
[ro.build.id]: [KXB21.85-18]
[ro.build.product]: [titan_udstv]
[ro.build.selinux]: [1]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [hudsoncm]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [24]
[ro.build.version.release]: [4.4.4]
[ro.build.version.sdk]: [19]
[ro.carrier]: [unknown]
[ro.cm.version]: [UNOFFICIAL-Titan]
[ro.com.android.dataroaming]: [false]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.com.android.wifi-watchlist]: [GoogleGuest]
[ro.com.google.clientidbase]: [android-google]
[ro.config.alarm_alert]: [Oxygen.ogg]
[ro.config.notification_sound]: [Moto.ogg]
[ro.config.ringtone]: [Moto.ogg]
[ro.config.vc_call_vol_steps]: [7]
[ro.crypto.fuse_sdcard]: [true]
[ro.debuggable]: [1]
[ro.emmc]: [0]
[ro.factorytest]: [0]
[ro.hardware]: [qcom]
[ro.hdmi.enable]: [true]
[ro.hw.device]: [titan]
[ro.hw.radio]: [0x1]
[ro.kernel.android.checkjni]: [1]
[ro.modem.no_wdog_chk]: [1]
[ro.modversion]: [UNOFFICIAL-Titan]
[ro.mot.build.customerid]: [RTGB]
[ro.nfc.port]: [I2C]
[ro.opengles.version]: [196608]
[ro.product.board]: [MSM8226]
[ro.product.brand]: [motorola]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [titan_udstv]
[ro.product.manufacturer]: [motorola]
[ro.product.model]: [XT1069]
[ro.product.name]: [titan_retbr_dstv]
[ro.qc.sdk.audio.fluencetype]: [fluence]
[ro.qc.sdk.audio.ssr]: [false]
[ro.qualcomm.bluetooth.sap]: [true]
[ro.qualcomm.bt.hci_transport]: [smd]
[ro.qualcomm.cabl]: [0]
[ro.revision]: [33792]
[ro.ril.transmitpower]: [true]
[ro.rommanager.developerid]: [cyanogenmod]
[ro.secure]: [0]
[ro.serialno]: [0430070903]
[ro.setupwizard.enterprise_mode]: [1]
[ro.sf.lcd_density]: [320]
[ro.telephony.default_network]: [3]
[ro.twrp.boot]: [1]
[ro.twrp.version]: [2.8.0.1]
[ro.url.legal.android_privacy]: [http://www.google.com/intl/%s/mobile/android/ba
sic/privacy.html]
[ro.url.legal]: [http://www.google.com/intl/%s/mobile/android/basic/phone-legal.
html]
[ro.usb.bpt]: [0x2e28]
[ro.usb.bpt_adb]: [0x2e29]
[ro.usb.bpteth]: [0x2e2a]
[ro.usb.bpteth_adb]: [0x2e2b]
[ro.usb.mtp]: [0x2e82]
[ro.usb.mtp_adb]: [0x2e76]
[ro.usb.ptp]: [0x2e83]
[ro.usb.ptp_adb]: [0x2e84]
[ro.use_data_netmgrd]: [true]
[ro.vendor.extension_library]: [/system/lib/libqc-opt.so]
[ro.wifi.channels]: []
[service.adb.root]: [1]
[sys.usb.config]: [adb]
[telephony.lteOnCdmaDevice]: [0]
[telephony.lteOnGsmDevice]: [0]
[tunnel.audiovideo.decode]: [true]
[tunnel.decode]: [true]
[twrp.crash_counter]: [0]
[use.voice.path.for.pcm.voip]: [true]
Relatorio completo caso queira ver
Click to expand...
Click to collapse
Entra no TWRP e vai na Seção MOUNT e tira a seleção de TUDO
Agora Vai no PC e em modo Adb Shell digita esse comando
mkfs.f2fs /dev/block/mmcblk0p38 e fala pra mim o que deu :highfive:
dai você tenta de novo reegravar os arquivos, Tem que aparecer FORMAT SUCESSFUL
LudwigFerdinand18 said:
Entra no TWRP e vai na Seção MOUNT e tira a seleção de TUDO
Agora Vai no PC e em modo Adb Shell digita esse comando
mkfs.f2fs /dev/block/mmcblk0p38 e fala pra mim o que deu :highfive:
dai você tenta de novo reegravar os arquivos, Tem que aparecer FORMAT SUCESSFUL
Click to expand...
Click to collapse
~ # ←[6nmkfs.f2fs /dev/block/mmcblk0p38
mkfs.f2fs /dev/block/mmcblk0p38
F2FS-tools: mkfs.f2fs Ver: 1.1.0 (2012-11-29)
Info: sector size = 512
Info: total sectors = 27055872 (in 512bytes)
Info: zone aligned segment0 blkaddr: 256
Error: Could not conduct fsync!!!
Info: format successful
~ # ←[6n
Apareceu Format Successful mas tem um erro ali em cima
GnR_xXTurner said:
~ # ←[6nmkfs.f2fs /dev/block/mmcblk0p38
mkfs.f2fs /dev/block/mmcblk0p38
F2FS-tools: mkfs.f2fs Ver: 1.1.0 (2012-11-29)
Info: sector size = 512
Info: total sectors = 27055872 (in 512bytes)
Info: zone aligned segment0 blkaddr: 256
Error: Could not conduct fsync!!!
Info: format successful
~ # ←[6n
Apareceu Format Successful mas tem um erro ali em cima
Click to expand...
Click to collapse
roda com esse parametro : mkfs.f2fs -t 1 /dev/block/mmcblk0p38
e dai tenta fazer aquilo de restaurar as partições pelo backup q vc tem, o meu eu fiz e não deu esse erro ...
---------- Post added at 07:57 PM ---------- Previous post was at 07:44 PM ----------
LudwigFerdinand18 said:
roda com esse parametro : mkfs.f2fs -t 1 /dev/block/mmcblk0p38
e dai tenta fazer aquilo de restaurar as partições pelo backup q vc tem, o meu eu fiz e não deu esse erro ...
Click to expand...
Click to collapse
se não funcionar de jeito nenhum você tenta o seguinte, eu salvei do meu celular o fsync e coloquei no zip, vc baixa e descompacta ...
você vai rodar esse comando :
dd if=/sdcard1/fsync.img of=/sbin/fsync
Sem reiniciar o celular nem nada você vai tentar rodar o comando :
mkfs.f2fs -t 1 /dev/block/mmcblk0p38
mkfs.f2fs /dev/block/mmcblk0p38
roda os dois pra ter certeza e vê se dá erro de novo ...
LudwigFerdinand18 said:
roda com esse parametro : mkfs.f2fs -t 1 /dev/block/mmcblk0p38
e dai tenta fazer aquilo de restaurar as partições pelo backup q vc tem, o meu eu fiz e não deu esse erro ...
Click to expand...
Click to collapse
~ # ←[6nmkfs.f2fs -t 1 /dev/block/mmcblk0p38
mkfs.f2fs -t 1 /dev/block/mmcblk0p38
F2FS-tools: mkfs.f2fs Ver: 1.1.0 (2012-11-29)
Info: Trim is enabled
Info: sector size = 512
Info: total sectors = 27055872 (in 512bytes)
Info: zone aligned segment0 blkaddr: 256
Info: This device doesn't support TRIM
Error: Could not conduct fsync!!!
Info: format successful
Deu isso, vou tentar fazer o restore, cara uma coisa que eu notei, olha
Em adb :
[ro.build.characteristics]: [default]
[ro.build.date.utc]: [1406670206]
[ro.build.date]: [Tue Jul 29 16:43:26 CDT 2014]
[ro.build.description]: [titan_retbr_dstv-user 4.4.4 KXB21.85-18 24 release-keys
]
[ro.build.display.id]: [KXB21.85-18]
[ro.build.fingerprint]: [motorola/titan_retbr_dstv/titan_udstv:4.4.4/KXB21.85-18
/24:user/release-keys]
[ro.build.host]: [ilclbld34]
[ro.build.id]: [KXB21.85-18]
[ro.build.product]: [titan_udstv]
[ro.build.selinux]: [1]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [hudsoncm]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [24]
[ro.build.version.release]: [4.4.4]
[ro.build.version.sdk]: [19]
Em Fastboot :
ro.build.fingerprint[0]: motorola/titan_retbr_dstv/titan_ud
ro.build.fingerprint[1]: stv:5.0.2/LXB22.46-28/27:user/rele
ro.build.fingerprint[2]: ase-keys
ro.build.version.full[0]: Blur_Version.22.21.28.titan_retbr
ro.build.version.full[1]: _dstv.retbr.en.BR
ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
ro.build.version.qcom[1]: .04.04.02.048.045
version-baseband:
kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
kernel.version[2]: MP PREEMPT Tue Jan 6 10:40:31 CST 2015
Ele mostra Androids diferentes, em adb mostra 4.4.4 e em fastboot mostra 5.0.2
To restaurando o System, data deu failed
LudwigFerdinand18 said:
roda com esse parametro : mkfs.f2fs -t 1 /dev/block/mmcblk0p38
e dai tenta fazer aquilo de restaurar as partições pelo backup q vc tem, o meu eu fiz e não deu esse erro ...
---------- Post added at 07:57 PM ---------- Previous post was at 07:44 PM ----------
se não funcionar de jeito nenhum você tenta o seguinte, eu salvei do meu celular o fsync e coloquei no zip, vc baixa e descompacta ...
você vai rodar esse comando :
dd if=/sdcard1/fsync.img of=/sbin/fsync
Sem reiniciar o celular nem nada você vai tentar rodar o comando :
mkfs.f2fs -t 1 /dev/block/mmcblk0p38
mkfs.f2fs /dev/block/mmcblk0p38
roda os dois pra ter certeza e vê se dá erro de novo ...
Click to expand...
Click to collapse
Okay, se não funcionar vou tentar fazer isso aqui
LudwigFerdinand18 said:
roda com esse parametro : mkfs.f2fs -t 1 /dev/block/mmcblk0p38
e dai tenta fazer aquilo de restaurar as partições pelo backup q vc tem, o meu eu fiz e não deu esse erro ...
---------- Post added at 07:57 PM ---------- Previous post was at 07:44 PM ----------
se não funcionar de jeito nenhum você tenta o seguinte, eu salvei do meu celular o fsync e coloquei no zip, vc baixa e descompacta ...
você vai rodar esse comando :
dd if=/sdcard1/fsync.img of=/sbin/fsync
Sem reiniciar o celular nem nada você vai tentar rodar o comando :
mkfs.f2fs -t 1 /dev/block/mmcblk0p38
mkfs.f2fs /dev/block/mmcblk0p38
roda os dois pra ter certeza e vê se dá erro de novo ...
Click to expand...
Click to collapse
Manda o download do Fsync por favor, não deu certo a restauração :crying:
GnR_xXTurner said:
Manda o download do Fsync por favor, não deu certo a restauração :crying:
Click to expand...
Click to collapse
Ae fsync
LudwigFerdinand18 said:
Ae fsync
Click to expand...
Click to collapse
Olha o meu fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 4882(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x7
(bootloader) emmc: 16GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) cid: 0x000C
(bootloader) channelid: 0x19
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) date: 2014-10-21
(bootloader) sku: XT1069
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jan 7 8:20:17 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retbr_dstv/titan_ud
(bootloader) ro.build.fingerprint[1]: stv:5.0.2/LXB22.46-28/27:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.28.titan_retbr
(bootloader) ro.build.version.full[1]: _dstv.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-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld72) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:40:31 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.82-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.82-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.82-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.82-0-g72f9f12
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/1
(bootloader) productid: 0431980388
(bootloader) sutinfo:
(bootloader) ro.carrier: retbr

Bricked XT1058

I bricked my XT1058, tried to update over OTA than, my phone stuck in bootloader.
Can't flash gpt.bin because it says FAIL.
I can't find which one is the latest OTA Firmware that i received, neither where to find...
ANyone can help me??
Velcis Ribeiro said:
I bricked my XT1058, tried to update over OTA than, my phone stuck in bootloader.
Can't flash gpt.bin because it says FAIL.
I can't find which one is the latest OTA Firmware that i received, neither where to find...
ANyone can help me??
Click to expand...
Click to collapse
Share the output pls.. fastboot getvar all
Salik Iqbal said:
Share the output pls.. fastboot getvar all
Click to expand...
Click to collapse
version-bootloader: 30BE(*)
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Hynix S4 SDRAM DIE=4Gb
emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x1
secure: yes
mid: 026b
serialno: d60f3183
qe:
unlocked: Not supported
iswarrantyvoid: Not supported
max-download-size: 805306368
uid: 143E2D040C000100000000000000
imei: 000000000000000
meid:
sku: 000000000000000
cid: 0xdead
iccid:
date: 01-01-1970
cust_md5:
reason: Invalid CID
ro.build.date:
ro.build.id:
ro.build.tags:
ro.build.type:
ro.build.user:
ro.build.version.codename:
ro.build.version.incremental:
ro.build.version.release:
ro.mot.build.customerid:
ro.product.name:
ro.build.fingerprint:
ro.build.version.full:
kernel.version:
all:
finished. total time: 0.171s
this bro :/ IMEI 00000
Velcis Ribeiro said:
version-bootloader: 30BE(*)
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Hynix S4 SDRAM DIE=4Gb
emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x1
secure: yes
mid: 026b
serialno: d60f3183
qe:
unlocked: Not supported
iswarrantyvoid: Not supported
max-download-size: 805306368
uid: 143E2D040C000100000000000000
imei: 000000000000000
meid:
sku: 000000000000000
cid: 0xdead
iccid:
date: 01-01-1970
cust_md5:
reason: Invalid CID
ro.build.date:
ro.build.id:
ro.build.tags:
ro.build.type:
ro.build.user:
ro.build.version.codename:
ro.build.version.incremental:
ro.build.version.release:
ro.mot.build.customerid:
ro.product.name:
ro.build.fingerprint:
ro.build.version.full:
kernel.version:
all:
finished. total time: 0.171s
this bro :/ IMEI 00000
Click to expand...
Click to collapse
Is your phone is charge enough too flash any file?
Salik Iqbal said:
Is your phone is charge enough too flash any file?
Click to expand...
Click to collapse
Yes, fixed. Needed to enter in chinese BAIDU website and download there the LATEST firmware which is not available in any another website.
Velcis Ribeiro said:
Yes, fixed. Needed to enter in chinese BAIDU website and download there the LATEST firmware which is not available in any another website.
Click to expand...
Click to collapse
The same thing happened with my Moto X.
I installed the ROM 5.1, after completion made ​​an update via OTA.
I can not flash any file. When i try to flash the file gpt.bin by fastboot returns the error. Writing partition failed.
What more can i do?
I'm sorry for bad English. Thank you.
fernandes.xx said:
The same thing happened with my Moto X.
I installed the ROM 5.1, after completion made ​​an update via OTA.
I can not flash any file. When i try to flash the file gpt.bin by fastboot returns the error. Writing partition failed.
What more can i do?
I'm sorry for bad English. Thank you.
Click to expand...
Click to collapse
I got a firmware from Chinese Baidu website, if you want i can search for you the link on my Windows PC. If you didn't fixed it already try to find the latest firmware otherwise contact me, than i send to you!
Velcis Ribeiro said:
I got a firmware from Chinese Baidu website, if you want i can search for you the link on my Windows PC. If you didn't fixed it already try to find the latest firmware otherwise contact me, than i send to you!
Click to expand...
Click to collapse
I looked on google and downloaded several ROMs without success. Could you send me the link? Thank you very much.
What, 2 brazilians talking with each other in english? Am I dreaming?
Sorry guys, couldn't resist. So, even though you fixed your phone, seems that you tried to flash an older ROM or you flashed the wrong one. Can you tell more about how you fixed your phone? It can probably help others in similar situations.
Renan Lazarotto said:
What, 2 brazilians talking with each other in english? Am I dreaming?
Sorry guys, couldn't resist. So, even though you fixed your phone, seems that you tried to flash an older ROM or you flashed the wrong one. Can you tell more about how you fixed your phone? It can probably help others in similar situations.
Click to expand...
Click to collapse
Renan bem observado... Não tinha visto que nosso colega é brasileiro.
Sobre meu problema, irei contar desde o inicio.
Curioso efetuei o desbloqueio do bootloader, instalei o twrp 3.0 e juntamente cyanogenmod 12.1. Utilizei por algumas semanas porem achei melhor instalar novamente a versão original.
Seguindo alguns tutoriais da internet efetuei o download da Stock ROM 5.1 Lollipop e instalei pelo Motorola RDS Lite.
Até então mil maravilhas, instalei meus apps configurei como de costume... Foi quando apareceu a maldita mensagem informando sobre uma atualização de segurança, eu inocentemente (Burro ) aceitei a atualização, ocorreu tudo normalmente até o final onde ocorreu o boot.
Desde então só aparece as mensagens que disse anteriormente, já baixei diversas versões de ROM's tentei instalar de todas as maneiras possíveis (RDS, adb + fastboot, etc...) sempre me deparo com a mensagem que não é possível gravar a partição gpt.
Uma dica: Quando fazemos root, devemos ir até a pasta /system/app e procurar arquivos de nome "otaupdater.apk, updater.apk, upgrader.apk" e (no meu caso, deletei o blur-updater e bota-settings.apk), se não quiser deletar, apenas tire o k do final, pq sempre dá problema após root, e essas mensagens de atualização desaparecem, e o menu de atualização evapora.
Sent by XT687 phone
fernandes.xx said:
Renan bem observado... Não tinha visto que nosso colega é brasileiro.
Sobre meu problema, irei contar desde o inicio.
Curioso efetuei o desbloqueio do bootloader, instalei o twrp 3.0 e juntamente cyanogenmod 12.1. Utilizei por algumas semanas porem achei melhor instalar novamente a versão original.
Seguindo alguns tutoriais da internet efetuei o download da Stock ROM 5.1 Lollipop e instalei pelo Motorola RDS Lite.
Até então mil maravilhas, instalei meus apps configurei como de costume... Foi quando apareceu a maldita mensagem informando sobre uma atualização de segurança, eu inocentemente (Burro ) aceitei a atualização, ocorreu tudo normalmente até o final onde ocorreu o boot.
Desde então só aparece as mensagens que disse anteriormente, já baixei diversas versões de ROM's tentei instalar de todas as maneiras possíveis (RDS, adb + fastboot, etc...) sempre me deparo com a mensagem que não é possível gravar a partição gpt.
Click to expand...
Click to collapse
While I like seeing brazilians, please remember that this is a international forum and it is in the rules that the main language is english. So, lets keep our talk in english
About your issue, have you tried to flash everything BUT gpt? Maybe this way it'll boot. Or you can wait for @Velcis Ribeiro reply on how he saved his XT1058 - I can't help you with that, mine is a XT1050 (converted to XT1060 hehe)
This is the latest firmware: https://dl.lolinet.com/firmware/mot..._RETBR_5.1_LPAS23.12-21.7-1_cid12_CFC.xml.zip
Velcis Ribeiro said:
This is the latest firmware: https://dl.lolinet.com/firmware/mot..._RETBR_5.1_LPAS23.12-21.7-1_cid12_CFC.xml.zip
Click to expand...
Click to collapse
My moto X is alive ...
I couldn't download by link past, searched for and found the version code link below.
http://www.filefactory.com/file/2z7..._RETBR_5.1_LPAS23.12-21.7-1_cid12_CFC.xml.zip
Through the RSD Lite flashed the ROM where they recorded the gtp.bin and the motoboot.bin. An error occurred while flashing your system.
I took an old ROM and in the xml file I have deleted the lines below.
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="gpt" filename="gpt_signed" MD5="41ba4d961f96655c1fd25908a05151e8"/>
<step operation="flash" partition="motoboot" filename="motoboot" MD5="405029619219aa3011a7a86653c5236e"/>
I saved the file and blinked via RSD Lite. Ready my moto x came back to life.
Thank you very much
You're welcome!

Moto X Style XT1572 Brazil - NO SIGNAL

Estou com o mesmo problema com o Moto X Style XT1572, não consigo sinal, ele reconhece os 2 chips mais não dá sinal da operadora em nenhum. já testei outros chip e nada, já troquei a ROM e nada, alguém sabe dizer o que devo fazer agora?
CQA Test: PHONE ICCID: PHONE_ICCID_UNKNOWN",
"Phone ICCID Compare with SIM ICCID: ERROR
alguém falou para flesh radio.img mais onde consigo isso?
---
EN Google
I'm having the same problem with Moto X Style XT1572, I can not signal, it recognizes the 2 chips but gives no signal from the carrier in any. I already tested other chips and nothing, I already changed a ROM and nothing, does anyone know what I should do now?
CQA Test: PHONE ICCID: PHONE_ICCID_UNKNOWN ",
"Phone ICCID Compare with SIM ICCID: ERROR
Has anyone spoken to flash radio.img more where do I get this?

(bootloader) Check 'OEM unlocking' in Android Settings > Developer LINEAGE OS 16

Buenas noches, amigos tengo este inconveniente,tenia el bootloader desbloqueado, estaba en lineage os 17, el telefono solo me reconocia redes 2g, entonces cambie por lineage os 16, y seguia igual, entonces flashee stock rom LAKE_PPWS29.98-111-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info, y se solucionaba todo excepto que me salia el imei 0, entonces probe con varios firmware, y seguia igual, entonces volvi, a lineage os 16, y sin querer por quitarle el boot logo bootloader desbloqueado, presione el BLOQUEAR BOOTLOADER.bat, desde entonces el cel arranca lineage os 16, pero sin gapps, y solo reconoce redes 2g, y no me permite flashear stock ni me bootea twrp, ya intente repararlo con LENOVO MOTO SMART ASISTANT, y tampoco, quisiera saber que puedo hacer para volver a stock y dejarlo como lo compre, de ante mano, muchas gracias.
El equipo fue comprado en Falabella Colombia.
C:\Users\Andres Valcarcel\Desktop\LAKE_RETAIL_9.0_PPWS29.98-111-5_subsidy-DEFAUL
T_regulatory-DEFAULT_CFC.xml>fastboot oem unlock RYJNXK4P57KZXBGIC5CN
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Users\Andres Valcarcel\Desktop\LAKE_RETAIL_9.0_PPWS29.98-111-5_subsidy-DEFAUL
T_regulatory-DEFAULT_CFC.xml>

Categories

Resources