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

[litojosh]

Help Please!!

Thank you for the information. I am having trouble with my moto g4 plus xt1641 - baseband: latam_cust (i'm from Peru, sorry for my english ) The situation is: I accidentally dropped my phone in water and after some days trying to get the phone completely dry I realized it got stacked in a bootloop. After that, I did a lot of research and I went from being a totally ignorant to having a decent level of understanding on the android world. To sum up, I find myself stacked with a bricked device that doesn't let me get over the booting up process and apparently there's no way for me to install a stock firmware because I have the OEM Locked.

Question: Is there any way for me to get my OEM Unlocked, so I can unlock the bootloader??. BTW. after many attempts applying different stock ROMs for the XT1641 version, I just realized every time I reboot my phone into Bootloader mode, the baseband section shows "Baseband: <not found>". Thanks in advance for any help given. I might not be an expert but I will do my best to understand and follow any instructions given.

 

[siredux]

Thank you for the information. I am having trouble with my moto g4 plus xt1641 - baseband: latam_cust (i'm from Peru, sorry for my english ) The situation is: I accidentally dropped my phone in water and after some days trying to get the phone completely dry I realized it got stacked in a bootloop. After that, I did a lot of research and I went from being a totally ignorant to having a decent level of understanding on the android world. To sum up, I find myself stacked with a bricked device that doesn't let me get over the booting up process and apparently there's no way for me to install a stock firmware because I have the OEM Locked.

Question: Is there any way for me to get my OEM Unlocked, so I can unlock the bootloader??. BTW. after many attempts applying different stock ROMs for the XT1641 version, I just realized every time I reboot my phone into Bootloader mode, the baseband section shows "Baseband: <not found>". Thanks in advance for any help given. I might not be an expert but I will do my best to understand and follow any instructions given.

Hi, sorry to hear that... You can flash stock firmware without having the need to unlock bootloader, unless you want to downgrade of course. Notice that "Allow OEM Unlock" must be enabled in Developer settings in order to complete bootloader unlock process which as you can realise, it's not an option right now. PM me for more details if you want to :good:

 

[jayeshaupe90]

nt detecting my device

---------- Post added at 10:34 PM ---------- Previous post was at 09:49 PM ----------

it is detecting as fastboot s

 

[rajatgupta1998]

nt detecting my device

---------- Post added at 10:34 PM ---------- Previous post was at 09:49 PM ----------

it is detecting as fastboot s

Uninstall useless drivers and install the proper ones. After that see it they have an update, else manually update.

 

[drfranz]

I have successfully recovered my dead/hard brick moto g4 plus mobile using below process.
Also let me know if it help

@vijayjadhav_143 Thank you, followed your guide and managed to unbrick my Moto Z 1650-3 (with blankflash.zip).

 

[jayeshaupe90]

uninstall useless drivers and install the proper ones. After that see it they have an update, else manually update.

uninstalled all the drivers...still it is detecting as fastboot s

 

[Btrusa]

Where do you get the G4's Programmer.mbn from?

 

[vijayjadhav_143]

Good to know that it helped

@vijayjadhav_143 Thank you, followed your guide and managed to unbrick my Moto Z 1650-3 (with blankflash.zip).

That's great, Congratulations. Also good to know that it helped at least someone, my writing in stackoverflow didn't get waste
Thanks for sharing.

 

[vijayjadhav_143]

Where do you get the G4's Programmer.mbn from?

those are blank or place-holder files. Those are used to bring your mobile from hardbrick to softbrick condition. One user is able to unbrick his using Moto Z, it should work for you also.

 

[drfranz]

That's great, Congratulations. Also good to know that it helped at least someone, my writing in stackoverflow didn't get waste
Thanks for sharing.

Far from it

 

[JoverDroid]

Help me

Hello everyone.
After using this tutorial my smartphone has a generic bootloader screen and with locked status, it does not start at all. How to solve this ??? I found a tutorial for the maxx bike and I think for the g4 bike more would be something like that, but I did not find the files needed. Below I will leave the maxx moto tutorial, so you can see how it was done, and maybe help me. (I can not post links)

 

[vijayjadhav_143]

Hello everyone.
After using this tutorial my smartphone has a generic bootloader screen and with locked status, it does not start at all. How to solve this ??? I found a tutorial for the maxx bike and I think for the g4 bike more would be something like that, but I did not find the files needed. Below I will leave the maxx moto tutorial, so you can see how it was done, and maybe help me. (I can not post links)

if you have got generic bootloader screen it means you completed major step, now you can flash stock ROM. please search for flashing stock rom and you will get lots of helping url/links, you can follow it.

 

[giri.shiva]

For moto z play xt1635-02

its showing this error please help me out


C:\Users\Shiva Giri\Desktop\blankflash>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.006] ...cpu.id = 70 (0x46)
[ 0.007] ...cpu.sn = 3381611295 (0xc98f4b1f)
[ 0.007] Opening singleimage
[ 0.009] Loading package
[ 0.021] Failed identify board. Wrong package?
[ 0.021] ERROR: error loading package
[ 0.021] Check qboot_log.txt for more details
[ 0.021] Total time: 0.025s
FAILED: qb_flash_singleimage()->error loading package

---------- Post added at 05:41 PM ---------- Previous post was at 05:15 PM ----------

this shows up when i copied singleimage.bin from blankflash1 to blankflash2


C:\Users\Shiva Giri\Desktop\blankflash2>.\qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ 0.005s]
greeting device for command mode
OKAY [ 0.004s]
identifying device
...serial = 0xC98F4B1F
...chip-id = 0x46
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.014s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.006s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)

 

