Need Latest September/October BlankFlash

Search This thread

veejay97

Member
Nov 12, 2014
9
0
Hyderabad
Please help, i think i have September security patch and tried to install via otg and my moto g4 plus is bricked.

[ -0.000] Opening device: \\.\COM4
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 2418 (0x972)
[ 0.007] ...cpu.sn = 29673406 (0x1c4c7be)
[ 0.007] Opening singleimage
[ 0.007] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.017] Loading programmer
[ 0.018] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.243] Handling things over to programmer
[ 0.245] Identifying CPU version
[ 0.250] Waiting for firehose to get ready
[ 60.639] Waiting for firehose to get ready
[120.793] ...MSM8952 unknown
[120.794] Determining target secure state
[120.804] Waiting for firehose to get ready
[180.968] ...secure = no
[181.001] Flashing GPT...
[181.002] Flashing partition:0 with gpt_main0.bin
[181.002] Initializing storage
[181.008] Waiting for firehose to get ready
[241.159] Configuring device...
[241.167] Waiting for firehose to get ready
[301.312] Waiting for firehose to get ready
[361.460] Waiting for firehose to get ready
[421.619] Waiting for firehose to get ready
[481.766] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[481.770] Check qboot_log.txt for more details
[481.774] Total time: 481.780s
[481.776]
[481.776] qboot version 3.40
[481.776]
[481.776] DEVICE {
[481.776] name = "\\.\COM4",
[481.776] flags = "0x64",
[481.776] addr = "0x61FE5C",
[481.776] sahara.current_mode = "0",
[481.776] api.buffer = "0x2EF2020",
[481.776] cpu.serial = "29673406",
[481.776] cpu.id = "2418",
[481.776] cpu.sv_sbl = "0",
[481.776] cpu.name = "MSM8952",
[481.776] storage.type = "eMMC",
[481.776] sahara.programmer = "programmer.mbn",
[481.776] module.firehose = "0x30ED0C0",
[481.776] cpu.ver = "0",
[481.776] cpu.vername = "unknown",
[481.776] api.bnr = "0x26F55C0",
[481.776] }
[481.776]
[481.776]
[481.776] Backup & Restore {
[481.776] num_entries = 0,
[481.776] restoring = "false",
[481.776] backup_error = "not started",
[481.776] restore_error = "not started",
[481.776] }
[481.776]
 

Amberdawn

Member
Nov 5, 2017
9
0
Please help, i think i have September security patch and tried to install via otg and my moto g4 plus is bricked.

[ -0.000] Opening device: \\.\COM4
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 2418 (0x972)
[ 0.007] ...cpu.sn = 29673406 (0x1c4c7be)
[ 0.007] Opening singleimage
[ 0.007] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.017] Loading programmer
[ 0.018] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.243] Handling things over to programmer
[ 0.245] Identifying CPU version
[ 0.250] Waiting for firehose to get ready
[ 60.639] Waiting for firehose to get ready
[120.793] ...MSM8952 unknown
[120.794] Determining target secure state
[120.804] Waiting for firehose to get ready
[180.968] ...secure = no
[181.001] Flashing GPT...
[181.002] Flashing partition:0 with gpt_main0.bin
[181.002] Initializing storage
[181.008] Waiting for firehose to get ready
[241.159] Configuring device...
[241.167] Waiting for firehose to get ready
[301.312] Waiting for firehose to get ready
[361.460] Waiting for firehose to get ready
[421.619] Waiting for firehose to get ready
[481.766] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[481.770] Check qboot_log.txt for more details
[481.774] Total time: 481.780s
[481.776]
[481.776] qboot version 3.40
[481.776]
[481.776] DEVICE {
[481.776] name = "\\.\COM4",
[481.776] flags = "0x64",
[481.776] addr = "0x61FE5C",
[481.776] sahara.current_mode = "0",
[481.776] api.buffer = "0x2EF2020",
[481.776] cpu.serial = "29673406",
[481.776] cpu.id = "2418",
[481.776] cpu.sv_sbl = "0",
[481.776] cpu.name = "MSM8952",
[481.776] storage.type = "eMMC",
[481.776] sahara.programmer = "programmer.mbn",
[481.776] module.firehose = "0x30ED0C0",
[481.776] cpu.ver = "0",
[481.776] cpu.vername = "unknown",
[481.776] api.bnr = "0x26F55C0",
[481.776] }
[481.776]
[481.776]
[481.776] Backup & Restore {
[481.776] num_entries = 0,
[481.776] restoring = "false",
[481.776] backup_error = "not started",
[481.776] restore_error = "not started",
[481.776] }
[481.776]

I am getting exactly the same message when executing the blankflash file from August the 21st on a Motorola G4 Plus that had been bricked a week ago during an update.

siddhesh9146 said:

I have tried the quoted link and also the following one without success:

https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

Do I need a newer blankflash file?
Thanks in advance
 

Outfield303

Senior Member
Nov 6, 2016
286
220
I have tried the quoted link and also the following one without success:

https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

Thanks in advance

this link that you gave is trash, those are very old files which won't work at all
first delete all the files you have downloaded, all zips and all extracted files too
make sure nothing is there, clean your downloaded folder or IDM if you use it:rolleyes:
then download fresh blankflash from here : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
trust me, it will work, you are mixing the older and newer blankflash files
and then report me back!
 
  • Like
Reactions: flash713

Amberdawn

Member
Nov 5, 2017
9
0
this link that you gave is trash, those are very old files which won't work at all
first delete all the files you have downloaded, all zips and all extracted files too
make sure nothing is there, clean your downloaded folder or IDM if you use it:rolleyes:
then download fresh blankflash from here : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
trust me, it will work, you are mixing the older and newer blankflash files
and then report me back!

I was mixing newer and older files in a folder but I have tried deleting all the files, downloading and using fresh blankflash files from the link you quoted with no success.
I have cleaned the download folder and I have left only the fresh blankflash folder.

I am obtaining the following:

Code:
[  0.001] Opening device: \\.\COM3
[  0.002] Detecting device
[  0.003] ...cpu.id  = 2418 (0x972)
[  0.003] ...cpu.sn  = 30778144 (0x1d5a320)
[  0.003] Opening singleimage
[  0.004] Loading package
[  0.006] ...filename = singleimage.pkg.xml
[  0.007] Loading programmer
[  0.008] ...filename = programmer.mbn
[  0.008] Sending programmer
[  0.227] Handling things over to programmer
[  0.228] Identifying CPU version
[  0.230] Waiting for firehose to get ready
[ 60.472] Waiting for firehose to get ready
[123.536] ...MSM8952 unknown
[123.536] Determining target secure state
[123.541] Waiting for firehose to get ready
[184.100] ...secure = no
[184.133] Flashing GPT...
[184.134] Flashing partition:0 with gpt_main0.bin
[184.135] Initializing storage
[184.145] Waiting for firehose to get ready
[245.666] Configuring device...
[245.670] Waiting for firehose to get ready
[307.737] Waiting for firehose to get ready
[370.305] Waiting for firehose to get ready
[430.370] Waiting for firehose to get ready
[491.434] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[491.434] Check qboot_log.txt for more details
[491.437] Total time: 491.438s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error

Any advice?
 

Outfield303

Senior Member
Nov 6, 2016
286
220
I was mixing newer and older files in a folder but I have tried deleting all the files, downloading and using fresh blankflash files from the link you quoted with no success.
I have cleaned the download folder and I have left only the fresh blankflash folder.

I am obtaining the following:

Code:
[  0.001] Opening device: \\.\COM3
[  0.002] Detecting device
[  0.003] ...cpu.id  = 2418 (0x972)
[  0.003] ...cpu.sn  = 30778144 (0x1d5a320)
[  0.003] Opening singleimage
[  0.004] Loading package
[  0.006] ...filename = singleimage.pkg.xml
[  0.007] Loading programmer
[  0.008] ...filename = programmer.mbn
[  0.008] Sending programmer
[  0.227] Handling things over to programmer
[  0.228] Identifying CPU version
[  0.230] Waiting for firehose to get ready
[ 60.472] Waiting for firehose to get ready
[123.536] ...MSM8952 unknown
[123.536] Determining target secure state
[123.541] Waiting for firehose to get ready
[184.100] ...secure = no
[184.133] Flashing GPT...
[184.134] Flashing partition:0 with gpt_main0.bin
[184.135] Initializing storage
[184.145] Waiting for firehose to get ready
[245.666] Configuring device...
[245.670] Waiting for firehose to get ready
[307.737] Waiting for firehose to get ready
[370.305] Waiting for firehose to get ready
[430.370] Waiting for firehose to get ready
[491.434] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[491.434] Check qboot_log.txt for more details
[491.437] Total time: 491.438s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error

Any advice?

can you tell me when your device was bricked? I mean on which update? and also tell me the android version and security patch before bricking your phone
 

Amberdawn

Member
Nov 5, 2017
9
0
can you tell me when your device was bricked? I mean on which update? and also tell me the android version and security patch before bricking your phone

First of all, it's not my device so I don't have all the answers...

