[GUIDE] Moto G4 Plus HardBrick SOLVED - ULTIMATE UNBRICKING GUIDE

[echo92]

My phone oem is locked and imei number is 000000000000000. So please upload the factory files of gtp and boot loader as they donot require oem unlocked
Thank you a lot in advance

1) Please do not quote the entire opening post - it clutters up your post.
2)If you're looking for the September 2017 GPT and bootloader, please look in this post here: https://forum.xda-developers.com/showpost.php?p=74459614&postcount=173 As your device bootloader is locked, you can only flash the same bootloader/GPT version or newer patch levels.
3)Why is your IMEI 0000, is that after using the blankflash or did you attempt to flash other firmware?

 

[mkms2]

Not sure how IMEI is 000000

I am not sure how my device imei has got 00000. While trying to root the phone I softbricked the phone and later I install the stock ROM for my phone ( Android 6.0.1). After that I received an OTA update for 7.0.1 where the device got hardbricked. Later I flashed the blank flash file. Now I am unable to flash an other files after that. Will try the latest file in the above given link

 

[mkms2]

My device is back with all data

Thanks a ton bro, My anthene is back to life and I also have all the data as I didnot flash the latest ROM the update I had downloded while updating was noguat 7.0 and it has been installed sucessfully now.

Once again thanks a ton

 

[echo92]

Thanks a ton bro, My anthene is back to life and I also have all the data as I didnot flash the latest ROM the update I had downloded while updating was noguat 7.0 and it has been installed sucessfully now.

Once again thanks a ton

Good to hear you got your device working. I would strongly suggest to flash the latest stock ROM, which might be NPJS25.93-14-10 depending on your region/device, to reduce the chances of a further hard brick should you take OTA updates. By flashing the latest stock ROM, you should be able to bring your device firmware all up to the same patch level. You could flash the stock ROM without using 'fastboot erase userdata' to save your data.

At any rate, you will want to delete the stock Marshmallow or any stock Nougat ROMs you still have older than June 2017/Sept 2017 patch level, as you found out flashing them onto a device running newer stock Nougat firmware and then attempting to apply OTA updates will cause another hard brick. You were lucky in that the blankflash worked, however Motorola may update the bootloader in future which prevents the blankflash from working, until we get another leak (if we get leaks). Motorola does not officially release blankflashes - they'd require you to replace the motherboard which is about 70-80% of the device cost.

 

[mkms2]

Sure thanks for the update. Is September the latest ROM??? And even the IMEI numbers are back

 

[echo92]

Sure thanks for the update. Is September the latest ROM??? And even the IMEI numbers are back

As of writing, September 2017 should be the latest patch level for Nougat stock ROMs. If you're in India, Brazil, EU/UK and other territories NPJS25.93-14-10 is the latest build for our devices. You can find it here too: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

The GPT/bootloader you flashed were from the Sept 2017 NPJS25.93-14-10 stock ROM, hence why I'm advocating flashing the firmware to match. Else, if your system and bootloader are not of the same patch level, and your bootloader is newer than your stock system, applying OTA updates may hard brick you again. OTA updates appear to only check if your system is unmodified and the correct build to patch, and OTA updates appear to assume your bootloader is at the same patch level. Motorola appears to really not like you downgrading your device.

 

[mkms2]

Yep September is the last.Just flashed with September patches and now it says software is upto date in settings>phones>updates

Thanks once again

 

[nehreo]

yeaaahh!!

great job dude!!! my phone go back to life! thanks !!1641

 

[nazdravanu82]

MOTO G4 qualcom HS-USB QDloader 9008

My phone oem is locked and imei number is 000000000000000. So please upload the factory files of gtp and boot loader as they donot require oem unlocked
Thank you a lot in advance

Hello
Its any solution for XT 1622,the same problem??
qualcom HS-USB QDloader 9008

 

[Outfield303]

Hello
Its any solution for XT 1622,the same problem??
qualcom HS-USB QDloader 9008

it should work on your moto g4 becouse the g4 and g4+ both contains the same SOC,
can you tell me when and how your device was bricked?

 

[nykola5]

I get the following error when trying to revive:

Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.008] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.008] Check qboot_log.txt for more details
[ 4.009] Total time: 4.010s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error

C:\Users\tss11\Downloads\blankflash>pause
Presione una tecla para continuar . . .

The phone was updating me and was about to restart when it was completely turned off, wait a few seconds to see if it started, then notice that it did not turn on, press the power button with less volume for 30 to 2 minutes and it did not turn on, I let it rest for a while and I put it to load and nothing, then I saw myself in this post with the hopes of reviving it and having to flash the firmware and it is ok but what happens is what I say above, what solution do you give me? I already have the motorola drivers installed (I uninstalled them and reinstalled them) and I also downloaded the file again and continues like this

 

[PasswordUnder_]

Thanks a lot @siddhesh9146
You are my life savior​

 

[DemonMonkey112]

Thanks a Ton

Thanks a ton for providing this method to unbrick the device.
After this is done can i install OTA official updates.. will it cause any more problems and also how can i relock my bootloader?


Thanks!!

 

[Outfield303]

Thanks a ton for providing this method to unbrick the device.
After this is done can i install OTA official updates.. will it cause any more problems and also how can i relock my bootloader?


Thanks!!

Yes you can take OTA updates as long as you are on Latest Security patch and GPT+Bootloader are same. You can also re-lock the bootloader but there is no need to do that, you can take official updates without it

 

[aditya.addi]

Need an humanitarian help
Hey bro may you please provide us an brief instructions how to buid same blank flash file forr moto x force?
Thanks in advance

 

[strongst]

Need an humanitarian help
Hey bro may you please provide us an brief instructions how to buid same blank flash file forr moto x force?
Thanks in advance

It can't be build. It must be leaked from motorola since it's not public. Someone leaked it for g4, it's not build from a source like a rom.

 

[aditya.addi]

It can't be build. It must be leaked from motorola since it's not public. Someone leaked it for g4, it's not build from a source like a rom.

Hey Strongst! Thanks for replying.
One more doubt....when i open the main file of blank-flash that is known as singleimage.bin it's contains mainly 5-6 ( most of the single-image.bin) like
1. aboot.img
2. DDR.bin
3. rpm.img
4. sbl1.img
5. tz.img

(I attached a pics for support)
and above files we have managed from dump rom of working device.
Could you please explain it for us?
Your reply will be really appreciating to us
Thanks!!

 

[strongst]

Hey Strongst! Thanks for replying.
One more doubt....when i open the main file of blank-flash that is known as singleimage.bin it's contains mainly 5-6 ( most of the single-image.bin) like
1. aboot.img
2. DDR.bin
3. rpm.img
4. sbl1.img
5. tz.img

(I attached a pics for support)
and above files we have managed from dump rom of working device.
Could you please explain it for us?
Your reply will be really appreciating to us
Thanks!!

I'm not sure but these are should be partition dumps if I'm not wrong

 

[echo92]

Hey Strongst! Thanks for replying.
One more doubt....when i open the main file of blank-flash that is known as singleimage.bin it's contains mainly 5-6 ( most of the single-image.bin) like
1. aboot.img
2. DDR.bin
3. rpm.img
4. sbl1.img
5. tz.img

(I attached a pics for support)
and above files we have managed from dump rom of working device.
Could you please explain it for us?
Your reply will be really appreciating to us
Thanks!!

Those files are bootloader images if I recall, packaged into a singleimage.bin along with other files such as the programmer.mbn. As I understand it, the programmer.mbn is what gets sent to a device after the blankflash communicates with your device, to check whether the blankflash meets or exceeds the bootloader version.
If so, then the programmer begins flashing the bootloader files to repair your bootloader. If your bootloader is too new (and corrupted from a OTA update after downgrading), then the programmer would likely block the flash for security reasons. Thus, it seems it's not just having the up to date files, you also would need a newer programmer file for access and verification.

As strongst has already mentioned, we only get these leaked, as they have to be signed by Motorola for the bootloader to accept them. Unless you can find a Motorola engineer (or a member with such a contact) willing to let you have Moto X force blankflashes, or up to date factory firmware is available/leaked, I'm afraid the only resolution is a motherboard replacement. There's been limited success with using blankflashes from other Motorola devices, but typically those devices have very similar/same CPUs (e.g g5 plus, z play etc), and I don't know of other Motorola devices with the SD810 chip inside.

 

[Adriana lacosteyahve.serv]

i love youuuuuuuuuuuuu thankssssssssssss

your are the best thanks, 100000000thanks