[Solved] Unbrick (Hard Bricked/Dead) Motorola G 4 plus or any Qualcomm mobile Device

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Motog4Plus XT1643, I restored stock FW, It was a downgrade from 93.14-8 to 93.14. Then I was installing march security OTA update 93.14-4 (march), during installation device got full bricked, No Bootloader, it was my first time I did a silly thing which is downgrading & installing OTA. Tried Blank flashing too which was not successful, plz HELP ME.
Unfortunately, there's little we can do to help, as far as I know. Similar to my reply above, we simply don't have the tools to unbrick a device bricked in this manner - effectively, the newer bootloader seems to have been corrupted by the OTA and the blankflash appears to be rejected by the newer bootloader from the June 2017 update.

Now, you could wait for a newer blankflash (but that may arrive, it may not), but if you need a working device, you could have your device motherboard replaced (for 6000 rupees, you mentioned) or alternatively save up for a new device and use this as an unfortunate, and expensive, lesson in downgrading. I'm sorry, I'm not aware of any other means to fix your device at the moment.
 

leo88sandy

Senior Member
May 5, 2016
54
1
0
Agartala
Unfortunately, there's little we can do to help, as far as I know. Similar to my reply above, we simply don't have the tools to unbrick a device bricked in this manner - effectively, the newer bootloader seems to have been corrupted by the OTA and the blankflash appears to be rejected by the newer bootloader from the June 2017 update.

Now, you could wait for a newer blankflash (but that may arrive, it may not), but if you need a working device, you could have your device motherboard replaced (for 6000 rupees, you mentioned) or alternatively save up for a new device and use this as an unfortunate, and expensive, lesson in downgrading. I'm sorry, I'm not aware of any other means to fix your device at the moment.
Couldn't wait more, so ordered g5plus worth 13500 in offer , still will be wit for g4plus blankflash file. As i can use both the mobile one is for experimenting.
 

gagan.satolia

New member
Aug 12, 2017
1
0
0
C:\Users\Gagan satolia\Downloads\hard unbrick\blank-flash\New folder>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 2418 (0x972)
[ -0.000] ...cpu.sn = 14667512 (0xdfcef8)
[ -0.000] Opening singleimage
[ 0.063] Loading package
[ 0.063] ...filename = singleimage.pkg.xml
[ 0.063] Loading programmer
[ 0.078] ...filename = programmer.mbn
[ 0.078] Sending programmer
[ 0.293] Handling things over to programmer
[ 0.293] Identifying CPU version
[ 0.293] Waiting for firehose to get ready
[ 4.648] ReadFile() failed, GetLastError()=0
[ 4.707] ReadFile() failed, GetLastError()=0
[ 4.758] ReadFile() failed, GetLastError()=0
[ 4.810] ReadFile() failed, GetLastError()=0
[ 5.398] ReadFile() failed, GetLastError()=0
[ 5.455] ReadFile() failed, GetLastError()=0
[ 5.530] ReadFile() failed, GetLastError()=0
[ 5.588] ReadFile() failed, GetLastError()=0
[ 5.658] ReadFile() failed, GetLastError()=0
[ 5.711] ReadFile() failed, GetLastError()=0
[ 5.788] ReadFile() failed, GetLastError()=0
[ 5.845] ReadFile() failed, GetLastError()=0
[ 5.904] ReadFile() failed, GetLastError()=0
[ 5.960] ReadFile() failed, GetLastError()=0
[ 6.021] ReadFile() failed, GetLastError()=0
[ 6.074] ReadFile() failed, GetLastError()=0
[ 6.151] ReadFile() failed, GetLastError()=0
[ 6.211] ReadFile() failed, GetLastError()=0
[ 6.280] ReadFile() failed, GetLastError()=0
[ 6.333] ReadFile() failed, GetLastError()=0
[ 6.406] ReadFile() failed, GetLastError()=0
[ 6.458] ReadFile() failed, GetLastError()=0
[ 6.524] ReadFile() failed, GetLastError()=0
[ 6.579] ReadFile() failed, GetLastError()=0
[ 6.666] ReadFile() failed, GetLastError()=0
[ 6.720] ReadFile() failed, GetLastError()=0
[ 6.849] ReadFile() failed, GetLastError()=0
[ 62.193] Waiting for firehose to get ready
[122.497] ...MSM8952 unknown
[122.497] Determining target secure state
[122.497] Waiting for firehose to get ready
[182.775] ...secure = no
[182.788] Flashing GPT...
[182.788] Flashing partition:0 with gpt_main0.bin
[182.807] Initializing storage
[182.811] Waiting for firehose to get ready
[243.061] Configuring device...
[243.061] Waiting for firehose to get ready
[303.310] Waiting for firehose to get ready
[363.567] Waiting for firehose to get ready




