Related
Good evening friends , how about , I require your urgent help, recently acquired one htc m7 , the truth of it is that was being updated via wifi , leave it in the night , waking in the morning , the computer was frozen , Total you restart it , what was my surprise when rebooting the camera did not work , opening the application is closed immediately without giving any message or anything, and the upper headset not sound or with music or with calls to address was to place the cel in speaker to listen to the call, the music just would not heal up by the horn , then proceeded to read to see if an improved dowgrade , opened the bootloader via HTCDev , then change the recovery and rootee , all good so far , then proceeded to change it to s -off , as was in 4.4.3 did not work but I runruner firewater , the peo is that my hboot is 1.57 , and the firewater gave me error , I got a tutorial on xda where one of his steps indicate cyanogenmod put him wholly to install it without a problem, try again with firewater and nothing, any use 12 bottles and drink anything, try several times and nothing getting switch to S -Off , and now to get me more high I 'm stuck on cyanogenmod , because I do not get any rom that is compatible with my firmware is 6.15.599.101 , all rom there are 6.09.xxx basis according lei ... I can not install or ? good my doubts and where I require your help is
if anyone can provide me a nandroid backup or ruu compatible with firmware 6.15.599.101 , my CID is htc__332 and my MID is PN0711000
if anyone knows how I can solve it from hboot 1.57 to pass to S -Off
rom that I can get out of giving me error cyanogenmod on calls and turn the camera icon does not appear anywhere
I just realized that when you connect the htc cyanogenmod AIO RUNNER me to the CID and MID are blank
buenas tardes amigos, que tal, requiero de su ayuda urgente, recientemente adquiri un htc one m7, lo cierto del caso es que se estaba actualizando via wifi, lo deje en la noche, al despertar en la mañana, el equipo estaba congelado, total que lo reinicie, cual fue mi sorpresa que al reiniciarse la camara no funcionaba, al abrir la aplicacion se cerraba de inmediato sin dar ningun mensaje ni nada, y el auricular superior no sonaba, ni con musica ni con llamadas, para atender debia colocar el cel en altavoz para poder escuchar la llamada, igual la musica no sanaba por la corneta de arriba, entonces procedi a leer para ver si con un dowgrade mejoraba, abri el bootloader via htcdev, luego cambie el recovery y rootee, todo bien hasta ahora, luego procedi a cambiarlo a s-off, como ya estaba en 4.4.3 no me funcionaba runruner sino firewater, el peo es que mi hboot es el 1.57, y me daba error el firewater, consegui un tutorial de xda donde en uno de sus pasos indican meterle cyanogenmod, total que se lo instale sin problema, intente otra vez con firewater y nada, la aplicacion se bebe 12 botellas y nada, intente varias veces y nada que conseguia cambiar a S-Off, y ahora para mas colmo me consigo que estoy atascado en cyanogenmod, porque no consigo ninguna rom que sea compatible con mi firmware que es el 6.15.599.101, todas las rom que hay son base a 6.09.xxx... segun lei no puedo instalarlas o si? bueno mis dudas y donde requiero su ayuda es
si alguien me puede facilitar un nandroid backup o una ruu compatible con el firmware 6.15.599.101, mi cid es el htc__332
si alguien sabe como puedo resolver lo del hboot 1.57 para pasarlo a S-Off
que rom puedo meter para salir de cyanogenmod que me da error en las llamadas y aparte el icono de la camara no aparece por ningun lado
acabo de darme cuenta que con cyanogenmod al conectar el htc al AIO RUNNER me aparece el CID y el MID en blanco
C:\androidSDK\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3818mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.170s
C:\androidSDK\platform-tools>
this is my getvar all,
anyone can help me get the OS on my HTC?
Alguien puede decirme donde conseguir el OS de mi HTC?
davidsha said:
if anyone knows how I can solve it from hboot 1.57 to pass to S -Off
Click to expand...
Click to collapse
Sunshine s-off should work.
You will never find RUU compatible with .599 version. I'm not sure if your issue is software or hardware related, but if you want to confirm by restoring your phone with a RUU you will definitively need s-off to change your CID and MID and then run another version RUU like the .401 WWE version or the .1540 Dev edition.
If the issue persist after flashing a rom or even after flashing a RUU its probably hardware related and you'll have to send your phone for repair.
davidsha said:
C:\androidSDK\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3818mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.170s
C:\androidSDK\platform-tools>
this is my getvar all,
anyone can help me get the OS on my HTC?
Alguien puede decirme donde conseguir el OS de mi HTC?
Click to expand...
Click to collapse
You might try a different TWRP: 2.6.3.3 will work with most roms and 2.8.0.X will work with CM11 or those roms that require "block:by-name" support. If changing TWRP doesn't help, then you should try a stock custom rom like ARHD 53.0 or 81.0. Once successfully install try firewater again. If you get the "whelp this sucks" message then firewater will not work on your phone and your only option is Sunshine S-OFF. The downside is it cost $25 USD.
Sorry for the bleak outcome, but there does not seem to be a RUU/firmware for your phone. Hopefully, someone with a nandroid backup will step forward and provide one for you.
majmoz said:
You might try a different TWRP: 2.6.3.3 will work with most roms and 2.8.0.X will work with CM11 or those roms that require "block:by-name" support. If changing TWRP doesn't help, then you should try a stock custom rom like ARHD 53.0 or 81.0. Once successfully install try firewater again. If you get the "whelp this sucks" message then firewater will not work on your phone and your only option is Sunshine S-OFF. The downside is it cost $25 USD.
Sorry for the bleak outcome, but there does not seem to be a RUU/firmware for your phone. Hopefully, someone with a nandroid backup will step forward and provide one for you.
Click to expand...
Click to collapse
I can install the ARHD rom 81, still s -on and with my current firmware?
davidsha said:
I can install the ARHD rom 81, still s -on and with my current firmware?
Click to expand...
Click to collapse
Yes, according to the OP. "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" You just have to wipe data inside AROMA.
please help my phone does not pass the logo of Android, can put a custom , but if I touch something restart or eh aid could put a ruu
S -on unloked , hboot 1.56
DiegoJhosue said:
please help my phone does not pass the logo of Android, can put a custom , but if I touch something restart or eh aid could put a ruu
S -on unloked , hboot 1.56
Click to expand...
Click to collapse
please post the output of "fastboot getvar all" (remove imei/sn)
already asked the same thing here btw
and you didn't replied...
sorry did not see in time , here my information
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.19.631.9
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3858mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
DiegoJhosue said:
sorry did not see in time , here my information
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.19.631.9
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3858mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Relock your bootloader:
Code:
fastboot oem lock
then flash this RUU
http://www.htc1guru.com/2014/03/rogers-android-ruu/
ok thanks downloading , but not back to factory recovery?
DiegoJhosue said:
ok thanks downloading , but not back to factory recovery?
Click to expand...
Click to collapse
The RUU will reset your phone back to stock
thanks friend one last question I install in fastboot mode or RUU
thank you very much friend I could relive my phone I have two major problems
1- serves no wifi or bt
2- if I turn off the phone will not turn back until discharge and charging from 0%
DiegoJhosue said:
thank you very much friend I could relive my phone I have two major problems
1- serves no wifi or bt
2- if I turn off the phone will not turn back until discharge and charging from 0%
Click to expand...
Click to collapse
Looks like you have an hardware problem. Flashing a RUU should fix any software or firmware issue so its most likely the hardware.
OK thanks very much my fone went sat
Enviado desde mi SM-G900F mediante Tapatalk
Hello everyone, I have a Moto Z3 Force XT1929-6 Latam Chile I had updated the firmware and after that the phone is working but the baseband is not found and the IMEI is unknow and of course there is no wi-fi and no carrier signal. I try with a lot of roms stock but i cant fix this. Some one can help me please?.. Thank you!!
leodechiloe said:
Hello everyone, I have a Moto Z3 Force XT1929-6 Latam Chile I had updated the firmware and after that the phone is working but the baseband is not found and the IMEI is unknow and of course there is no wi-fi and no carrier signal. I try with a lot of roms stock but i cant fix this. Some one can help me please?.. Thank you!!
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
DOnt work. Failed to connect or Doesn´t apropiate firmware .
I have the same problem "baseband not found"
no signal or wifi ... moto z3 play xt1929-6 beckham at & t MX ..... any solution? I already tried different roms both att and retail and it remains the same ..
I thought about using blankflash but I don't know how to do the procedure. any clues please?
Yayo70136 said:
I have the same problem "baseband not found"
no signal or wifi ... moto z3 play xt1929-6 beckham at & t MX ..... any solution? I already tried different roms both att and retail and it remains the same ..
I thought about using blankflash but I don't know how to do the procedure. any clues please?
Click to expand...
Click to collapse
Rayos! if u find the solution can post here?? i do the same, oka? ... mi zplay 3 is almost a
personal weapon
Yayo70136 said:
I have the same problem "baseband not found"
no signal or wifi ... moto z3 play xt1929-6 beckham at & t MX ..... any solution? I already tried different roms both att and retail and it remains the same ..
I thought about using blankflash but I don't know how to do the procedure. any clues please?
Click to expand...
Click to collapse
Cannot use a blankflash unless device is in emergency download mode (edl)
All a blankflash does is flash a bootloader, if the bootloader is corrupted.
It will not fix radio issues.
Sent from my Moto E (4) using Tapatalk
leodechiloe said:
Rayos! if u find the solution can post here?? i do the same, oka? ... mi zplay 3 is almost a
personal weapon
Click to expand...
Click to collapse
I currently found a solution partially ... Flash havoc os android 9 with twrp flash gaps and it gives me network and internet, everything works. Except motorcycle horn mod, it is a momentary solution in what is a solution since when flashing the stock rom it keeps leaving me without signal....
I was thinking about flashing the stock rom without the commands that eliminate the modem based on this configuration to see if it is possible that this way the problem is fixed, since in havoc os bluetooth did not work for me, so I flashed it directly from the stock rom and it worked It was repaired, so now I'm looking to do something similar with the modem aver if I'm lucky, although I don't know what the exact commands to achieve it would be ... I'll investigate further, I should find a solution !! Let me know if you recovered signal with. havoc os. You have to be persistent since sometimes it does not catch the signal, it tries with a clean installation.
Skip
fastboot flash modem NON-HLOS. bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I hope it works. I'll try as soon as I can.
great! thx 4 compart u approach!!
You can Fastboot flash all the imgs in the stock ROM. I believe it's only boot, and recovery that's needed, but might as well flash em all (3-4) to be safe. Then LMSA will recognize your device and recover it.
Alternatively, you can install one of the custom roms, then using TWRP, back up your EFS Partition to an SD card.
Then after installing Stock ROM, Fastboot twrp, and restore your EFS.
hello. i try with almost all rom for beckham, one for every variant from this site ( https://mirrors.lolinet.com/firmware/moto/beckham/official ), one for android 8.1 and the other for android 9, without lucky.. no simm , 4g and no wifi. I find that the base band exactly for my version is "Modem Version: M636_30.77.01.101R2 beckham latam custom" not present in lolinet, but present in a pay site (for tecnical people).my question is.. if i buy that rom because is the same version, the problem should fix'??. thankyou
Okey.. FIXED! In my case, Is just the band base version compatibility. I buy de oficial, oficial rom (exactly like say in the box.. in my case xt1929-6 P/N PA9T0016CL <--- this is the serial that u need find in the web). And voila! all oki doki.. Looking in this web, i a web for technik people (electric manual, especific roms stock, etc). 1.- http://www.ligtelgsm.com.br/downloads/class/index.php?p=file&idprog=9356 2.- https://www.firmwaredown.com.br/ ... in the sit 1.- i buy a little account. If u wee u exactly base band (i ask to people with the same phone and company phone-- they send me a screen impr) y can donwnload and up 4you. But, looking good, i have few megas more. GLuck
leodechiloe said:
Okey.. FIXED! In my case, Is just the band base version compatibility. I buy de oficial, oficial rom (exactly like say in the box.. in my case xt1929-6 P/N PA9T0016CL <--- this is the serial that u need find in the web). And voila! all oki doki.. Looking in this web, i a web for technik people (electric manual, especific roms stock, etc). 1.- http://www.ligtelgsm.com.br/downloads/class/index.php?p=file&idprog=9356 2.- https://www.firmwaredown.com.br/ ... in the sit 1.- i buy a little account. If u wee u exactly base band (i ask to people with the same phone and company phone-- they send me a screen impr) y can donwnload and up 4you. But, looking good, i have few megas more. GLuck
Click to expand...
Click to collapse
Hello, so you could solve it ??? I can't find the version for my cell phone !!! PA9T0000MX. Doesn't appear on the pages you mention ...
Yayo70136 said:
Hello, so you could solve it ??? I can't find the version for my cell phone !!! PA9T0000MX. Doesn't appear on the pages you mention ...
Click to expand...
Click to collapse
option 2. ask in face or somtehing what version they have.. I ask in facebook market. 128/6g Z3p - same company sailes. They send me one imprscreen, so, with the information aboud band base, looking for the roms.... Every rom in the description, have de band base number exact...
En español: pidele, pregunta a la gente de facebook market u otro medio que este vendiendo un telefono como el tuyo, x e modelo exacto, y en la compañia que podia funcionar (que sim acepta.. aqui en chile estan todos liberados para todas las compañias). Pidele que te envie un pantallazo de la banda de base, que version exacta es.. y ese numero, con punto y coma, lo buscas en las descripciones de las roms.. (que tienen.. con punto y coma.. exactamente el numero de la banda base detallado... y en base a eso buscas las rooms candidatas...) MI cellular es un xt1929-6 de banda de base M636_30.77.01.101R (modem version M636_30.77.01.101R), y la que baje e instale fue la rom para una xt1929-5 que tiene la misma version del modem.. o sea banda de base M636_30.77.01.101R.. Captas?
MI phone is a XT1929-6 SINGLE SIM but i fix with a xt1929-5 DUAL SIM room --> http://www.ligtelgsm.com.br/downloads/class/index.php?p=file&idprog=9356 because have the same band base.
leodechiloe said:
option 2. ask in face or somtehing what version they have.. I ask in facebook market. 128/6g Z3p - same company sailes. They send me one imprscreen, so, with the information aboud band base, looking for the roms.... Every rom in the description, have de band base number exact...
En español: pidele, pregunta a la gente de facebook market u otro medio que este vendiendo un telefono como el tuyo, x e modelo exacto, y en la compañia que podia funcionar (que sim acepta.. aqui en chile estan todos liberados para todas las compañias). Pidele que te envie un pantallazo de la banda de base, que version exacta es.. y ese numero, con punto y coma, lo buscas en las descripciones de las roms.. (que tienen.. con punto y coma.. exactamente el numero de la banda base detallado... y en base a eso buscas las rooms candidatas...) MI cellular es un xt1929-6 de banda de base M636_30.77.01.101R (modem version M636_30.77.01.101R), y la que baje e instale fue la rom para una xt1929-5 que tiene la misma version del modem.. o sea banda de base M636_30.77.01.101R.. Captas?
MI phone is a XT1929-6 SINGLE SIM but i fix with a xt1929-5 DUAL SIM room --> http://www.ligtelgsm.com.br/downloads/class/index.php?p=file&idprog=9356 because have the same band base.
Click to expand...
Click to collapse
Would you be so kind as to provide me with the commands I use to flash your device? thanks and greetings!
Yayo70136 said:
Would you be so kind as to provide me with the commands I use to flash your device? thanks and greetings!
Click to expand...
Click to collapse
Make a new text document. Paste:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.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 system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot reboot
Rename you file.txt to file.bat. Cut in u room folder and click. Good Luck
exactly that problem is the one that occurred to me the bootloader is corrupt and does not allow me to update it with any rom so I cannot repair the radio signal of my phone so I thought I would use the blankflash file to repair the boot loader and be able to update with stock rom but I don't know how a hard brick could be caused in my moto z3 play currently, I can enter fastboot mode and flash any rom beckham and the cell phone works but without signal and without wifi: / any ideas ??? Any help is appreciated !!!! I've been like this for almost a month!:crying:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZY2...........
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 1FB614B6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ..................
(bootloader) meid:
(bootloader) date: 09-14-2018
(bootloader) sku: XT1929-6
(bootloader) carrier_sku: XT1929-6
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 3890
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-22/d2da2:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.271.29.beckham.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gebfe3c50a253
(bootloader) kernel.version[1]: -02598-g4bfe89b274ac ([email protected]
(bootloader) kernel.version[2]: 2) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Thu Mar 12 22
(bootloader) kernel.version[4]: :35:14 CDT 2020
(bootloader) git:abl: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) git:xbl: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) gitmic: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) git:rpm: MBM-3.0-beckham_sprint-33b79ec-190708
(bootloader) git:tz: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:hyp: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:devcfg: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib64: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:keymaster: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) gitrov: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:storsec: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: attmx
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.146s
sd_shadow said:
Cannot use a blankflash unless device is in emergency download mode (edl)
All a blankflash does is flash a bootloader, if the bootloader is corrupted.
It will not fix radio issues.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Yayo70136 said:
exactly that problem is the one that occurred to me the bootloader is corrupt and does not allow me to update it with any rom so I cannot repair the radio signal of my phone so I thought I would use the blankflash file to repair the boot loader and be able to update with stock rom but I don't know how a hard brick could be caused in my moto z3 play currently, I can enter fastboot mode and flash any rom beckham and the cell phone works but without signal and without wifi: / any ideas ??? Any help is appreciated !!!! I've been like this for almost a month!:crying:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZY2...........
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 1FB614B6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ..................
(bootloader) meid:
(bootloader) date: 09-14-2018
(bootloader) sku: XT1929-6
(bootloader) carrier_sku: XT1929-6
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 3890
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-22/d2da2:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.271.29.beckham.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gebfe3c50a253
(bootloader) kernel.version[1]: -02598-g4bfe89b274ac ([email protected]
(bootloader) kernel.version[2]: 2) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Thu Mar 12 22
(bootloader) kernel.version[4]: :35:14 CDT 2020
(bootloader) git:abl: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) git:xbl: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) gitmic: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) git:rpm: MBM-3.0-beckham_sprint-33b79ec-190708
(bootloader) git:tz: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:hyp: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:devcfg: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib64: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:keymaster: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) gitrov: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:storsec: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: attmx
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.146s
Click to expand...
Click to collapse
Doesn't sound like a corrupted bootloader.
Sounds like mismatched modem firmware.
Bit if you want to flash the blankflash, flash twrp,
Look for reboot to edl or use
Code:
adb reboot edl
I appreciate your prompt response but it doesn't seem to work! I think that if the bootloader was damaged because before it flashed other roms and they started! now they do not go beyond the motorola logo. (havoc os, RR, etc all install without errors but when rebooting it does not go beyond the logo and goes into infinite loop rebooting. I thought that the version of the bootloader is the last one to update and I cannot return the command fastboot flash bootloader bootloader. img always fails with each and every one of the roms that I have tried to flash ... for this reason I was thinking of starting from 0 with blankflash ... but in reality I don't know if it works ..... you seem to know more than I do. idea ?? motorola smart assistant does not recognize the cell phone !!! It is worth mentioning that I am from Mexico operator att version PA9T0000MX .... greetings from a distance!
C:\adb>fastboot reboot edl
fastboot: usage: unknown reboot target edl
C:\adb>adb fastboot reboot edl
adb.exe: unknown command fastboot
C:\adb>adb reboot edl
error: no devices/emulators found
sd_shadow said:
Doesn't sound like a corrupted bootloader.
Sounds like mismatched modem firmware.
Bit if you want to flash the blankflash, flash twrp,
Look for reboot to edl or use
Code:
adb reboot edl
Click to expand...
Click to collapse
Yayo70136 said:
I appreciate your prompt response but it doesn't seem to work! I think that if the bootloader was damaged because before it flashed other roms and they started! now they do not go beyond the motorola logo. (havoc os, RR, etc all install without errors but when rebooting it does not go beyond the logo and goes into infinite loop rebooting. I thought that the version of the bootloader is the last one to update and I cannot return the command fastboot flash bootloader bootloader. img always fails with each and every one of the roms that I have tried to flash ... for this reason I was thinking of starting from 0 with blankflash ... but in reality I don't know if it works ..... you seem to know more than I do. idea ?? motorola smart assistant does not recognize the cell phone !!! It is worth mentioning that I am from Mexico operator att version PA9T0000MX .... greetings from a distance!
C:\adb>fastboot reboot edl
fastboot: usage: unknown reboot target edl
C:\adb>adb fastboot reboot edl
adb.exe: unknown command fastboot
C:\adb>adb reboot edl
error: no devices/emulators found
Doesn't sound like a corrupted bootloader.
Sounds like mismatched modem firmware.
Bit if you want to flash the blankflash, flash twrp,
Look for reboot to edl or use
Click to expand...
Click to collapse
While twrp is booted?
Sent from my ali using XDA Labs
I am using platform tools I use "fastboot reboot edl" and nothing happens. I don't understand what you mean by "while twrp starts" ??
or maybe you mean write command in twrp terminal ???
sd_shadow said:
While twrp is booted?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
EN-US:
In short I can't flash on any official device rom, and the bootloader is unlocked, which I actually need to enable and the OEM at the developer's option.
But I can't turn on the device because the phone says it has a different operating system, and goes back to fastboot. (I can't go to any other screen besides fastboot)
Can anyone help me with this?
ps: I'm using the translator because I don't speak English.
PT-BR:
Resumidamente eu não consigo da flash em nenhuma rom oficial do dispositivo, e o bootloader esta desbloqueado, o que na verdade preciso habilitar e o OEM na opção do desenvolvedor.
Mais não consigo ligar o aparelho pois o celular diz está com um sistema operacional diferente, e volta para o fastboot. (Não consigo ir para nenhuma outra tela fora o fastboot)
Alguém pode me ajudar com isso?
ps: Eu tou usando o Tradutor pois não falo inglês.
PU Kirito LP said:
EN-US:
In short I can't flash on any official device rom, and the bootloader is unlocked, which I actually need to enable and the OEM at the developer's option.
But I can't turn on the device because the phone says it has a different operating system, and goes back to fastboot. (I can't go to any other screen besides fastboot)
Can anyone help me with this?
ps: I'm using the translator because I don't speak English.
PT-BR:
Resumidamente eu não consigo da flash em nenhuma rom oficial do dispositivo, e o bootloader esta desbloqueado, o que na verdade preciso habilitar e o OEM na opção do desenvolvedor.
Mais não consigo ligar o aparelho pois o celular diz está com um sistema operacional diferente, e volta para o fastboot. (Não consigo ir para nenhuma outra tela fora o fastboot)
Alguém pode me ajudar com isso?
ps: Eu tou usando o Tradutor pois não falo inglês.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
------------------
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-191220
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0055749849
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 0F2A4B3E
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577096137011
(bootloader) meid:
(bootloader) date: 04-05-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C44559
(bootloader) battery-voltage: 4320
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:9/PPW29.98-
(bootloader) ro.build.fingerprint[1]: 28/b7d2f:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.31.31.lake.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g73ca513-0001
(bootloader) kernel.version[1]: 1-g007505b ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Dec 11 09:54:13 CST
(bootloader) kernel.version[4]: 2018
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9-191220
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-191220
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-191220
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-191220
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.312s
PU Kirito LP said:
What does getvar all say?
------------------
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-191220
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0055749849
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 0F2A4B3E
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577096137011
(bootloader) meid:
(bootloader) date: 04-05-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C44559
(bootloader) battery-voltage: 4320
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:9/PPW29.98-
(bootloader) ro.build.fingerprint[1]: 28/b7d2f:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.31.31.lake.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05200-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g73ca513-0001
(bootloader) kernel.version[1]: 1-g007505b ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Dec 11 09:54:13 CST
(bootloader) kernel.version[4]: 2018
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9-191220
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-191220
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-191220
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-191220
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-191220
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.312s
Click to expand...
Click to collapse
Says bootloader is locked.
Code:
securestate: flashing_locked
And baseband is missing
Code:
version-baseband: <not found>
Try using the unlock code again.
Sent from my ocean using XDA Labs
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
If that doesn't work see
https://forum.xda-developers.com/showpost.php?p=81614501&postcount=9
Sent from my ocean using XDA Labs
sd_shadow said:
Says bootloader is locked.
Code:
securestate: flashing_locked
And baseband is missing
Code:
version-baseband: <not found>
Try using the unlock code again.
Sent from my ocean using XDA Labs
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
If that doesn't work see
https://forum.xda-developers.com/showpost.php?p=81614501&postcount=9
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
check 'allow oem unlock' in android settings developer (bootloader) options.
is sending I enable, plus the internet does not pay for lack of the modem.
even if i use bluetooth to use internet, or use the pc to send internet to the cell phone i can't enable the OEM in the developer's option.
PU Kirito LP said:
Says bootloader is locked.
And baseband is missing
------------------
check 'allow oem unlock' in android settings developer (bootloader) options.
is sending I enable, plus the internet does not pay for lack of the modem.
even if i use bluetooth to use internet, or use the pc to send internet to the cell phone i can't enable the OEM in the developer's option.
Click to expand...
Click to collapse
Did you lock the bootloader or did it seem to lock it's self?
Sent from my ocean using XDA Labs
sd_shadow said:
Did you lock the bootloader or did it seem to lock it's self?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
-----------------
in this case I formatted the cell phone and the oem option was disabled. and now I can’t flash the roms anymore.
PU Kirito LP said:
-----------------
in this case I formatted the cell phone and the oem option was disabled. and now I can’t flash the roms anymore.
Click to expand...
Click to collapse
I think the only fix is boot into edl mode
Code:
fastboot oem blankflash
Then flash a blankflash
Sent from my ocean using XDA Labs
sd_shadow said:
I think the only fix is boot into edl mode
Code:
fastboot oem blankflash
Then flash a blankflash
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
But how do I do this? boot into edl mode
I never hear about that command just do I apply?
Code:
fastboot oem blankflash
PU Kirito LP said:
But how do I do this? boot into edl mode
I never hear about that command just do I apply?
Click to expand...
Click to collapse
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I will try to run tests later.
sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
None of the things on that page worked. I'm still in the same problem.
PU Kirito LP said:
------------------
None of the things on that page worked. I'm still in the same problem.
Click to expand...
Click to collapse
What things?
Sent from my ocean using XDA Labs
sd_shadow said:
See my blankflash post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I tried everything that was here on this link but I was not successful.
I'm trying to activate the 'Unlock OEM from the developer option' by ADB Shell, since the wi-fi and the operator chip won't catch on.
But I haven't had much success yet, I just found some commands to enter developer mode via adb shell. But I found nothing on how to activate the Unlock OEM via ADB Shell.
PU Kirito LP said:
------------------
I tried everything that was here on this link but I was not successful.
I'm trying to activate the 'Unlock OEM from the developer option' by ADB Shell, since the wi-fi and the operator chip won't catch on.
But I haven't had much success yet, I just found some commands to enter developer mode via adb shell. But I found nothing on how to activate the Unlock OEM via ADB Shell.
Click to expand...
Click to collapse
Fastboot oem blankflash failed?
Sent from my ocean using XDA Labs
sd_shadow said:
Fastboot oem blankflash failed?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
Yes, it failed.
PU Kirito LP said:
------------------
Yes, it failed.
Click to expand...
Click to collapse
Dod you try to boot twrp?
Sent from my ocean using XDA Labs
sd_shadow said:
Dod you try to boot twrp?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
------------------
I can go to Recovery mode, but I can't send TWRP to my cell phone.
i have been in exactly the same problem since last year,
Eu to com o mesmo problema desde o ano passado, e até hoje nao achei uma solução pro Flashing_locked
Coxinha2139 said:
i have been in exactly the same problem since last year,
Eu to com o mesmo problema desde o ano passado, e até hoje nao achei uma solução pro Flashing_locked
Click to expand...
Click to collapse
[PT-BR]
Estou com o mesmo problema, levei na assistência e foi diagnosticado com problema na memoria eMMC
[EN-US]
I have the same problem. Sent to technical assistance, and I was told that it is a hardware problem on eMMC memory.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
C: \ Users \ jared \ Downloads \ Compressed \ Motorola_Moto_X4_XT1900-4_PAYTON_OPENMX_9.0_PPWS29.69-40-3-1_ (por_motostockrom.com) \ Motorola_Moto_X4_XT1900-4_PAYTON_OPENMX_9.0_PPWS29.69-40-3
getvar: max-sparse-size FAILED (remoto: comando desconocido)
terminado. tiempo total: 0.016s
(cargador de arranque) slot-count-size: no encontrado
(cargador de arranque) slot-suffi: no encontrado
...
(gestor de arranque) 'fb_mode_setfixes' no es un comando oem compatible
(gestor de arranque) Ver 'ayuda de fastboot oem'
FAILED (falla remota)
terminado. tiempo total: 0.000s
(cargador de arranque) slot-countxes: no encontrado
(gestor de arranque) slot-suf: no encontrado
(cargador de arranque) slot-suffi: no encontrado
(cargador de arranque) tipo de partición: no encontrado
(gestor de arranque) max-download-: no encontrado
el destino no informó el tamaño máximo de descarga
enviando 'partición' (37 KB) ...
FAILED (lectura de estado fallida (demasiados enlaces))
terminado. tiempo total: 3.085s
help please
HaschwalthU said:
C: \ Users \ jared \ Downloads \ Compressed \ Motorola_Moto_X4_XT1900-4_PAYTON_OPENMX_9.0_PPWS29.69-40-3-1_ (por_motostockrom.com) \ Motorola_Moto_X4_XT1900-4_PAYTON_OPENMX_9.0_PPWS29.69-40-3
getvar: max-sparse-size FAILED (remoto: comando desconocido)
terminado. tiempo total: 0.016s
(cargador de arranque) slot-count-size: no encontrado
(cargador de arranque) slot-suffi: no encontrado
...
(gestor de arranque) 'fb_mode_setfixes' no es un comando oem compatible
(gestor de arranque) Ver 'ayuda de fastboot oem'
FAILED (falla remota)
terminado. tiempo total: 0.000s
(cargador de arranque) slot-countxes: no encontrado
(gestor de arranque) slot-suf: no encontrado
(cargador de arranque) slot-suffi: no encontrado
(cargador de arranque) tipo de partición: no encontrado
(gestor de arranque) max-download-: no encontrado
el destino no informó el tamaño máximo de descarga
enviando 'partición' (37 KB) ...
FAILED (lectura de estado fallida (demasiados enlaces))
terminado. tiempo total: 3.085s
help please
Click to expand...
Click to collapse
Code:
getvar: max-sparse-size FAILED
(remote: unknown command) finished. total time: 0.016s
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found ...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader ) See 'fastboot oem help' FAILED
(remote failure) finished. total time: 0.000s
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition type: not found
( bootloader) max-download-: destination not found did not report maximum download size sending 'partition' (37 KB) ... FAILED
(read failed status (too many links)) finished. total time: 3.085s
What does getvar all say? (remove the IMEI before posting)
Code:
fastboot getvar all
sd_shadow said:
Code:
getvar: max-sparse-size FAILED
(remote: unknown command) finished. total time: 0.016s
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found ...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader ) See 'fastboot oem help' FAILED
(remote failure) finished. total time: 0.000s
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition type: not found
( bootloader) max-download-: destination not found did not report maximum download size sending 'partition' (37 KB) ... FAILED
(read failed status (too many links)) finished. total time: 3.085s
What does getvar all say? (remove the IMEI before posting)
Code:
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-f8d873e-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY2252L7QM
(bootloader) cid: 0x0032
just check that, it does not give more information
HaschwalthU said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-f8d873e-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY2252L7QM
(bootloader) cid: 0x0032
just check that, it does not give more information
Click to expand...
Click to collapse
What does the bootloader screen say?
Does it say oem_locked?
sd_shadow said:
¿Qué dice la pantalla del cargador de arranque?
¿Dice oem_locked?
Click to expand...
Click to collapse
Actualmente, sí, pero aunque el OEM está desbloqueado, todavía muestra el mismo error.
HaschwalthU said:
Actualmente, sí, pero aunque el OEM está desbloqueado, todavía muestra el mismo error.
Click to expand...
Click to collapse
I believe you need to boot into EDL Mode and use a blankflash.
See
How to boot into EDL Mode
There is a blankflash here
https://mirrors.lolinet.com/firmware/moto/payton/blankflash/
none of the above worked
sd_shadow said:
I believe you need to boot into EDL Mode and use a blankflash.
See
How to boot into EDL Mode
There is a blankflash here
https://mirrors.lolinet.com/firmware/moto/payton/blankflash/
Click to expand...
Click to collapse
none of the above worked
HaschwalthU said:
none of the above worked
Click to expand...
Click to collapse
I don't have any more ideas.
sd_shadow said:
I don't have any more ideas.
Click to expand...
Click to collapse
thanks