[HELP]Blank Flash For Moto G7 Power

sd_shadow

Recognized Contributor
Sep 21, 2011
16,628
7,539
253
South Dakota
goo.gl
Hey, i know i'm a bit late to the thread, but what exactly did you do to unbrick your Moto? Mine keeps getting stuck at waiting for firehose to get ready. Even though i have a Moto g7 Power XT1955-4. I'm so confused.
You have a xt1955-4 , I haven't seen anyone other than you post that they tried the blankflash.
It's possible that it's not compatible.
The XT1955-5 is single sim, and I believe the XT-1955-4 is dual SIM, and possible other hardware differences.


Sent from my mata using XDA Labs
 
G

GuestD2221

Guest
You have a xt1955-4 , I haven't seen anyone other than you post that they tried the blankflash.
It's possible that it's not compatible.
The XT1955-5 is single sim, and I believe the XT-1955-4 is dual SIM, and possible other hardware differences.
Yeah you're probably right. Looks like i might be screwed in that case. Regardless thanks for the help.
 

gigawatt

Senior Member
Nov 19, 2008
141
16
0
Hi, I have a moto g7 power xt1955-5 I got from metro. I got them all unlocked and they also did the imei repair. On all but one of them, after the unlock and repair I could flash the stock rom and get the retla1st channel. However on one of them I can't. Does somebody have a blank flash that will flash the proper boot or bootloader to allow this or a complete backup I can use to make this possible to flash other stock roms. P.S. On all of the other phones I did the bootloader was locked. Thanks in advance.
 

WetWilly

Senior Member
Apr 26, 2007
65
25
0
Yeah you're probably right. Looks like i might be screwed in that case. Regardless thanks for the help.
Checking in a bit late, but the blankflash should have theoretically worked. Based on what you said, it looks like it is hanging at the point where the programmer is identifying the CPU; it takes about 3 seconds after the "Waiting for firehose to get ready" message for the CPU version ("MSM8953 1.0") to show up and the blankflash to continue. That points to either the programmer.mbn not being compatible with the XT1955-4 variant or that tweaks need to be made to files in the blankflash (e.g., xml edits and/or replacing .bin files with files for that specific variant).

Check the qboot log and after the "qboot version x.xx" line there's a DEVICE { section; confirm in that section that the cpu.id is 186 and the CPU.name is "MSM8953". If the CPU detection is correct then the blankflash probably needs to be tweaked.
 

flash713

Senior Member
May 7, 2015
843
425
93
Houston, Texas
Checking in a bit late, but the blankflash should have theoretically worked. Based on what you said, it looks like it is hanging at the point where the programmer is identifying the CPU; it takes about 3 seconds after the "Waiting for firehose to get ready" message for the CPU version ("MSM8953 1.0") to show up and the blankflash to continue. That points to either the programmer.mbn not being compatible with the XT1955-4 variant or that tweaks need to be made to files in the blankflash (e.g., xml edits and/or replacing .bin files with files for that specific variant).

Check the qboot log and after the "qboot version x.xx" line there's a DEVICE { section; confirm in that section that the cpu.id is 186 and the CPU.name is "MSM8953". If the CPU detection is correct then the blankflash probably needs to be tweaked.

I have the metro moto g7 power and ive tried the blankflash 10 times or more and mine hangs on exactly the same part as the person w/ the xt1955-4 .. :confused: I may give the sdcard boot a shot and see if that will work. Hate to use my samsung 128 gb ultra card for it but i have two so wth. lol.

when i bricked some months ago i was using one of the 1st test twrp that came out and i rebooted recovery i believe and that was it. no more nothing..
 

flash713

Senior Member
May 7, 2015
843
425
93
Houston, Texas
You changed the block size to bs=1000000000 ?
like
Code:
sudo dd bs=1000000000 if=mmcblk0.img of=/dev/sdb status=progress oflag=sync


---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------

and rename XT1955.5.mmcblk0.img to mmcblk0.img
or change code like
Code:
sudo dd bs=1000000000 if=XT1955.5.mmcblk0.img of=/dev/sdb status=progress oflag=sync
Just to be clear do I need to do the block size change after following the tutorial or at step #1 ? I'm about to give this a shot and going to just use one of my Samsung ultra 128 gb sdcards. Just want to make 100% sure when to change the block size. I sure appreciate you uploading the mmcblk.img for the xt1955-5!!
 

