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

giri.shiva

giri.shiva

Member
Jun 19, 2015
27
5
0
May 31, 2017 at 8:23 PM
vijayjadhav_143 said:
Please charge your mobile before start, you can keep mobile on charger for 2-3 hours, expecting it will get charged in that time.

I dont have Z play, but will try to locate if I find blankflash files for that and I have to search that on internet though :)
Click to expand...

i plugged in the charger for over night but i dont think it has charge in the battery
does it really charge ?
 
Z

Z-borg

Member
Sep 3, 2015
21
0
0
Jun 1, 2017 at 11:07 AM
Hi, I flashed blank-flash1.bat it rebooted my phone to fastboot I thought it was successful so I closed CMD window, but then when I flashed ATHENE_NPJ25.93-14 stock it gave me following error message -
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.069s

what should I do as phone is not booting.
 
E

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Jun 1, 2017 at 6:12 PM
Z-borg said:
Hi, I flashed blank-flash1.bat it rebooted my phone to fastboot I thought it was successful so I closed CMD window, but then when I flashed ATHENE_NPJ25.93-14 stock it gave me following error message -
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.069s

what should I do as phone is not booting.
Click to expand...
Looks like you need the latest firmware to flash: try flashing the NPJS25.93-14.4 (March 2017 security patch) firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
 
  • Like
Reactions: Z-borg
A

Arrow_Strider

Member
Jun 26, 2014
21
2
0
Jun 16, 2017 at 10:26 AM
Hello OP!

I will try your solution with my Moto G2 XT1069.

I'll keep you posted about results.

Just hope this works, i really, REALLY need this to work as i only have a crappy spare phone.

Wish me luck!
 
A

Arrow_Strider

Member
Jun 26, 2014
21
2
0
Jun 16, 2017 at 1:40 PM
Well, it was a fool's hope i've got... To no avail.

I keep attached myself to the sentence: "Should work for all Qualcomm devices(except hardware failure).", but that is not true at least for me.

Keep getting singleimage error. Tried lots of combinations.

I don't know what to do anymore. It's a nightmare i'm facing for over 4 months. I don't have money to buy another phone and i'm desperate.

Don't know what else can i do.

---------- Post added at 01:40 PM ---------- Previous post was at 01:10 PM ----------

C:\Users\Arrow_Strider\Desktop\blank-flash\blankflash3>.\qboot.exe blank-flash
opening device: \\.\COM6
OKAY [ 5.079s]
greeting device for command mode
OKAY [ 1.486s]
identifying device
...serial = 0x77C0243
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.000s]
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.016s]
sending programmer
OKAY [ -0.000s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
 
I

icarorgs

New member
Jul 6, 2017
1
0
0
Jul 6, 2017 at 12:46 PM
please help i keep getting this error, moto g4 plus xt1640


C:\Users\Icaro\Downloads\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 0.016] ...cpu.id = 2418 (0x972)
[ 0.016] ...cpu.sn = 42789970 (0x28cec52)
[ 0.016] Opening singleimage
[ 0.031] Loading package
[ 0.031] ...filename = singleimage.pkg.xml
[ 0.031] Loading programmer
[ 0.031] ...filename = programmer.mbn
[ 0.031] Sending programmer
[ 0.250] Handling things over to programmer
[ 0.250] Identifying CPU version
[ 0.265] Waiting for firehose to get ready
[ 9.821] ReadFile() failed, GetLastError()=0
[ 9.915] ReadFile() failed, GetLastError()=0
[ 29.164] ReadFile() failed, GetLastError()=0
[ 38.093] ReadFile() failed, GetLastError()=0
[ 61.358] Waiting for firehose to get ready
 
baunthiyal

baunthiyal

Senior Member
Jan 16, 2015
229
64
28
26
Jaipur
Jul 7, 2017 at 11:52 AM
Waiting for firehose

Hello. I followed your tutorial and flash blankflash1. It is stuck at Waiting for firehose to get ready.
Please check attachment.
Edit - I received a Failure message.
Edit2 - MSM8952 unknown
Edit3 - Waiting for firehorse to get ready
And the cycle repeats.
 

Attachments

Last edited:
  • Like
Reactions: ankur205 and S a K
M

Mdsp9070

New member
Jul 9, 2017
1
0
0
Campos dos Goytacazes
Jul 9, 2017 at 2:54 AM
Didn't work :(

Hi, i'm brazilian and i flashed the stock ROM for Moto G4 Plus android 6.0.1
Ok, i did that before, and i only did that 'cause i came back from Ressuction Remix Rom and i intended to go to the stock ROM Nougat(7.0), however, to do that, i need to flash the Stock ROM 6.0.1 and install a zip of the OTA update on the Stock Recovery. Going onr, this time i guess i hardbricked my phone (XT1640). I got flash the stock ROM 6.0.1 and the OTA zip to, moreover when i erased the cache partition and Restart the system, the phone turned off and Has not started anymore. I installed the drivers and i did all steps but had problem with the blankflash.bat, i had to download one for the android Nougat NPJ95.93-11 (i don't know if this it's the correct version) and every time i run the .bat i have the same error:

