Moto Z3 Play Baseband no fount Imei Unknow

Search This thread

Loko_vr

Member
Apr 6, 2011
11
3
Volta Redonda
I solved this!

After trying all possible procedures and ROMS, and causing hard brick on my Moto Z3 Play several times, I solved the problem with a Sprint operator firmware. With it, I recovered the baseband, so wifi and network signal (SIM 1 and 2) went back to work.

This is the firmware:
XT1929-3_BECKHAM_SPRINT_9.0_PCWS29.85-36-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC (download)

Use these commands in fastboot mode:
Code:
fastboot getvar max-sparse-size 
fastboot oem fb_mode_set
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot

Wait for the first boot (takes a few minutes) and check if you have fixed the problem.

If it is fixed, you can flash the latest firmware available for your device and region. I, for example, used the firmware XT1929-6_BECKHAM_RETBR_9.0_PPWS29.131-27-1-22.

Then, if you are unable to make other updates via OTA, use the Rescue and Smart Assistant (LMSA) program to update.

My Moto Z3 Play now has the latest firmware available and is working perfectly.
 

Attachments

  • Screenshot_20200727-140516.png
    Screenshot_20200727-140516.png
    68.5 KB · Views: 53

henrispc013

Member
May 5, 2013
22
3
São Paulo
The solution for this error is actually pretty simple. Download the latest firmware from your phone and flash the modem with the commands above. Based on previous experiences with Motorola phones, "Baseband_unknown" occurs when your NON-HLOS file gets downgraded or corrupted for some reason, and the only "compatible" file so to say is found only in the most recent version of the Stock rom (unless you're never updated the phone, in this case the "compatible" file will be the NON-HLOS file contained in whatever stock rom version you've been using).

EDIT: corrections
 

FcoEsc

New member
Apr 13, 2021
1
0
I just solved an Z3 Play ATT from Mexico with this
at this time this is the latest software.
But the different step I did is to flash it with "Moto_v1.1" software
Just register & login, then flash the rom selecting flashfile.xml
 
Last edited:

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,983
2
10,009
South Dakota
goo.gl
Motorola Droid X
Amazon Fire

bitflung

New member
Jun 3, 2014
1
0
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!!
I HAVE FIXED IT!
(i'm not the OP)

first, a few notes:
1. i have the Z3 Play XT1929-4 RETUS. this is likely not a significant difference
2. the lenovo "rescue and smart assistant" did NOTHING for me. don't bother installing that crapware

my understanding of the problem:
1. one or both of the /modemst1 /modemst2 partitions are corrupted
2. these partitions can be READ or ERASED, but cannot be directly WRITTEN
3. the FSG partition, aka "filesystem golden copy" will be cloned to the /modemst1 partition when it is invalid (i'm getting this info from here: https://xdaforums.com/t/info-android-device-partitions-and-filesystems.3586565/ )
4. somehow the /modem partition might play a role in updating the /modemst2 partition in a similar way? i think?
5. here's the kicker: this is an A/B device. so there are two copies of most partitions, including the /modem and /fsg partitions
6. when /modemst1 and /modemst2 are rebuilt by the OS, apparently the rebuild will sometimes pull from the WRONG A/B source ... in other words, NOT the /modem and /fsg that you are flashing when you update to the stock ROM

the fix:
1. follow the normal process for acquiring stock firmware (i used lolinet to acquire mine)
2. as usual, look at the flashfile.xml for the list of commands you'll run
3. (optional?) this is a motorola phone and there is a motorola-specific version of fastboot available. i found my copy at http://firmware.center and used that (aka mfastboot.exe) rather than the general fastboot.exe
4. flash BOTH the A and the B partitions for /modem and /fsg
4.a example: replace the below
mfastboot flash modem NON-HLOS.bin mfastboot flash fsg fsg.mbn
with this more complete code targetting both A and B partitions
mfastboot flash modem_a NON-HLOS.bin mfastboot flash modem_b NON-HLOS.bin mfastboot flash fsg_a fsg.mbn mfastboot flash fsg_b fsg.mbn
4.b. the rest of the flashing process is likely still required, or at the very least the lines which erase /modemst1 and /modemst2

this is what i have done, and i've now recovered my moto z3 play retus.
hope it helps someone else (i realize this thread is a year old, but it's still the closest thing to help that i found as i was searching for a solution all day here)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    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?
    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
    1
    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 ... :(

    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.
    1
    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 (hudsoncm@ilclbld15
    (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) git:pmic: 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) git:prov: 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
    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