FORUMS

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

16 posts
Thanks Meter: 38
 
By vijayjadhav_143, Junior Member on 5th April 2017, 09:11 PM
Post Reply Email Thread
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..

Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -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
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
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.

Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[  2.059] ReadFile() failed, GetLastError()=0
[  2.563] ...cpu.id  = 2418 (0x972)
[  2.563] ...cpu.sn  = 28194769 (0x1ae37d1)
[  2.563] Opening singleimage
[  2.563] Loading package
[  2.563] ...filename = singleimage.pkg.xml
[  2.563] Loading programmer
[  2.563] ...filename = programmer.mbn
[  2.563] Sending programmer
[  2.793] Handling things over to programmer
[  2.793] Identifying CPU version
[  2.793] Waiting for firehose to get ready
[  5.800] ...MSM8952 1.1
[  5.800] Determining target secure state
[  5.800] ...secure = yes
[  5.816] Flashing GPT...
[  5.816] Flashing partition:0 with gpt_main0.bin
[  5.816] Initializing storage
[  5.816] Configuring device...
[  5.832] ...blksz = 512
[  6.331] Re-initializing storage...
[  6.331] Initializing storage
[  6.362] Flashing bootloader...
[  6.362] Flashing aboot with emmc_appsboot.mbn
[  6.721] Flashing rpm with rpm.mbn
[  6.783] Flashing tz with tz.mbn
[  7.033] Flashing hyp with hyp.mbn
[  7.080] Flashing cmnlib with cmnlib.mbn
[  7.158] Flashing keymaster with keymaster.mbn
[  7.236] Flashing sbl1 with sbl1.mbn
[  7.392] Rebooting to fastboot
[  7.392] Total time: 7.392s
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/mot...igned-t3460695

Other link for flashing ROM into any android mobile:
https://forum.xda-developers.com/wik...uide_-_Android
https://forum.xda-developers.com/sho....php?t=2131284
https://www.xda-developers.com/how-t...m-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).
The Following 37 Users Say Thank You to vijayjadhav_143 For This Useful Post: [ View ] Gift vijayjadhav_143 Ad-Free
6th April 2017, 01:46 AM |#2  
Junior Member
Thanks Meter: 5
 
More
Thanks for the help, it is good to know that there are people helping others but I already repaired it with the same method thanks for responding
18th April 2017, 06:28 AM |#3  
Senior Member
Flag Bangalore
Thanks Meter: 577
 
Donate to Me
More
Secure=no
Quote:
Originally Posted by vijayjadhav_143

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

Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -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
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
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.

Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[  2.059] ReadFile() failed, GetLastError()=0
[  2.563] ...cpu.id  = 2418 (0x972)
[  2.563] ...cpu.sn  = 28194769 (0x1ae37d1)
[  2.563] Opening singleimage
[  2.563] Loading package
[  2.563] ...filename = singleimage.pkg.xml
[  2.563] Loading programmer
[  2.563] ...filename = programmer.mbn
[  2.563] Sending programmer
[  2.793] Handling things over to programmer
[  2.793] Identifying CPU version
[  2.793] Waiting for firehose to get ready
[  5.800] ...MSM8952 1.1
[  5.800] Determining target secure state
[  5.800] ...secure = yes
[  5.816] Flashing GPT...
[  5.816] Flashing partition:0 with gpt_main0.bin
[  5.816] Initializing storage
[  5.816] Configuring device...
[  5.832] ...blksz = 512
[  6.331] Re-initializing storage...
[  6.331] Initializing storage
[  6.362] Flashing bootloader...
[  6.362] Flashing aboot with emmc_appsboot.mbn
[  6.721] Flashing rpm with rpm.mbn
[  6.783] Flashing tz with tz.mbn
[  7.033] Flashing hyp with hyp.mbn
[  7.080] Flashing cmnlib with cmnlib.mbn
[  7.158] Flashing keymaster with keymaster.mbn
[  7.236] Flashing sbl1 with sbl1.mbn
[  7.392] Rebooting to fastboot
[  7.392] Total time: 7.392s
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/mot...igned-t3460695

Other link for flashing ROM into any android mobile:
https://forum.xda-developers.com/wik...uide_-_Android
https://forum.xda-developers.com/sho....php?t=2131284
https://www.xda-developers.com/how-t...m-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).