C:\Users\Matheus\Desktop\Jogos e programas\Android 5.1.1, 6.0.1 e 7.0\Moto g4 Plus\Hardbrick\athene_blankflash-NPJ95.93-11\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.021] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.021] Check qboot_log.txt for more details
[ 4.021] Total time: 4.036s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error


The maxium i got was other error: Wainting for firehose and after 28 seconds another message appears: press any key to continue, Thanks for reading my clemency. ;)

So, i got a new error when i downloaded other blankflash.bat

C:\Users\Matheus\Desktop\Jogos e programas\Android 5.1.1, 6.0.1 e 7.0\Moto g4 Plus\Hardbrick\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.004s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.003s]
identifying device
...serial = 0x10A9D1D
...chip-id = 0x972
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.008s]
validating files
OKAY [ 0.003s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.005s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
 
Last edited:
D

Draconfla

Member
Jul 9, 2017
21
1
0
Juiz de Fora - MG
Jul 9, 2017 at 7:58 PM
baunthiyal said:
Hello. I followed your tutorial and flash blankflash1. It is stuck at Waiting for firehose to get ready.
Please check attachment.
Edit - I received a Failure message.
Edit2 - MSM8952 unknown
Edit3 - Waiting for firehorse to get ready
And the cycle repeats.
Click to expand...

Eu também estou com esse problema quando eu rodo o blankflash1 o meu é o moto g4 xt1626 é o com tv

I also have this problem when I run the blankflash1 mine is the moto g4 xt1626 is the with tv.

Alguém conseguiu recuperar esse modelo xt1626?

Has anyone managed to recover this xt1626 model?
 
Last edited:
baunthiyal

baunthiyal

Senior Member
Jan 16, 2015
229
64
28
26
Jaipur
Jul 11, 2017 at 4:31 AM
From what I understand, those of us who flashed the 14-8 OTA and then downgraded will need a new singleimage.bin. According to what I read online, the singleimage.bin contains 5 partitions - sbl, ddr, aboot, rpm and TZ (this information comes from Moto G (falcon) XDA forums).
I may be wrong about the .bin file, but the fact of the matter is, unless we have an updated singleimage, our devices are bricked.
 
  • Like
Reactions: Draconfla and champagne66601
E

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Jul 11, 2017 at 1:13 PM
baunthiyal said:
From what I understand, those of us who flashed the 14-8 OTA and then downgraded will need a new singleimage.bin. According to what I read online, the singleimage.bin contains 5 partitions - sbl, ddr, aboot, rpm and TZ (this information comes from Moto G (falcon) XDA forums).
I may be wrong about the .bin file, but the fact of the matter is, unless we have an updated singleimage, our devices are bricked.
Click to expand...
That would make sense, given the blank-flash we have access to is from NPJ25.93-11 (the November 2016 patch), which wouldn't be as up to date. I noticed that, from the logs, the CPU isn't detected properly (MSM8952 unknown as opposed to MSM8952 1.1 in the opening post), which might be as a result too.

Regardless, I hope there's a new blank-flash for NPJS25.93-14-8 soon, unfortunately as I understand it, it's a file that Motorola has to generate and cryptographically sign, so when it arrives is anyone's guess :(
 
D

Draconfla

Member
Jul 9, 2017
21
1
0
Juiz de Fora - MG
Jul 11, 2017 at 2:09 PM
echo92 said:
That would make sense, given the blank-flash we have access to is from NPJ25.93-11 (the November 2016 patch), which wouldn't be as up to date. I noticed that, from the logs, the CPU isn't detected properly (MSM8952 unknown as opposed to MSM8952 1.1 in the opening post), which might be as a result too.

Regardless, I hope there's a new blank-flash for NPJS25.93-14-8 soon, unfortunately as I understand it, it's a file that Motorola has to generate and cryptographically sign, so when it arrives is anyone's guess :(
Click to expand...
It makes sense what you said even though the processor (MSM8952) was the same. We have to wait for a new updated .bin file.

After 2 years I was able to recover my xt1033 with another forum post.

What gives me the most anger is that this comes from the bike g 1 and the motorola does not release these files. At the time that gave this same problem in my XT1033 I sent for assistance and they said that it was a problem on the card and that there was no repair, look only long after I managed to revive it (XT1033).

I hope this moto g4 .bin file is released as fast as possible. :fingers-crossed:
 
Pratham Nathyal

Pratham Nathyal

Senior Member
May 30, 2015
106
29
0
Jammu
Jul 11, 2017 at 7:54 PM
baunthiyal said:
Hello. I followed your tutorial and flash blankflash1. It is stuck at Waiting for firehose to get ready.
Please check attachment.
Edit - I received a Failure message.
Edit2 - MSM8952 unknown
Edit3 - Waiting for firehorse to get ready
And the cycle repeats.
Click to expand...

Have the ditto same screen after following that tutorial. Man. What to do?
@vijayjadhav_143 please help.

http://www.droidsavvy.com/unbrick-qualcomm-mobiles/ and please tell can this method work? Should I try this?

And if not. Please do something to help me. I bricked my only device.
View attachment 4208770
View attachment qboot_log.txt
 
Last edited:
baunthiyal

baunthiyal

Senior Member
Jan 16, 2015
229
64
28
26
Jaipur
Jul 12, 2017 at 3:01 AM
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone