• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[Index] Motorola Flashing Utilities and Firmware (Unbrick Your Moto)

Search This thread

w4rh4ck3r

Member
Jul 26, 2016
23
2
Fernandópolis
Emergency Download Mode
If your Moto will not boot, and your PC shows it as Qualcomm HS-USB QDLoader 9008 or​
Qualcomm QHSUSB_Bulk​
It's in Emergency Download Mode​
There are a few methods that can be tried to recover the device.
  • Disconnect or let the battery die.
    • For some devices, if you let the battery die, so that it will power off, then recharge,
    • it will may power on normally, or maybe you can get to the bootloader to reflash the firmware.
  • Flash a Blank Flash
    • A Blank Flash is a special Firmware created by the processor manufacturer.
    • A different Blank Flash is created for chip model.
    • These are leaked by someone who has access to them.
  • Flash a mmcblk0.img or loader.img
    • A mmcblk0.img is a copy of the whole device depending on the device 16gb, 32gb or larger.
    • A loader.img is just 165mb
    • Both the mmcblk0.img and the loader.img must be pulled from a working device.
    • How to pull a mmcblk0.img or Loader.img

Links about flashing a Blank Flash


Building a Blankflash
https://forum.xda-developers.com/moto-g7/how-to/blankflash-moto-g7-xt1962-5-river-reteu-t4020263

Booting to EDL Mode
If you can boot a custom recovery like TWRP
see reboot options for EDL
or use
Code:
adb reboot edl




The following doesn't appear to work with Moto Devices


[SIZE=+3][INDEX]Motorola Unbricking Tools[/SIZE]
[SIZE=+2]Only For Motorola Devices[/SIZE]

[SIZE=+1]This a list of USB/Fastboot Drivers, Firmware, Flashing Utilities, and other Unbricking Dev Projects for Motorola Devices.​
Please only post in this thread with feedback on how to improve this document.​
Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own.​
Do not use this as a general help thread.[/SIZE]​


*​
Forum Rules | New Users Guide | XDA Tour | Report Posts

Please look for a similar thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.

A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP


My "G8 Plus XT2019-2 retbr" can't start (only fastboot mode), does not boot/recovery mode.

I don't know what else to try... could you help me, please ?


https://forum.xda-developers.com/t/...-retbr-cant-start-only-fastboot-mode.4208715/
 

janvantonder

Senior Member
Aug 17, 2007
55
10
Good Evening!

I messed up the baseband on my Motorola x4 (XT1900-7) while attempting to install a custom ROM. The phone was on Android 7.1.1 and I cannot find the firmware for this model.

Can anyone point me to this firmware?

Here is a bootloader Pic from before I made any changes.


Screenshot from 2021-01-20 22-22-54.png
 

sd_shadow

Recognized Contributor
Sep 21, 2011
17,897
1
8,446
South Dakota
goo.gl
Motorola Droid X
Moto X4
Last edited:

janvantonder

Senior Member
Aug 17, 2007
55
10
Good Evening!

I messed up the baseband on my Motorola x4 (XT1900-7) while attempting to install a custom ROM. The phone was on Android 7.1.1 and I cannot find the firmware for this model.

Can anyone point me to this firmware?

Here is a bootloader Pic from before I made any changes.


View attachment 5193877
 

janvantonder

Senior Member
Aug 17, 2007
55
10
Good Morning!

$ fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(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: SDM630 1.0 (6)
(bootloader) serialno: ZY224KGFPP
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 31E01D35
(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: 356516081212750
(bootloader) meid:
(bootloader) date: 10-21-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4144
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:pmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:prov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 2
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.046s

The problem is that I should have updated to Oreo before installing the custom ROM. I've tried flashing 11 different stock ROMs from Lolinet but the best result I got was from:

XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

After flashing this the phone shows a baseband version, however WLAN still does not work.

My guess is that my best hope is to flash stock Android 7.1.1 for the XT1900-7, however I cannot find such a ROM version anywhere.

So if anyone can help....

The ROM I'm looking for is probably in here somewhere:


Unfortunately it's not possible to list the contents of this directory.
 
Good Morning!

$ fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(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: SDM630 1.0 (6)
(bootloader) serialno: ZY224KGFPP
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 31E01D35
(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: 356516081212750
(bootloader) meid:
(bootloader) date: 10-21-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4144
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:pmic: MBM-3.0-payton_retail-fe5d8a9-190829
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-190829
(bootloader) git:tz: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:hyp: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:devcfg: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:keymaster: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:prov: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) git:storsec: MBM-3.0-payton_retail-3ea0392-190829
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 2
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.046s

The problem is that I should have updated to Oreo before installing the custom ROM. I've tried flashing 11 different stock ROMs from Lolinet but the best result I got was from:

XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

After flashing this the phone shows a baseband version, however WLAN still does not work.

My guess is that my best hope is to flash stock Android 7.1.1 for the XT1900-7, however I cannot find such a ROM version anywhere.

So if anyone can help....

The ROM I'm looking for is probably in here somewhere:


Unfortunately it's not possible to list the contents of this directory.


flash at your own risk!
 

janvantonder

Senior Member
Aug 17, 2007
55
10
Hello again

I flashed quite a few stock firmwares and the only one showing results is the latest one:

PAYTON_RETAIL_9.0_PPWS29.69-40-3-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

My phone now shows a baseband version, the SIM is recognized and WLAN works -

However my IMEI is 0

fastboot getvar imei shows the correct IMEI.

Does anyone have suggestions here?

Thanks!
 

sd_shadow

Recognized Contributor
Sep 21, 2011
17,897
1
8,446
South Dakota
goo.gl
Motorola Droid X
Moto X4
Motorola Options for booting into EDL Mode and using a Blankflash

A blankflash can be used to repair a Motorola device
If the bootloader will no longer allow the firmware to be flashed.
To use a Blankflash the device must be in Emergency Download Mode.

Normally, Motos cannot be forced in to EDL Mode if the bootloader is OEM_Locked
However if the bootloader was unlocked, and now says
Code:
securestate: oem_locked
But the command to relock the bootloader was not made, and is
a result of a failed flashing of a custom rom, rooting or similar action
One of the methods below may allow the device to be recovered.

A blankflash file will also be needed,
which one will depend on the device model, and current firmware version
There are some posted on

Option 1
Code:
fastboot oem blankflash
If that works phone screen will go black, with no text. (if it didn't see Twrp Method)
If it does see
Is my device in EDL Mode?
If the drivers are good,
download the blankflash, unzip it and
run the blank-flash.bat
If the blankflash works, the device will reboot, you may need to reflash firmware with fastboot.


Option 2
if it didn't enter EDL Mode see if you can boot Twrp
Code:
fastboot boot twrp-3.5.2_9-0-potter.img
If twrp boots use
Code:
adb reboot edl
If that works, and the device is now in EDL Mode use the blankflash .bat
 
Last edited:

Erbid

Member
Dec 24, 2007
45
2
Moto G7 Power
I can't vouch for the source but I went through a similar search for my stock images before I started to flash my phone.
you might try motostockrom.com/motorola-moto-x4-xt1900-7 which had two links for RETEU version.

Be sure to look for RETEU if that is what you need (other versions are also listed).

Erbid
 

syndicate3333

Member
Apr 3, 2021
7
0
Cannot with a locked bootloader.
With the bootloader unlocked, just flash the firmware with fastboot.exe

Many thanks for your swift reply. I've just unlocked bootloader and flashed stock fw via "moto flash pro". Afterwards I checked the sw channel via fastboot getvar all and it still shows timit...
Do I need to flash manually step by step as listed in the file of stock fw?
<?xml version="1.0" ?>
<flashing>
<header>
<phone_model model="racer_retail"/>
<software_version version="racer_retail-user 10 QPDS30.114-80-4 2c9ffb release-keys"/>
<subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
<regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png"/>
<sparsing enabled="true" max-sparse-size="536870912"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="433865908ece7028a17b6068f12e3667" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="6ba51fb1763190317d789aa154e0c977" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="4efd8cb280fddae65298e69c0f02ec67" filename="vbmeta.img" operation="flash" partition="vbmeta"/>
<step MD5="5913d10e54c5f14e72c264f11d9c9a96" filename="radio.img" operation="flash" partition="radio"/>
<step MD5="ae59cf09fe4edd58864a3f29d7da61ed" filename="BTFM.bin" operation="flash" partition="bluetooth"/>
<step MD5="35303058ff0a1ce10625345a910626da" filename="dspso.bin" operation="flash" partition="dsp"/>
<step MD5="29e26baf8b0ec78c611f88eb36e217fe" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="ca1129419495a682b2d26356187d59f5" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="5b566bd40d66c5d5e9c56fe1d170f638" filename="dtbo.img" operation="flash" partition="dtbo"/>
<step MD5="3526a150f1903c1f30871e557b4c671f" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="651591a09edaab5924f0492cbb088267" filename="super.img_sparsechunk.0" operation="flash" partition="super"/>
<step MD5="90c3ad6fdc0fa2809bf3816e3ceb88ae" filename="super.img_sparsechunk.1" operation="flash" partition="super"/>
<step MD5="76a880803d88838de861d27a5c87761d" filename="super.img_sparsechunk.2" operation="flash" partition="super"/>
<step MD5="158b65e393378b6465173912d00cf6cb" filename="super.img_sparsechunk.3" operation="flash" partition="super"/>
<step MD5="4ca903d17124a298dd51e6bff15cade2" filename="super.img_sparsechunk.4" operation="flash" partition="super"/>
<step MD5="dc8c1fc8421f2f9f12bf633e0c359ce3" filename="super.img_sparsechunk.5" operation="flash" partition="super"/>
<step MD5="c9f3ed6b8b5d0f280c9ea241a3e87940" filename="super.img_sparsechunk.6" operation="flash" partition="super"/>
<step MD5="874f34c6cdad9ec64ddbf0f8deaf7eb7" filename="super.img_sparsechunk.7" operation="flash" partition="super"/>
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="metadata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
 

sd_shadow

Recognized Contributor
Sep 21, 2011
17,897
1
8,446
South Dakota
goo.gl
Motorola Droid X
Moto X4
GSI on Motorola Devices




Threads

Posts
 
Last edited:

syndicate3333

Member
Apr 3, 2021
7
0
I've been using the online flashfile converter, there's a link in my
I did it again via fastboot (step by step) and software channel hasn't changed. Could you successfully change the software channel? Btw I own the Motorola Edge. Thx again.
 

nabofox

Member
May 8, 2021
16
0
Moto G5 Plus
Help needed! (newbie here)

I have a moto g5 plus (potter) and it is locked on this screen. I already tried to use the motorola recovery program but he doesn't recognize it because imei appears 0000000. I need help to bring it back to life (my computer is linux) and if possible to install the factory rom on it.
WhatsApp Image 2021-05-24 at 13.56.41.jpeg
WhatsApp Image 2021-05-24 at 13.56.37.jpeg
WhatsApp Image 2021-05-24 at 13.56.36.jpeg
 

nabofox

Member
May 8, 2021
16
0
Moto G5 Plus
[Fixing] Baseband <not found> / IMEI=0 / No Network After Flash / Issues

Lots of Moto threads lately with
Baseband not found
No Baseband
IMEI=0
No Network
No Data after Flash
no wifi

One solution that seems to work is
Reflashing last known Firmware that worked.

If still not working try.

Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

also see these threads, for possible solutions.
hello, i'm trying to recover the imei of my Moto G5+, it shows 0 but in the first step you posted, it shows up

< waiting for device >

and stays like this forever
 

Top Liked Posts