The device was bricked a week ago. First, it got stuck in the booting process, exactly when Motorola logo appears. It remained for hours so a reboot into fastboot mode was performed. Then, the database had been wiped. After that, the phone started rebooting normally, it started updating and it got stuck again for 2h. As a result of this, the mobile was switched off and as a consecuence was bricked.

The device had stock Android 7 but I don't know the exact version as the owner doesn't know. I can confirm that it definitively had the security patch from September.

Hope you find this information useful
 

Amberdawn

Member
Nov 5, 2017
9
0
First of all, it's not my device so I don't have all the answers...

The device was bricked a week ago. First, it got stuck in the booting process, exactly when Motorola logo appears. It remained for hours so a reboot into fastboot mode was performed. Then, the database had been wiped. After that, the phone started rebooting normally, it started updating and it got stuck again for 2h. As a result of this, the mobile was switched off and as a consecuence was bricked.

The device had stock Android 7 but I don't know the exact version as the owner doesn't know. I can confirm that it definitively had the security patch from September.

Hope you find this information useful

Any suggestion? Any idea of what is happening with the device?
Regards
 

echo92

Senior Member
Jan 1, 2017
3,732
1,989
Plymouth
Hi,
Still having problems while executing the blankflash file, can't figure out what could be the problem. Any idea/suggestion?
Thanks in advance.

What problems are you having with the blankflash, are they the same as previously or different?

Can you confirm with the owner they are using the latest blankflash still (as provided here): https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

You may wish to also confirm they've tried the tips below: (from https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 )
Follow the below steps.
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.
If this doesn't work, then we might have to start considering a service repair - does the owner know if their device is still under warranty?
 
  • Like
Reactions: Amberdawn

Amberdawn

Member
Nov 5, 2017
9
0
What problems are you having with the blankflash, are they the same as previously or different?

Can you confirm with the owner they are using the latest blankflash still (as provided here): https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

The problems I am having are the same as previously. I can confirm that I am using the blankflash still as provided in the link you quoted.

I'm going to post again what I'm obtaining after executing the blankflash

Code:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[  0.001] Detecting device
[  0.002] ...cpu.id  = 2418 (0x972)
[  0.003] ...cpu.sn  = 30778144 (0x1d5a320)
[  0.003] Opening singleimage
[  0.003] Loading package
[  0.005] ...filename = singleimage.pkg.xml
[  0.006] Loading programmer
[  0.007] ...filename = programmer.mbn
[  0.007] Sending programmer
[  0.230] Handling things over to programmer
[  0.231] Identifying CPU version
[  0.237] Waiting for firehose to get ready
[ 63.482] Waiting for firehose to get ready
[127.045] ...MSM8952 unknown
[127.046] Determining target secure state
[127.052] Waiting for firehose to get ready
[188.612] ...secure = no
[188.624] Flashing GPT...
[188.625] Flashing partition:0 with gpt_main0.bin
[188.625] Initializing storage
[188.629] Waiting for firehose to get ready
[252.178] Configuring device...
[252.184] Waiting for firehose to get ready
[312.752] Waiting for firehose to get ready
[373.317] Waiting for firehose to get ready
[436.386] Waiting for firehose to get ready
[497.451] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[497.452] Check qboot_log.txt for more details
[497.455] Total time: 497.457s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error

Log from qboot_log.txt file:

Code:
[ -0.000] Opening device: \\.\COM3
[  0.001] Detecting device
[  0.002] ...cpu.id  = 2418 (0x972)
[  0.003] ...cpu.sn  = 30778144 (0x1d5a320)
[  0.003] Opening singleimage
[  0.003] Loading package
[  0.005] ...filename = singleimage.pkg.xml
[  0.006] Loading programmer
[  0.007] ...filename = programmer.mbn
[  0.007] Sending programmer
[  0.230] Handling things over to programmer
[  0.231] Identifying CPU version
[  0.237] Waiting for firehose to get ready
[ 63.482] Waiting for firehose to get ready
[127.045] ...MSM8952 unknown
[127.046] Determining target secure state
[127.052] Waiting for firehose to get ready
[188.612] ...secure = no
[188.624] Flashing GPT...
[188.625] Flashing partition:0 with gpt_main0.bin
[188.625] Initializing storage
[188.629] Waiting for firehose to get ready
[252.178] Configuring device...
[252.184] Waiting for firehose to get ready
[312.752] Waiting for firehose to get ready
[373.317] Waiting for firehose to get ready
[436.386] Waiting for firehose to get ready
[497.451] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[497.452] Check qboot_log.txt for more details
[497.455] Total time: 497.457s
[497.456] 
[497.456] qboot version 3.40
[497.456] 
[497.456] DEVICE {
[497.456]   name  = "\\.\COM3",
[497.456]   flags = "0x64",
[497.456]   addr  = "0x61FE5C",
[497.456]   sahara.current_mode = "0",
[497.456]   api.buffer = "0x2F01020",
[497.456]   cpu.serial = "30778144",
[497.456]   cpu.id = "2418",
[497.456]   cpu.sv_sbl = "0",
[497.456]   cpu.name = "MSM8952",
[497.456]   storage.type = "eMMC",
[497.456]   sahara.programmer = "programmer.mbn",
[497.457]   module.firehose = "0x3088C78",
[497.457]   cpu.ver = "0",
[497.457]   cpu.vername = "unknown",
[497.457]   api.bnr = "0x2746888",
[497.457] }
[497.457] 
[497.457] 
[497.457] Backup & Restore {
[497.457]   num_entries = 0,
[497.457]   restoring = "false",
[497.457]   backup_error = "not started",
[497.457]   restore_error = "not started",
[497.457] }
[497.457]

You may wish to also confirm they've tried the tips below: (from https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 )

If this doesn't work, then we might have to start considering a service repair - does the owner know if their device is still under warranty?

I can also confirm that I have tried following the steps from that post. It's true that sometimes I need to follow these tips in order for blankflash to start executing.

However, the blankflash process doesn't work properly.

I think that the device is still under warranty. I have realised that more and more people are reporting the same problem.
 

abhi212b

Senior Member
Feb 16, 2016
552
161
Noida
www.youtube.com
Bro... 1st of all.. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

This is the one u need to follow! But, DO NOT USE THE BOOTLOADER AND GPT OF THE ROM WITH BUILD NUMBER 14-8...YOU SHOULD DOWNLOAD LATEST ROM.. i.e., ending with build number 14-10...extract it and then use the bootloader and GPT files from this..
The only reason you are stuck on this is because you have not updated your usb moto drivers... Uninstall what you have, download them again.. Remember, download them again and then install and then use blankflash.. I have used it twice.. Once to unbrick my phone and another to make a youtube video!
Just in case you need to see what and how to do my video link is https://youtu.be/m2NqpY6X-X4
Hope this helps! Good luck! :D
 
  • Like
Reactions: 6ixf6ix

Amberdawn

Member
Nov 5, 2017
9
0
Bro... 1st of all.. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

This is the one u need to follow! But, DO NOT USE THE BOOTLOADER AND GPT OF THE ROM WITH BUILD NUMBER 14-8...YOU SHOULD DOWNLOAD LATEST ROM.. i.e., ending with build number 14-10...extract it and then use the bootloader and GPT files from this..
The only reason you are stuck on this is because you have not updated your usb moto drivers... Uninstall what you have, download them again.. Remember, download them again and then install and then use blankflash.. I have used it twice.. Once to unbrick my phone and another to make a youtube video!
Just in case you need to see what and how to do my video link is https://youtu.be/m2NqpY6X-X4
Hope this helps! Good luck! :D

Hi abhi212b! I have tried following your video but again, I got stuck in the "waiting for firehose to get ready" step.

siddhesh9146 said:
I guess someone from motorola need to leak another blankflash...

Are you sure? I'm starting to think the same but then I see people who have succeeded unbricking their devices...

Is the device's hardware damaged?

Your help is much appreciated
 

abhi212b

Senior Member
Feb 16, 2016
552
161
Noida
www.youtube.com
Hi abhi212b! I have tried following your video but again, I got stuck in the "waiting for firehose to get ready" step.



Are you sure? I'm starting to think the same but then I see people who have succeeded unbricking their devices...

Is the device's hardware damaged?

Your help is much appreciated

Did you update the drivers?? it should work.. i was stuck on waiting for firehose for like 2 hours, and after i updated the drivers, the procedure got through in 1st attempt..
 

Amberdawn

Member
Nov 5, 2017
9
0
Did you update the drivers?? it should work.. i was stuck on waiting for firehose for like 2 hours, and after i updated the drivers, the procedure got through in 1st attempt..

Yes, I did! I uninstalled the Motorola Drivers and then reinstalled the ones linked in your video. I also reinstalled the Qualcomm drivers
 

Bhavik kaila

Member
Aug 10, 2018
45
0
Moto g4 plus

I have a moto g4 plus .......i m update with oreo today.....after update net work is note working ....imei is fine....but network problem.....after i m downgrade with nougate 7.0 ......imei nomber is null.....after i m update 40mb in nougate system update....mobile restart for installing but now in dead mode......


I m trying blank flash but "waiting for firehose get ready" stunk at this moment.....

Plz help me some body.......
 

Top Liked Posts

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