pls help me
 
Mar 5, 2015
15
0
0
Hello guys I have the same problem with my Motorola g4 plus xt1644, bricked dead by installing March security patcher. I tryed to fix it but only appear a command like waiting for de device and something and at the end failed up
 

Snakehips999

Member
Jul 6, 2017
5
0
0
Hello, I'm working on that with Linux but encountering following error:

./blank-flash.sh
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.002] ...cpu.id = 2418 (0x972)
[ 0.002] ...cpu.sn = 33383710 (0x1fd651e)
[ 0.002] Opening singleimage
[ 0.002] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.020] Loading programmer
[ 0.021] ...filename = programmer.mbn
[ 0.021] Sending programmer
[ 0.251] Handling things over to programmer
[ 0.251] Identifying CPU version
[ 0.259] Waiting for firehose to get ready
[ 3.259] serial_write(), line 280: Input/output error
[ 61.844] Waiting for firehose to get ready
[121.943] ...MSM8952 unknown
[121.943] Determining target secure state
[121.950] Waiting for firehose to get ready
[124.950] serial_write(), line 280: Input/output error
[184.183] ...secure = no
[184.217] Flashing GPT...
[184.217] Flashing partition:0 with gpt_main0.bin
[184.217] Initializing storage
[184.221] Waiting for firehose to get ready
[244.983] Configuring device...
[244.991] Waiting for firehose to get ready
[305.762] Waiting for firehose to get ready
[366.538] Waiting for firehose to get ready
[427.313] Waiting for firehose to get ready
[488.076] 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
[488.076] Check qboot_log.txt for more details
[488.076] Total time: 488.076s
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
Any solution, Mr. OP?
 
Last edited:

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Thanks mate, am I wrong or is it like a scandal?
Everyone updated via OTA, devices bricked all over the world.
Good Job, Motorola/Lenovo :good:
How did you brick your device?

If it was via downgrading from the June 2017 update (or downgrading from the June 2017 update) and then updating via OTA), then that is what incurs a (currently unrecoverable) hard brick. (As an aside, quite a lot of users have updated to the June 2017 update okay, https://forum.xda-developers.com/moto-g4-plus/how-to/ota-update-june-security-patch-started-t3632792)

Should Motorola/Lenovo made it explicit that you cannot downgrade from this OTA/June security patch? Maybe.

Only options at the moment are to have your motherboard replaced or save up for another device.
 

chiraxo

Member
Sep 18, 2016
7
0
0
tadepalligudem
getting error

C:\Users\chiranjeevi\Documents\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM5
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 9987626 (0x98662a)
[ 0.005] Opening singleimage
[ 0.006] Loading package
[ 0.017] ...filename = singleimage.pkg.xml
[ 0.022] Loading programmer
[ 0.022] ...filename = programmer.mbn
[ 0.023] Sending programmer
[ 0.247] Handling things over to programmer
[ 0.247] Identifying CPU version
[ 0.252] Waiting for firehose to get ready
[ 60.351] Waiting for firehose to get ready
[120.442] ...MSM8952 unknown
[120.442] Determining target secure state
[120.448] Waiting for firehose to get ready
[180.533] ...secure = no
[180.561] Flashing GPT...
[180.561] Flashing partition:0 with gpt_main0.bin
[180.562] Initializing storage
[180.570] Waiting for firehose to get ready
[240.676] Configuring device...
[240.681] Waiting for firehose to get ready
[300.834] Waiting for firehose to get ready
[360.951] Waiting for firehose to get ready
[421.064] Waiting for firehose to get ready
[481.161] 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.164] Check qboot_log.txt for more details
[481.165] Total time: 481.169s
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

C:\Users\chiranjeevi\Documents\blankflash>pause
Press any key to continue . . .
 
Aug 13, 2017
15
0
0
C:\Users\Deepak\Desktop\blankflash1\blankflash>qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM8
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 23839371 (0x16bc28b)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.012] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.017] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.314] Handling things over to programmer
[ 0.316] Identifying CPU version
[ 0.326] Waiting for firehose to get ready
[ 60.897] Waiting for firehose to get ready
[121.478] ...MSM8952 unknown
[121.478] Determining target secure state
[121.478] Waiting for firehose to get ready
[182.043] ...secure = no
[182.074] Flashing GPT...
[182.074] Flashing partition:0 with gpt_main0.bin
[182.074] Initializing storage
[182.089] Waiting for firehose to get ready
[242.623] Configuring device...
[242.623] Waiting for firehose to get ready
[303.047] Waiting for firehose to get ready
[363.475] Waiting for firehose to get ready
[424.095] Waiting for firehose to get ready
[484.697] 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.697] Check qboot_log.txt for more details
[484.697] Total time: 484.701s
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


Getting this error plz plz plz plz help me.....

---------- Post added at 04:58 AM ---------- Previous post was at 04:01 AM ----------

C:\Users\chiranjeevi\Documents\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \.\COM5
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 9987626 (0x98662a)
[ 0.005] Opening singleimage
[ 0.006] Loading package
[ 0.017] ...filename = singleimage.pkg.xml
[ 0.022] Loading programmer
[ 0.022] ...filename = programmer.mbn
[ 0.023] Sending programmer
[ 0.247] Handling things over to programmer
[ 0.247] Identifying CPU version
[ 0.252] Waiting for firehose to get ready
[ 60.351] Waiting for firehose to get ready
[120.442] ...MSM8952 unknown
[120.442] Determining target secure state
[120.448] Waiting for firehose to get ready
[180.533] ...secure = no
[180.561] Flashing GPT...
[180.561] Flashing partition:0 with gpt_main0.bin
[180.562] Initializing storage
[180.570] Waiting for firehose to get ready
[240.676] Configuring device...
[240.681] Waiting for firehose to get ready
[300.834] Waiting for firehose to get ready
[360.951] Waiting for firehose to get ready
[421.064] Waiting for firehose to get ready
[481.161] 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.164] Check qboot_log.txt for more details
[481.165] Total time: 481.169s
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

C:\Users\chiranjeevi\Documents\blankflash>pause
Press any key to continue . . .
Did u got sol.?????

---------- Post added at 05:35 AM ---------- Previous post was at 04:58 AM ----------

I have successfully recovered my dead/hard brick moto g4 plus mobile using below process. :)

To give you background, I have hard bricked my new moto g4 plus mobile. To do that, I have unlocked boot loader which void my warranty, then I have rooted yet and got root access. Till that it was working. After that I have installed custom rom cyanogenmod 14.1 . It was still working for some days. Now As I came from blackberry z10 to moto, I was missing blackberry hub features, so I downloaded BlackBerry android OS(Blackberry Priv) and tried to flash it. that's it, it stopped working. I know it was stupid things to do :( . I have given mobile to service center, other few famous mobile repairing shops, but no one was able to do anything.

My mobile was dead for almost 1 month, I tried lots of option, including MI flash tool, QPST(QFIL) etc. but didn't get it thought it. For current options also I was working for couple days, after that I got the solution.

Let start work now.....
------------------------------------------------------

There are two parts for this tutorial,
Part1 - make your device bootable/softbrick/start in recovery mode. This is difficult part and most of us stuck here only. We need to make device from hard brick to soft brick. Should work for all Qualcomm devices(except hardware failure).
Part2 - Flash ROM to your device. This is easy part and there are lots tutorial/information available to flashing ROM into device. It will be dependent on individual devices.

Part1:- -
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

