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

leo88sandy · Aug 8, 2017 at 7:43 AM

sidhya1441 said:
sry wrong rpl...

its ok, lets us know

yurdrekz · Aug 8, 2017 at 3:53 PM

Same here, Blank Flash blocked by June update.
I bought my Moto G4 Plus on the motorola website, i tried the warranty, even if i knew that the warranty was avoid due to bootloader unlock.

I contacted the Motorola Support, told me to send my phone thanks to a paid DHL.
My phone came back with a intervention report : "Software modification attempt. Product not under warranty anymore. No intervention."

We must be patient now.

suryaprakash99 · Aug 8, 2017

vijayjadhav_143 said:
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/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).

is my motherboard dead if this dosent work
Waiting for firehose to get ready
this comand continously appers

Outfield303 · Aug 8, 2017 at 10:31 PM

leo88sandy said:
mujhe to only 6000 bola

which city?

suryaprakash99 · Aug 9, 2017 at 2:46 AM

vijayjadhav_143 said:
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/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).

my device got turned off during an update and led blinks when connected to charger does this process work

leo88sandy · Aug 9, 2017 at 7:19 AM

siddhesh9146 said:
which city?

Agartala

Cooltango26 · Dec 12, 2014 11 0 0

doesnot detect my device

mostwanted4evah · Jul 20, 2016 8 1 0

vijayjadhav_143 said:
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.

i didnt find programmer.mbn in zip ..?

mostwanted4evah · Jul 20, 2016 8 1 0

leo88sandy said:
must let us know bro plz

---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------

r u Vaibhav Mandavi ?

i am vaibhav

---------- Post added at 05:50 PM ---------- Previous post was at 05:47 PM ----------

yurdrekz said:
Same here, Blank Flash blocked by June update.
I bought my Moto G4 Plus on the motorola website, i tried the warranty, even if i knew that the warranty was avoid due to bootloader unlock.

I contacted the Motorola Support, told me to send my phone thanks to a paid DHL.
My phone came back with a intervention report : "Software modification attempt. Product not under warranty anymore. No intervention."

We must be patient now.

bro if that the case we all moto g4 plus user with same problem are ****ed up ..

leo88sandy · Aug 9, 2017 at 6:55 PM

Guys MotoG5 Plus le leta hu, or kitna wait karu g4+ ka thik honeka, ???

S a K · Feb 12, 2014 5 0 0

i got this error moto g4 plus plzzz.. help me

Identifying cpu unknown
Secure no
Waiting for filehose to get ready
Error

that_psychopath · Mar 18, 2017 7 0 0

i am using windows xp and i dont know how to get in test mode

amith.chennai · Aug 11, 2017 5 1 0

blank flash failed pls reply

F:\SOFTWARE\mobile software\blankflash1\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2418 (0x972)
[ 0.000] ...cpu.sn = 14555574 (0xde19b6)
[ 0.000] Opening singleimage
[ 0.172] Loading package
[ 0.172] ...filename = singleimage.pkg.xml
[ 0.188] Loading programmer
[ 0.188] ...filename = programmer.mbn
[ 0.188] Sending programmer
[ 0.412] Handling things over to programmer
[ 0.412] Identifying CPU version
[ 0.412] Waiting for firehose to get ready
[ 60.753] Waiting for firehose to get ready
[121.273] ...MSM8952 unknown
[121.273] Determining target secure state
[121.276] Waiting for firehose to get ready
[181.686] ...secure = no
[181.702] Flashing GPT...
[181.780] Flashing partition:0 with gpt_main0.bin
[181.780] Initializing storage
[181.780] Waiting for firehose to get ready
[242.314] Configuring device...
[242.314] Waiting for firehose to get ready
[302.445] Waiting for firehose to get ready
[362.570] Waiting for firehose to get ready
[422.697] Waiting for firehose to get ready
[482.815] 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
[482.816] Check qboot_log.txt for more details
[482.817] Total time: 482.817s
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

F:\SOFTWARE\mobile software\blankflash1\blankflash>pause
Press any key to continue . . .

pls reply blank flash not have been done. i just update to 7 and this happen.

echo92 · Aug 11, 2017 at 2:38 PM

amith.chennai said:
pls reply blank flash not have been done. i just update to 7 and this happen.

Can you describe what happened up to this point please? You described updating to 7, what ROM were you on before, and had you been on the March or June 2017 stock Nougat ROM previously?

amith.chennai · Aug 11, 2017 5 1 0

blankflash failed pls help

