Database Develop

[Q] NO OTA update Help

Hello Forum,
Recently i made a mistake and updated my HTC One M7 4.3 Sense to 4.4 Google Edition. Instantly i decided to go back to HTC sense again because i love sense more.
I reverted my phone back to stock with Guru_Reset_M7_3.62.401.1.zip. Then Unrooted, LOCKED and S-ON. So far so good.
Right now my phone is Android 4.3, HTC Sense 5.5, Software Number 3.62.401.1
But when i check Software Updates, it says "There are no updates available for your phone" I have been waiting for a long time. Finally i checked my HBOOT. There is something wrong. Here is my HBOOT data.
TAMPERED
LOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.21.3236.04
OpenDSP-v32.120.274.0909
OS-3.62.1700.1
eMMC-boot 2048MB
Dec 9 2013,00:38:19.0
OS version is wrong. HTC Sense says 3.62.401.1 but Hboot says 3.62.1700.1. I think it is from Google Edition.
Maybe i am not getting update because of this problem,
Could you please help? Thanks in advance!
Best Regards

Aynen yanlış birşeyler var gibi. Eğer OTA güncellemelerini almak istiyorsan biraz uğraşman gerekecek. Öncelikle tekrar unlocked olup cihazı rootlayıp S-off olman lazım. Daha sonra fastboot tan cid ve mid numarana uygun (eğer TR cihazıysa HTC_M27 ve PN711000 olması lazım) 1.44 hboot flash layıp yine cid ve mid numarasına uygun stock ruu flashlaman gerekli.

Çok teşekkür ederim hızlı yanıt için. Daha önce dediğiniz gibi yapıp RUU yapmayı denedim ama hata verdi. Hboot 1.54 iken denedim. Daha eski bir os kurmayı denediğim için olabilir mi?
Telefonum Almanya kökenli, ona uygun 1.44 hboot buldum. Dediğiniz gibi yapıp hbootu flashlarsam. Eski versiyon Ruu ile duzelirmi?
Hboot 'taki os doğru versyonu gosterirmi?
Tekrar tesekkurler yanıt için. Duzelirse bir daha dokunmayacagim

yucelyilmaz said:
Çok teşekkür ederim hızlı yanıt için. Daha önce dediğiniz gibi yapıp RUU yapmayı denedim ama hata verdi. Hboot 1.54 iken denedim. Daha eski bir os kurmayı denediğim için olabilir mi?
Telefonum Almanya kökenli, ona uygun 1.44 hboot buldum. Dediğiniz gibi yapıp hbootu flashlarsam. Eski versiyon Ruu ile duzelirmi?
Hboot 'taki os doğru versyonu gosterirmi?
Tekrar tesekkurler yanıt için. Duzelirse bir daha dokunmayacagim
Click to expand...
Click to collapse
karizma60 said:
Aynen yanlış birşeyler var gibi. Eğer OTA güncellemelerini almak istiyorsan biraz uğraşman gerekecek. Öncelikle tekrar unlocked olup cihazı rootlayıp S-off olman lazım. Daha sonra fastboot tan cid ve mid numarana uygun (eğer TR cihazıysa HTC_M27 ve PN711000 olması lazım) 1.44 hboot flash layıp yine cid ve mid numarasına uygun stock ruu flashlaman gerekli.
Click to expand...
Click to collapse
Im sry to says this but you MUST use English here, other languages aren't allowed in the forum.
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Click to expand...
Click to collapse
Now post your ''fastboot getvar all'' without IMEI/SN.

Here is my fast boot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3977mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

yucelyilmaz said:
Here is my fast boot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3977mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
well I don't understand, if you had s-off earlier why did you used a guru reset rom instead of the 1.28.401 ruu.exe and why did you turned s-on again? And why not removing the tempered flag in bootloader if you went back to s-on? Not sure if 4.4 is out for your cid either. with s-off you could have tried differents EMEA cid....
---------- Post added at 08:50 PM ---------- Previous post was at 08:44 PM ----------
yucelyilmaz said:
Here is my fast boot getvar all
Click to expand...
Click to collapse
you can also manually flash the ota from stock recovery btw

- I had guru reset because RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7 failed.
- I turned s-on because, i wanted to back to stock.
- I removed tampered flash unfortunately it came back. No idea why.
Question, how can i install manually flash OTA from stock recovery. Where will i find the update file ?
Thanks
alray said:
well I don't understand, if you had s-off earlier why did you used a guru reset rom instead of the 1.28.401 ruu.exe and why did you turned s-on again? And why not removing the tempered flag in bootloader if you went back to s-on? Not sure if 4.4 is out for your cid either. with s-off you could have tried differents EMEA cid....
---------- Post added at 08:50 PM ---------- Previous post was at 08:44 PM ----------
you can also manually flash the ota from stock recovery btw
Click to expand...
Click to collapse

yucelyilmaz said:
- I had guru reset because RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7 failed.
Click to expand...
Click to collapse
Because you did not downgraded hboot to 1.44 before running the ruu
yucelyilmaz said:
- I turned s-on because, i wanted to back to stock.
Click to expand...
Click to collapse
Bad idea to s-on and not even required to revert back to stock.
yucelyilmaz said:
Question, how can i install manually flash OTA from stock recovery. Where will i find the update file ?
Click to expand...
Click to collapse
copy ota to phone
boot phone in stock recovery then hold vol + after press power then apply the ota. you need to apply all ota in order (1,2,3,4) you cant ota from 1 to 4. You can find the file if you search the forum.
Honestly you should just s-off again, downgrade hboot reset the bootloader flags and run the 1.28.401 ruu. That will make everthing clean again. keep s-off after the ruu so you'll be able to change cid to find the ota

As you said, i returned to S-OFF.
I have tried to downgrade my hboot to 1.44 but i get this
C:\adb>fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.729s
alray said:
Because you did not downgraded hboot to 1.44 before running the ruu
Bad idea to s-on and not even required to revert back to stock.
copy ota to phone
boot phone in stock recovery then hold vol + after press power then apply the ota. you need to apply all ota in order (1,2,3,4) you cant ota from 1 to 4. You can find the file if you search the forum.
Honestly you should just s-off again, downgrade hboot reset the bootloader flags and run the 1.28.401 ruu. That will make everthing clean again. keep s-off after the ruu so you'll be able to change cid to find the ota
Click to expand...
Click to collapse

Thank you for your help guys. My HTC one is perfectly stock and getting up updates ota.
Here is my steps.
- unlocked, rooted then s-off
- changed my cid to super cid
- flashed hboot 1.44
- removed tampered, locked
- Ruu Install
- S-on for %100 stock

No OTA Updates

English :
Hello, I can no longer do the OTA updates, I Unlocked. Would you have a solution? Thank you.
French :
Bonjour, je n'arrive plus à faire les mises à jour OTA, je suis Unlocked. Auriez-vous une solution ? Merci.
C:\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.22
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW
(bootloader) imei:
(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: 4210mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s

Venuz-Planeta said:
English :
Hello, I can no longer do the OTA updates, I Unlocked. Would you have a solution? Thank you.
French :
Bonjour, je n'arrive plus à faire les mises à jour OTA, je suis Unlocked. Auriez-vous une solution ? Merci.
C:\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.22
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW
(bootloader) imei:
(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: 4210mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
relock your bootloader and flash the 7.19.401.22 ruu, this will reset your phone back to stock. Make sure to backup your files first, the ruu will wipe everything from your phone. Once the ruu is flashed, check for ota updates and you'll get notified for the 7.19.401.30 update, download it and install the update before doing any modifications like unlocking again / flashing custom recovery / root. Instructions how to flash the RUU at post #1 of this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944, the 7.19.401.22 ruu is at post #2
Allo, re-verouille ton bootloader et ensuite installe le RUU version 7.19.401.22, ton téléphone va être remis aux valeurs d'usine. Fais une sauvegarde de tes fichiers important avant d'installer le RUU puisque cela va effacer tout le contenu du téléphone. Après avoir installé le RUU tu devrais recevoir une notification pour installer la mise à jour 7.19.401.30, installe-la avant de faire n'importe qu'elle modification (avant de déverrouiller le bootloader ou d'installer une custom recovery / root). Tu peux trouver les instructions et le fichier ici: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

Thank you very much, it worked! Once 7.19.401.30 update finished, can I unlocked the bootloader? Thank you.
Merci beaucoup, ça a fonctionné ! Une fois la mise à jour 7.19.401.30 terminé, puis-je débloqué le bootloader ? Merci.

Venuz-Planeta said:
Thank you very much, it worked! Once 7.19.401.30 update finished, can I unlocked the bootloader? Thank you.
Merci beaucoup, ça a fonctionné ! Une fois la mise à jour 7.19.401.30 terminé, puis-je débloqué le bootloader ? Merci.
Click to expand...
Click to collapse
Yes but you'll have to redo the same process if there is another update in the future. Unlocking the bootloader wipes some /data files needed to install ota updates.
http://android-revolution-hd.blogspot.ca/2013/03/negative-effects-of-unlocked-bootloader.html
Oui mais dans l’éventualité d'une autre mise à jour, il faudra recommencer le processus. Dévérouiiler le bootloader efface des fichiers de la partition /data nécessaire pour installer les mise à jour (certaine applications HTC, lire le lien ci-haut)
De rien

Moto Z3 Play Baseband no fount Imei Unknow

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

fashing_locked Moto G7 Plus

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"
}

Help, i can't flash

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