Download QualcommDrv.zip from here , extract to an empty folder, then open the folder according to your Windows type (x64 or x86) and double click dpinst64.exe (if you have 64-bit Windows) to install the Qualcomm driver
now please connect your Qualcomm Mobile to PC or laptop Your phone should now being detected as “Qualcomm HS-USB QDLoader 9008” and the driver version 2.0.8.7 (please check it through Windows’ “Device Manager”). If its not detected, then you can keep mobile connecting to computer and press power button and volume down button.( This is for motorola g4 plus and can be different for your mobile. )

Now you have your mobile connected to computer, now follow the below steps.

Please download zip " blankflash1.zip" from location here extract it your computer and goto extracted folder and click blank-flash.bat
It will start in command prompt and detect device on your computer port(eg. COM5, COM8 etc).

If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile. Refer below Part2 for this.
If above didn't work and you are getting error like below..



Or any other error, then its little tricky to solve this.
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.



5. once this is complete then you mobile will boot in bootloader/recovery mode, or you can go to recovery mode using volume up/down button.
After this, your mobile would be detected using adb(android driver), and you can execute fastboot commands.

Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.

Step3 is the key for whole process. you may need to try multiple times while blank-flash.bat is running.

Once you reached here, Congratulations, your mobile is saved and back to life. next part flashing stock rom is very easy. I will try to find url for that.
you just need correct ROM for your mobile and steps to flash it.

Part 2 :
Below is url for motorola, you will get idea how to do it for your mobile by going through it.
Alternative, now you can give your mobile to service center or mobile repair shop to flash ROM.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695

Other link for flashing ROM into any android mobile:
https://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
https://forum.xda-developers.com/showthread.php?t=2131284
https://www.xda-developers.com/how-to-install-custom-rom-android/

Let me know if you have any doubts/questions, I will try to update.

Also let me know if it helps you and you can also Donate :) (Optional).
C:\Users\Deepak\Desktop\blankflash1\blankflash>qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM8
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 23839371 (0x16bc28b)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.012] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.017] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.314] Handling things over to programmer
[ 0.316] Identifying CPU version
[ 0.326] Waiting for firehose to get ready
[ 60.897] Waiting for firehose to get ready
[121.478] ...MSM8952 unknown
[121.478] Determining target secure state
[121.478] Waiting for firehose to get ready
[182.043] ...secure = no
[182.074] Flashing GPT...
[182.074] Flashing partition:0 with gpt_main0.bin
[182.074] Initializing storage
[182.089] Waiting for firehose to get ready
[242.623] Configuring device...
[242.623] Waiting for firehose to get ready
[303.047] Waiting for firehose to get ready
[363.475] Waiting for firehose to get ready
[424.095] Waiting for firehose to get ready
[484.697] 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.697] Check qboot_log.txt for more details
[484.697] Total time: 484.701s
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


Getting this error plz plz plz plz help me.....
 

tawanda01

Member
Dec 14, 2016
15
2
0
i heard no news about new blank flash maybe if android 8.0 is out i think they will make a new blankflash so please wait for long but dont lose hope
 

tawanda01

Member
Dec 14, 2016
15
2
0
can someone plz upload file name
sdm_hdr.mbn and
pitfile.pit
adb commands for.
sdm_hdr.mbn
dd if=/dev/block/mmcblk0p1 of=/sdcard/Desktop/
sdm_hdr.mbn
pitfile.pit
dd if=/dev/block/mmcblk0p9 of=/sdcard/Desktop/
pitfile.pit
and copy this file frome desktop and uploade on mega.
 
  • Like
Reactions: deepakgadhave61
Aug 13, 2017
15
0
0
Not working on XT1643 plzz help stuck in firehose....

---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------

can someone plz upload file name
sdm_hdr.mbn and
pitfile.pit
adb commands for.
sdm_hdr.mbn
dd if=/dev/block/mmcblk0p1 of=/sdcard/Desktop/
sdm_hdr.mbn
pitfile.pit
dd if=/dev/block/mmcblk0p9 of=/sdcard/Desktop/
pitfile.pit
and copy this file frome desktop and uploade on mega.

Which model r u using
 
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