F:\SOFTWARE\mobile software\blankflash1\blankflash>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM4
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 2418 (0x972)
[ -0.000] ...cpu.sn = 14555574 (0xde19b6)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ -0.000] ...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.250] Waiting for firehose to get ready
[ 60.674] Waiting for firehose to get ready
[120.793] ...MSM8952 unknown
[120.793] Determining target secure state
[120.798] Waiting for firehose to get ready
[180.923] ...secure = no
[180.938] Flashing GPT...
[180.938] Flashing partition:0 with gpt_main0.bin
[180.938] Initializing storage
[180.954] Waiting for firehose to get ready
[241.424] Configuring device...
[241.424] Waiting for firehose to get ready
[301.883] Waiting for firehose to get ready
[362.401] Waiting for firehose to get ready
[422.912] Waiting for firehose to get ready
[483.261] 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.262] Check qboot_log.txt for more details
[483.262] Total time: 483.262s
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

F:\SOFTWARE\mobile software\blankflash1\blankflash>pause
Press any key to continue . . .

echo92 · Aug 11, 2017

amith.chennai said:
F:\SOFTWARE\mobile software\blankflash1\blankflash>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM4
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 2418 (0x972)
[ -0.000] ...cpu.sn = 14555574 (0xde19b6)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ -0.000] ...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.250] Waiting for firehose to get ready
[ 60.674] Waiting for firehose to get ready
[120.793] ...MSM8952 unknown
[120.793] Determining target secure state
[120.798] Waiting for firehose to get ready
[180.923] ...secure = no
[180.938] Flashing GPT...
[180.938] Flashing partition:0 with gpt_main0.bin
[180.938] Initializing storage
[180.954] Waiting for firehose to get ready
[241.424] Configuring device...
[241.424] Waiting for firehose to get ready
[301.883] Waiting for firehose to get ready
[362.401] Waiting for firehose to get ready
[422.912] Waiting for firehose to get ready
[483.261] 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.262] Check qboot_log.txt for more details
[483.262] Total time: 483.262s
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

F:\SOFTWARE\mobile software\blankflash1\blankflash>pause
Press any key to continue . . .

Without knowing more about what happened to your device, it looks like you'll need to take your device to a service centre or repair shop to have its motherboard changed (from other reports, I've read it's anywhere between 6000-10000 rupees), or save up for a new device. You could try to hard reboot your device (hold the power button for 2-3 minutes) then attempt to boot, or hold down the power and volume down keys and hope you can boot to bootloader.

Currently, there appear to be no other ways to rescue a hard bricked device if this blankflash doesn't work. Sorry, I wish I had better news - for now, a hard brick is unrecoverable.

leo88sandy · Aug 12, 2017 at 5:35 AM

echo92 said:
Can you describe what happened up to this point please? You described updating to 7, what ROM were you on before, and had you been on the March or June 2017 stock Nougat ROM previously?

Can u help me?

VivekBhagat · Aug 12, 2017 at 6:05 AM

echo92 said:
Can you describe what happened up to this point please? You described updating to 7, what ROM were you on before, and had you been on the March or June 2017 stock Nougat ROM previously?

June

echo92 · Aug 12, 2017 at 1:38 PM

VivekBhagat said:
June

Oh, so you were on the June stock ROM update, downgraded to Marshmallow and then updated, is that right?

If so, that's not good, as the June 2017 update is what caused your device to hard brick, and as I mentioned above, there's no solution currently except to replacing your motherboard/saving up for a new device. You could wait for a new blank flash, but they have to be made and signed by Motorola, and since we're not supposed to have these tools (and also they don't support downgrading), I imagine they'll just refer you to a service centre. If Android O is released, then we might see a full firmware produced and leaked, which may have the blank flash (as we saw for Nougat), but that's just speculation on my part.

---------- Post added at 01:38 PM ---------- Previous post was at 01:37 PM ----------

leo88sandy said:
Can u help me?

What do you need help with?

leo88sandy · Aug 12, 2017 at 3:24 PM

echo92 said:
Oh, so you were on the June stock ROM update, downgraded to Marshmallow and then updated, is that right?

If so, that's not good, as the June 2017 update is what caused your device to hard brick, and as I mentioned above, there's no solution currently except to replacing your motherboard/saving up for a new device. You could wait for a new blank flash, but they have to be made and signed by Motorola, and since we're not supposed to have these tools (and also they don't support downgrading), I imagine they'll just refer you to a service centre. If Android O is released, then we might see a full firmware produced and leaked, which may have the blank flash (as we saw for Nougat), but that's just speculation on my part.

---------- Post added at 01:38 PM ---------- Previous post was at 01:37 PM ----------

What do you need help with?

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.

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

Senior Member

New member

Member

Senior Member

Member

Senior Member

Member

Member

Member

Senior Member

Member

Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member