[JoverDroid]

if you have got generic bootloader screen it means you completed major step, now you can flash stock ROM. please search for flashing stock rom and you will get lots of helping url/links, you can follow it.

Thank you vijayjadhav_143, I managed to revive my smartphone, I flashed the last rom stock he had. Which was NPJS 25.93-14-4, I tried to flash older ones like NPJS 25.93-14 and it did not work. But in the end I got out of a hard brick.

 

[vijayjadhav_143]

Thank you vijayjadhav_143, I managed to revive my smartphone, I flashed the last rom stock he had. Which was NPJS 25.93-14-4, I tried to flash older ones like NPJS 25.93-14 and it did not work. But in the end I got out of a hard brick.

Congratulations!!! Good to know

 

[vijayjadhav_143]

its showing this error please help me out


C:\Users\Shiva Giri\Desktop\blankflash>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.006] ...cpu.id = 70 (0x46)
[ 0.007] ...cpu.sn = 3381611295 (0xc98f4b1f)
[ 0.007] Opening singleimage
[ 0.009] Loading package
[ 0.021] Failed identify board. Wrong package?
[ 0.021] ERROR: error loading package
[ 0.021] Check qboot_log.txt for more details
[ 0.021] Total time: 0.025s
FAILED: qb_flash_singleimage()->error loading package

---------- Post added at 05:41 PM ---------- Previous post was at 05:15 PM ----------

this shows up when i copied singleimage.bin from blankflash1 to blankflash2


C:\Users\Shiva Giri\Desktop\blankflash2>.\qboot.exe blank-flash
opening device: \\.\COM3
OKAY [ 0.005s]
greeting device for command mode
OKAY [ 0.004s]
identifying device
...serial = 0xC98F4B1F
...chip-id = 0x46
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.014s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.006s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)

did you try with only singleimage file copying into other folder or with programmer.mbn file also? not sure, generally one of three blankflash should work. Could you please try with different combinations , there are 3 blankflash folders, each with 2 files(singleimage/programmer), there might be 6 combinations..

 

[giri.shiva]

not working

did you try with only singleimage file copying into other folder or with programmer.mbn file also? not sure, generally one of three blankflash should work. Could you please try with different combinations , there are 3 blankflash folders, each with 2 files(singleimage/programmer), there might be 6 combinations..

already tried but nothing works
can you create z play blankfalsh files if yes then please help us there are many people who are suffering from this same problem

if my phone's battery is completely dead then also i can try to flash blankfalsh files ??

 

[giri.shiva]

already tried but nothing works
can you create z play blankfalsh files if yes then please help us there are many people who are suffering from this same problem

if my phone's battery is completely dead then also i can try to flash blankfalsh files ??

C:\Users\Shiva Giri\Documents\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.003s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM4
opening device: \\.\COM4
opening device: \\.\COM4
OKAY [ 0.005s]
greeting device for command mode
OKAY [ 0.021s]
identifying device
...serial = 0xC98F4B1F
...chip-id = 0x46
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.035s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.005s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)




what does this log mean ? explain please

 

[vijayjadhav_143]

charge mobile full before start

already tried but nothing works
can you create z play blankfalsh files if yes then please help us there are many people who are suffering from this same problem

if my phone's battery is completely dead then also i can try to flash blankfalsh files ??

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

 

[vijayjadhav_143]

C:\Users\Shiva Giri\Documents\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.003s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM4
opening device: \\.\COM4
opening device: \\.\COM4
OKAY [ 0.005s]
greeting device for command mode
OKAY [ 0.021s]
identifying device
...serial = 0xC98F4B1F
...chip-id = 0x46
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.035s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.005s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)




what does this log mean ? explain please

I am not sure about error .
Also I see blankflash from 2 or 3 folder/zip, using other/old qboot.exe utility, as it doesnt print "Motorola qboot utility version 3.40" in log when executed, please try to copy qboot.exe file from blankflash1 to blankflash 2 /blankflash 3 and try again.

I am sorry but "try and check"is the only option we have.