sd_shadow

Recognized Contributor
Sep 21, 2011
16,628
7,539
253
South Dakota
goo.gl
You changed the block size to bs=1000000000 ?
like


---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------

and rename XT1955.5.mmcblk0.img to mmcblk0.img
or change code like


Just to be clear do I need to do the block size change after following the tutorial or at step #1 ? I'm about to give this a shot and going to just use one of my Samsung ultra 128 gb sdcards. Just want to make 100% sure when to change the block size. I sure appreciate you uploading the mmcblk.img for the xt1955-5!!
You shouldn't need the mmcblk0.img there is a blankflash

Sent from my ocean using XDA Labs
 

flash713

Senior Member
May 7, 2015
843
425
93
Houston, Texas
You shouldn't need the mmcblk0.img there is a blankflash
I've tried the blankflash 12-15 times and doesn't work. I have metro g7 power.. I'll try it again and post the log in 20-30 minutes of exactly what it says when I hold buttons down and get it going..

---------- Post added at 04:46 PM ---------- Previous post was at 04:06 PM ----------

You shouldn't need the mmcblk0.img there is a blankflash

Sent from my ocean using XDA Labs
Here's my log: https://mega.nz/#!cI92gSpZ!IPozK644Kt6swHRxuLgs098bEKtj0NBvhpe8EOqULWs
and
Here's what terminal said:
[email protected]:~/Downloads/blankflash_ocean_PDOS29.114-134-2$ sudo ./blank-flash.sh
[sudo] password for flash713:
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.004] ...cpu.id = 186 (0xba)
[ 0.004] ...cpu.sn = 839264944 (0x32062ab0)
[ 0.004] Opening singleimage
[ 0.128] Loading package
[ 0.132] ...filename = singleimage.pkg.xml
[ 0.134] Loading programmer
[ 0.146] ...filename = programmer.mbn
[ 0.146] Sending programmer
[ 0.441] Handling things over to programmer
[ 0.441] Identifying CPU version
[ 0.446] Waiting for firehose to get ready
[ 3.446] serial_write(), line 280: Input/output error
[ 61.526] Waiting for firehose to get ready
[ 64.526] serial_write(), line 280: Input/output error
[124.246] ...MSM8953 unknown
[124.246] Determining target secure state
[124.249] Waiting for firehose to get ready
[127.250] serial_write(), line 280: Input/output error
[186.976] ...secure = no
[187.026] Initializing storage
[187.031] Waiting for firehose to get ready
[190.031] serial_write(), line 280: Input/output error
[249.682] Configuring device...
[249.688] Waiting for firehose to get ready
[252.688] serial_write(), line 280: Input/output error
[312.325] Waiting for firehose to get ready
[315.325] serial_write(), line 280: Input/output error
[375.043] Waiting for firehose to get ready
[378.043] serial_write(), line 280: Input/output error
[444.310] Waiting for firehose to get ready
[447.311] serial_write(), line 280: Input/output error
[506.838] Initializing storage
[506.847] Waiting for firehose to get ready
[509.847] serial_write(), line 280: Input/output error
[569.473] Configuring device...
[569.479] Waiting for firehose to get ready
[572.479] serial_write(), line 280: Input/output error
[632.136] Waiting for firehose to get ready
[635.137] serial_write(), line 280: Input/output error
[694.786] Waiting for firehose to get ready
[697.786] serial_write(), line 280: Input/output error
[757.454] Waiting for firehose to get ready
[760.454] serial_write(), line 280: Input/output error
[827.391] Waiting for firehose to get ready
[830.391] serial_write(), line 280: Input/output error
[888.992] Configuring device...
[888.996] Waiting for firehose to get ready
[891.996] serial_write(), line 280: Input/output error
[963.564] Waiting for firehose to get ready
[966.564] serial_write(), line 280: Input/output error
[1024.846] Waiting for firehose to get ready
[1027.847] serial_write(), line 280: Input/output error
[1086.458] Waiting for firehose to get ready
[1089.458] serial_write(), line 280: Input/output error
[1147.794] ERROR: do_package()->do_recipe()->do_configure()->device_open()->error opening device
[1147.795] Check qboot_log.txt for more details
[1147.795] Total time: 1147.794s
[1147.795] There were some hiccups in backup and restore.
[1147.795] Please save the following files and see a Bootloader member.
[1147.795] 1) ./qboot_log.txt
[1147.795] 2) ./backup_0x32062AB0_2020-01-01_161852.img
[1147.795]
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->device_open()->error opening device
[email protected]:~/Downloads/blankflash_ocean_PDOS29.114-134-2$ sudo ./blank-flash.sh

(Edit, added below)

I found a good read on what may be the issue for me. I googled the FAILED qb_flash_singleimage...at the bottom just above where I'm typing this. Here's what it shows: https://www.androidpit.com.br/forum/750136/recuperar-bootloader-via-blanck-flash
 
Last edited:

KUSANAGUI

Senior Member
Jul 10, 2019
128
49
38
24
Lima
Update:
I finally got around to Unlocking the bootloader, and rooting.
The Terminal Emulator method wasn't working for me.
I flashed the new TWRP
[PORT] Unofficial TWRP for G7 Power by Geofferey
and used the steps in this thread
[GUIDE] How to create 'mmcblk0.img' from a working device? by kalyansundhar
and used
Code:
dd if=/dev/block/mmcblk0 of=/external_sd/XT1955.5.mmcblk0.img bs=1000000000 count=30
The mmcblk0.img is almost 30gb, I'm compressing it, and uploading now may take awhile.

Old Post

I believe if someone with a rooted Moto G7 can pull a copy of the mmcblk0.img from their device with
Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en

using these commands
Code:
su
GRANT Terminal emulator a Root Access
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
How to Unbrick (Debrick) Qualcomm Android Devices Using your SD Card
https://www.aryk.store/2019/09/unbrick-qualcomm-android-using-sd-card.html
and
[GUIDE] How to create 'mmcblk0.img' from a working device? by kalyansundhar


That mmcblk0.img can be used to boot the non-working G7 into Fastboot mode, as described in the links below
and then you just need to reflash the firmware.

[Guide] [Unbrick] How to revive a hard bricked Moto G5 by TheFixItMan
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012

https://android.stackexchange.com/questions/125135/how-to-pull-mmcblk0-to-a-windows-pc

Edit:
you managed to raise the mmcblk0.img of the g7 power ?
 

KUSANAGUI

Senior Member
Jul 10, 2019
128
49
38
24
Lima
You have a xt1955-4 , I haven't seen anyone other than you post that they tried the blankflash.
It's possible that it's not compatible.
The XT1955-5 is single sim, and I believe the XT-1955-4 is dual SIM, and possible other hardware differences.


Sent from my mata using XDA Labs
I first installed the Qualcomm HS-USB QDLoader 9008 drivers
but they don't appear after restarting the pc,
in device manager /ports does not appear: qualcomm hs-usb qdloader 9008!!!
please help me T.T
 

sd_shadow

Recognized Contributor
Sep 21, 2011
16,628
7,539
253
South Dakota
goo.gl
you managed to raise the mmcblk0.img of the g7 power ?
I made a couple of mmcblk0.img s but to my knowledge no one as got them to work.

Sent from my jerry_cheets using XDA Labs

---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------

I first installed the Qualcomm HS-USB QDLoader 9008 drivers
but they don't appear after restarting the pc,
in device manager /ports does not appear: qualcomm hs-usb qdloader 9008!!!
please help me T.T
What is it listed as?


Sent from my jerry_cheets using XDA Labs
 

KUSANAGUI

Senior Member
Jul 10, 2019
128
49
38
24
Lima
help

I made a couple of mmcblk0.img s but to my knowledge no one as got them to work.

Sent from my jerry_cheets using XDA Labs

---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------

What is it listed as?


Sent from my jerry_cheets using XDA Labs
it only appears in windows 10 x64, that the usb device is not recognized and appears in the device manager, in universal serial bus controllers: Unknown USB device (device descriptor request error).
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone