Database Users

[HELP] Hard Brick / No Bootloader Moto G4 Plus

Hi, I tested most of the tutorials I saw on this page, including this one:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
But I can't recover my Moto G4 Plus.
The qboot_log is as follows:
**** Log buffer [000001] 2017-05-29_17:16:12 ****
[ 0.000] Opening device: \\.\COM26
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 21868753 (0x14db0d1)
[ 0.004] Opening singleimage
[ 0.270] Loading package
[ 0.276] ...filename = singleimage.pkg.xml
[ 0.280] Loading programmer
[ 0.281] ...filename = programmer.mbn
[ 0.281] Sending programmer
[ 0.502] Handling things over to programmer
[ 0.502] Identifying CPU version
[ 0.506] Waiting for firehose to get ready
[ 61.162] Waiting for firehose to get ready
[121.436] ...MSM8952 unknown
[121.436] Determining target secure state
[121.440] Waiting for firehose to get ready
[182.473] ...secure = no
[182.495] Flashing GPT...
[182.496] Flashing partition:0 with gpt_main0.bin
[182.496] Initializing storage
[182.502] Waiting for firehose to get ready
[244.409] Configuring device...
[244.414] Waiting for firehose to get ready
[305.562] Waiting for firehose to get ready
[367.782] Waiting for firehose to get ready
[430.850] Waiting for firehose to get ready
[491.546] 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.546] Check qboot_log.txt for more details
[491.547] Total time: 491.548s
[491.548]
[491.548] qboot version 3.40
[491.548]
[491.548] DEVICE {
[491.548] name = "\\.\COM26",
[491.548] flags = "0x64",
[491.548] addr = "0x22FE6C",
[491.548] sahara.current_mode = "0",
[491.548] api.buffer = "0x1A60020",
[491.548] cpu.serial = "21868753",
[491.548] cpu.id = "2418",
[491.548] cpu.sv_sbl = "0",
[491.548] cpu.name = "MSM8952",
[491.548] storage.type = "eMMC",
[491.548] sahara.programmer = "programmer.mbn",
[491.548] module.firehose = "0x3AF2B8",
[491.548] cpu.ver = "0",
[491.548] cpu.vername = "unknown",
[491.548] api.bnr = "0x19B2340",
[491.548] }
[491.548]
[491.548]
[491.548] Backup & Restore {
[491.548] num_entries = 0,
[491.548] restoring = "false",
[491.548] backup_error = "not started",
[491.548] restore_error = "not started",
[491.548] }
[491.548]
Click to expand...
Click to collapse

arizaseba said:
Hi, I tested most of the tutorials I saw on this page, including this one:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
But I can't recover my Moto G4 Plus.
The qboot_log is as follows:
Click to expand...
Click to collapse
Estou com esse mesmo problema.. Não consigo reviver meu moto g4
I'm having this same problem .. I can not revive my g4 bike

[ 0.000] Opening device: \\.\COM7
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2418 (0x972)
[ 0.000] ...cpu.sn = 13573873 (0xcf1ef1)
[ 0.000] Opening singleimage
[ 0.016] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.234] Handling things over to programmer
[ 0.234] Identifying CPU version
[ 0.234] Waiting for firehose to get ready
[ 60.618] Waiting for firehose to get ready
[120.979] ...MSM8952 unknown
[120.979] Determining target secure state
[120.979] Waiting for firehose to get ready
[181.357] ...secure = no
[181.357] Flashing GPT...
[181.388] Flashing partition:0 with gpt_main0.bin
[181.388] Initializing storage
[181.404] Waiting for firehose to get ready
[241.761] Configuring device...
[264.166] Waiting for firehose to get ready
[324.496] Waiting for firehose to get ready
[384.643] Waiting for firehose to get ready
[444.723] Waiting for firehose to get ready
[504.808] 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
[504.808] Check qboot_log.txt for more details
[504.808] Total time: 504.808s
FAILED: qb_flash_singleimage()->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
plz help me..

go get new device

Bricked after Android N update

I tried to update my phone to Android N, but once the update installed, it went onto a black screen and will not turn on now.
When connected to the computer it says - qualcomm hs-usb qdloader 9008
I cant get anything loaded through pressing the volume down and power key.
I have tried to follow the link below but can't get blank-flash to work, I only get to this
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
[ 4.072]
[ 4.072] qboot version 3.40
[ 4.072]
[ 4.072] DEVICE {
[ 4.072] name = "\\.\COM5",
[ 4.072] flags = "0x64",
[ 4.072] addr = "0x28FE6C",
[ 4.072] api.bnr = "0x5F2DE8",
[ 4.072] }
[ 4.072]
[ 4.072]
[ 4.072] Backup & Restore {
[ 4.072] num_entries = 0,
[ 4.072] restoring = "false",
[ 4.072] backup_error = "not started",
[ 4.072] restore_error = "not started",
[ 4.072] }
[ 4.072]
**** Log buffer [000001] 2017-04-06_00:08:07 ****
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
[ 4.072]
[ 4.072] qboot version 3.40
[ 4.072]
[ 4.072] DEVICE {
[ 4.072] name = "\\.\COM5",
[ 4.072] flags = "0x64",
[ 4.072] addr = "0x28FE6C",
[ 4.072] api.bnr = "0x5A2DE8",
[ 4.072] }
[ 4.072]
[ 4.072]
[ 4.072] Backup & Restore {
[ 4.072] num_entries = 0,
[ 4.072] restoring = "false",
[ 4.072] backup_error = "not started",
[ 4.072] restore_error = "not started",
[ 4.072] }
[ 4.072]
**** Log buffer [000001] 2017-08-23_07:24:45 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2418 (0x972)
[ 0.000] ...cpu.sn = 13126848 (0xc84cc0)
[ 0.000] Opening singleimage
[ 0.219] Loading package
[ 0.234] ...filename = singleimage.pkg.xml
[ 0.234] Loading programmer
[ 0.234] ...filename = programmer.mbn
[ 0.234] Sending programmer
[ 0.469] Handling things over to programmer
[ 0.469] Identifying CPU version
[ 0.469] Waiting for firehose to get ready
[ 60.980] Waiting for firehose to get ready
[121.447] ...MSM8952 unknown
[121.447] Determining target secure state
[121.463] Waiting for firehose to get ready
[181.889] ...secure = no
[181.904] Flashing GPT...
[181.920] Flashing partition:0 with gpt_main0.bin
[181.920] Initializing storage
[181.936] Waiting for firehose to get ready
[242.406] Configuring device...
[242.406] Waiting for firehose to get ready
[302.883] Waiting for firehose to get ready
[363.337] Waiting for firehose to get ready
[423.753] Waiting for firehose to get ready
[484.166] 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
[484.166] Check qboot_log.txt for more details
[484.166] Total time: 484.166s
[484.197]
[484.197] qboot version 3.40
[484.197]
[484.197] DEVICE {
[484.197] name = "\\.\COM3",
[484.197] flags = "0x64",
[484.197] addr = "0x61FE5C",
[484.197] sahara.current_mode = "0",
[484.197] api.buffer = "0x1388020",
[484.197] cpu.serial = "13126848",
[484.197] cpu.id = "2418",
[484.197] cpu.sv_sbl = "0",
[484.197] cpu.name = "MSM8952",
[484.197] storage.type = "eMMC",
[484.197] sahara.programmer = "programmer.mbn",
[484.197] module.firehose = "0x7389B8",
[484.197] cpu.ver = "0",
[484.197] cpu.vername = "unknown",
[484.197] api.bnr = "0x834860",
[484.197] }
[484.197]
[484.197]
[484.197] Backup & Restore {
[484.197] num_entries = 0,
[484.197] restoring = "false",
[484.197] backup_error = "not started",
[484.197] restore_error = "not started",
[484.197] }
[484.197]
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Please help
Thank you

Hello.
I believe you'll need the updated blankflash.
Follow this guide - https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

I would try holding power key and vol down (without it being connected to PC, make sure it has enough battery) for as long as needed to reboot in to normal bootloader. This can be up to 5-10 mins

Hard Bricked Moto G4 Plus
Kindly send your mail ID and I will forward you all the files
Moderator Edit: "Kindly" don't ask anyone to do this.
Members are advised to avoid this kind of garbage.

why are you giving your Email ID for no whatever reason. Blankflash files are available on the Thread
@ncfcdaniel if you dont know which thread it is, then here is the link : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

Need Latest September/October BlankFlash

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]

did u tried this ?
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

veejay97 said:
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]
Click to expand...
Click to collapse
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:
did u tried this ?
https://forum.xda-developers.com/mot...guide-t3657761
Click to expand...
Click to collapse
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

Amberdawn 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
Thanks in advance
Click to expand...
Click to collapse
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
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!

siddhesh9146 said:
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
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!
Click to expand...
Click to collapse
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?

Amberdawn said:
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?
Click to expand...
Click to collapse
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

siddhesh9146 said:
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
Click to expand...
Click to collapse
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 said:
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
Click to expand...
Click to collapse
Any suggestion? Any idea of what is happening with the device?
Regards

Amberdawn said:
Any suggestion? Any idea of what is happening with the device?
Regards
Click to expand...
Click to collapse
Did you tried flashing stock rom again?

strongst said:
Did you tried flashing stock rom again?
Click to expand...
Click to collapse
No I didn't. As I was looking for a solution for the blankflash issue I haven't tried to go any further step yet.

Hi,
Still having problems while executing the blankflash file, can't figure out what could be the problem. Any idea/suggestion?
Thanks in advance.

Amberdawn said:
Hi,
Still having problems while executing the blankflash file, can't figure out what could be the problem. Any idea/suggestion?
Thanks in advance.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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?

echo92 said:
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
Click to expand...
Click to collapse
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]
echo92 said:
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?
Click to expand...
Click to collapse
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.

I guess someone from motorola need to leak another blankflash...

siddhesh9146 said:
did u tried this ?
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
thank you so much..:good:

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!

abhi212b said:
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!
Click to expand...
Click to collapse
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...
Click to expand...
Click to collapse
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

Amberdawn said:
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
Click to expand...
Click to collapse
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..

abhi212b said:
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..
Click to expand...
Click to collapse
Yes, I did! I uninstalled the Motorola Drivers and then reinstalled the ones linked in your video. I also reinstalled the Qualcomm drivers

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.......

Moto G4 hard bricked (XT 1622)

This is another question on how to unbrick a hard-bricked G4.
What I did so far:
1) Windows runs on test mode.
2) QualcommDrv installed --> Device is shown as "Qualcomm HS-USB QDLoader 9008 (COM5)"
3) Downloaded "blankflash-MotoG4" package and ran the blank-flash.bat file --> ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
4) Pressed POWER BUTTON + VOL DOWN while running the bat file: same error
5) out of curiosity I took a blankflas package for G4+ and this took me to " Waiting for firehose to get ready"
but nothing more happened after this message.
Any advice? Thank you!

The same problem is happening with my moto g4.
The same problem is happening with my moto g4, I tried many blank flash, but did not work.
markusk11 said:
This is another question on how to unbrick a hard-bricked G4.
What I did so far:
1) Windows runs on test mode.
2) QualcommDrv installed --> Device is shown as "Qualcomm HS-USB QDLoader 9008 (COM5)"
3) Downloaded "blankflash-MotoG4" package and ran the blank-flash.bat file --> ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
4) Pressed POWER BUTTON + VOL DOWN while running the bat file: same error
5) out of curiosity I took a blankflas package for G4+ and this took me to " Waiting for firehose to get ready"
but nothing more happened after this message.
Any advice? Thank you!
Click to expand...
Click to collapse

Can you check the qboot log and see if there's any more info there that might explain what the problem is? An IO error normally indicates that your device can't be detected or there's an issue with the file system

qboot_log.txt
[ -0.000] Opening device: \\.\COM5
[ 0.010] Detecting device
[ 0.012] ...cpu.id = 2418 (0x972)
[ 0.012] ...cpu.sn = 39153073 (0x2556db1)
[ 0.012] Opening singleimage
[ 0.012] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.018] Loading programmer
[ 0.019] ...filename = programmer.mbn
[ 0.019] Sending programmer
[ 0.236] Handling things over to programmer
[ 0.237] Identifying CPU version
[ 0.239] Waiting for firehose to get ready
[ 9.753] ReadFile() failed, GetLastError()=0
[ 9.803] ReadFile() failed, GetLastError()=0
[ 62.253] Waiting for firehose to get ready
[122.562] ...MSM8952 unknown
[122.562] Determining target secure state
[122.564] Waiting for firehose to get ready
[182.873] ...secure = no
[182.883] Flashing GPT...
[182.884] Flashing partition:0 with gpt_main0.bin
[182.884] Initializing storage
[182.887] Waiting for firehose to get ready
[243.195] Configuring device...
[243.197] Waiting for firehose to get ready
[303.506] Waiting for firehose to get ready
[363.814] Waiting for firehose to get ready
[424.126] Waiting for firehose to get ready
[484.430] 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
[484.430] Check qboot_log.txt for more details
[484.431] Total time: 484.431s
[484.432]
[484.432] qboot version 3.40
[484.432]
[484.432] DEVICE {
[484.432] name = "\\.\COM5",
[484.432] flags = "0x64",
[484.432] addr = "0x28FE6C",
[484.432] sahara.current_mode = "0",
[484.432] api.buffer = "0x2600020",
[484.432] cpu.serial = "39153073",
[484.432] cpu.id = "2418",
[484.432] cpu.sv_sbl = "0",
[484.432] cpu.name = "MSM8952",
[484.432] storage.type = "eMMC",
[484.432] sahara.programmer = "programmer.mbn",
[484.432] module.firehose = "0x25616A0",
[484.432] cpu.ver = "0",
[484.432] cpu.vername = "unknown",
[484.432] api.bnr = "0x2567DA8",
[484.432] }
[484.432]
[484.432]
[484.432] Backup & Restore {
[484.432] num_entries = 0,
[484.432] restoring = "false",
[484.432] backup_error = "not started",
[484.432] restore_error = "not started",
[484.432] }
[484.432]

Unable to unbrick Moto G4 Plus, Please help.

Tried almost all help given in XDA.. i'm exhausted.
Tried doing blankflast different versions as provided by different threads in forum, but nothing helped.
Qboot logs for reference
[ -0.000] Opening device: \\.\COM8
[ 0.004] Detecting device
[ 0.004] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 13700177 (0xd10c51)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.012] ...filename = singleimage.pkg.xml
[ 0.012] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.236] Handling things over to programmer
[ 0.236] Identifying CPU version
[ 0.236] Waiting for firehose to get ready
[ 60.618] Waiting for firehose to get ready
[121.049] ...MSM8952 unknown
[121.049] Determining target secure state
[121.049] Waiting for firehose to get ready
[181.466] ...secure = no
[181.466] Flashing GPT...
[181.466] Flashing partition:0 with gpt_main0.bin
[181.482] Initializing storage
[181.482] Waiting for firehose to get ready
[241.893] Configuring device...
[241.897] Waiting for firehose to get ready
[302.311] Waiting for firehose to get ready
[362.736] Waiting for firehose to get ready
[423.099] Waiting for firehose to get ready
[483.440] 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
[483.440] Check qboot_log.txt for more details
[483.440] Total time: 483.444s
[483.440]
[483.440] qboot version 3.40
[483.440]
[483.440] DEVICE {
[483.440] name = "\\.\COM8",
[483.440] flags = "0x64",
[483.440] addr = "0x61FE5C",
[483.440] sahara.current_mode = "0",
[483.440] api.buffer = "0xE13020",
[483.440] cpu.serial = "13700177",
[483.440] cpu.id = "2418",
[483.440] cpu.sv_sbl = "0",
[483.440] cpu.name = "MSM8952",
[483.440] storage.type = "eMMC",
[483.440] sahara.programmer = "programmer.mbn",
[483.440] module.firehose = "0x6D8E50",
[483.440] cpu.ver = "0",
[483.440] cpu.vername = "unknown",
[483.440] api.bnr = "0x825C60",
[483.440] }
[483.440]
[483.440]
[483.440] Backup & Restore {
[483.440] num_entries = 0,
[483.440] restoring = "false",
[483.440] backup_error = "not started",
[483.440] restore_error = "not started",
[483.440] }
[483.440]

Have you tried the OPJ28.111-22 blankflash as posted here https://forum.xda-developers.com/showpost.php?p=79737132&postcount=787 or here: https://forum.xda-developers.com/showpost.php?p=79714477&postcount=778
The blankflash might take a few tries to work.