For me it is showing secure=no and waiting for firehose to get ready is constantly popping out plz plz help me
The Following 2 Users Say Thank You to shamith For This Useful Post: [ View ] Gift shamith Ad-Free
18th April 2017, 07:52 AM |#4  
OP Junior Member
Flag Pune
Thanks Meter: 38
 
Donate to Me
More
Quote:
Originally Posted by Irvin16

For me it is showing secure=no and waiting for firehose to get ready is constantly popping out plz plz help me

Could you please provide more details? on which steps you are getting error? error log/screenshot?
Its command prompt activity so not sure how you are getting pop up.
21st April 2017, 12:47 AM |#5  
Member
Thanks Meter: 0
 
More
for moto g4 play
Colleague you have this file for moto g4 play
21st April 2017, 08:13 AM |#6  
OP Junior Member
Flag Pune
Thanks Meter: 38
 
Donate to Me
More
you can try above files, these are blankflash files meaning, after this your mobile will be reboot in recovery mode and will be available to connect it using adb/android driver and after that you can flash Moto g4 play stock ROM. you can search for moto g4 stock rom on internet.
21st April 2017, 10:40 AM |#7  
Member
Thanks Meter: 0
 
More
fo moto g4 play
Quote:
Originally Posted by vijayjadhav_143

you can try above files, these are blankflash files meaning, after this your mobile will be reboot in recovery mode and will be available to connect it using adb/android driver and after that you can flash Moto g4 play stock ROM. you can search for moto g4 stock rom on internet.



It's giving you this error.
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 1797 (0x705)
[ -0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ 0.010] Failed identify board. Wrong package?
[ 0.010] ERROR: error loading package
[ 0.010] Check qboot_log.txt for more details
[ 0.010] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
21st April 2017, 02:53 PM |#8  
OP Junior Member
Flag Pune
Thanks Meter: 38
 
Donate to Me
More
try with other blankflash.
Quote:
Originally Posted by tecnologianet2

It's giving you this error.
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 1797 (0x705)
[ -0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ 0.010] Failed identify board. Wrong package?
[ 0.010] ERROR: error loading package
[ 0.010] Check qboot_log.txt for more details
[ 0.010] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package


Did you tried with other blankflash*.zip, Please note below lines.

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.
21st April 2017, 03:08 PM |#9  
Member
Thanks Meter: 0
 
More
for moto g4 play
Quote:
Originally Posted by vijayjadhav_143

Did you tried with other blankflash*.zip, Please note below lines.

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.

error logs

blankflash1
[ 0.000] Opening device: \\.\COM8
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 1797 (0x705)
[ 0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.000] Failed identify board. Wrong package?
[ 0.000] ERROR: error loading package
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package

blankflash2
opening device: \\.\COM8
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.010s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)

blankflash3
opening device: \\.\COM8
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
21st April 2017, 03:30 PM |#10  
OP Junior Member
Flag Pune
Thanks Meter: 38
 
Donate to Me
More
Quote:
Originally Posted by tecnologianet2

error logs

blankflash1
[ 0.000] Opening device: \\.\COM8
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 1797 (0x705)
[ 0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.000] Failed identify board. Wrong package?
[ 0.000] ERROR: error loading package
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package

blankflash2
opening device: \\.\COM8
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.010s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)

blankflash3
opening device: \\.\COM8
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)

please try below options to fix error (Unexpected packet: 4. Was expecting: 3)
1. Copy only singleimage.bin file from blankflash1 to blankfalsh 2 folder and run,
if not working then
2. revert above change, and only copy programmer.mbn in from blankflash1 to blankflash and run,
if not working then,
3. revert above changed and copy both programmer.mbn and singleimage.bin file from blankflash1 to blankflash2 and run.
please let me know the result.
21st April 2017, 04:07 PM |#11  
Member
Thanks Meter: 0
 
More
for moto g4 play
Quote:
Originally Posted by vijayjadhav_143

please try below options to fix error (Unexpected packet: 4. Was expecting: 3)
1. Copy only singleimage.bin file from blankflash1 to blankfalsh 2 folder and run,
if not working then
2. revert above change, and only copy programmer.mbn in from blankflash1 to blankflash and run,
if not working then,
3. revert above changed and copy both programmer.mbn and singleimage.bin file from blankflash1 to blankflash2 and run.
please let me know the result.

erro log
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.006s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)

---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------

Ta giving same error i need singleimage file for moto g4 play
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes