[GUIDE] Unbrick MOTO Z Play (not working yet)

[SherlockDk]

Can you at least get to TWRP when it boots?

No, only white led is blinking when plugging usb cable or charger.

 

[yssie]

No, only white led is blinking when plugging usb cable or charger.

Have you tried to boot it into bootloader? Power buttom + volume down at the same time.

 

[SherlockDk]

Have you tried to boot it into bootloader? Power buttom + volume down at the same time.

Yes. I've tried basic level to the middleman. I am looking forward to the new blank.

 

[brheno]

not working yet, on hold ....

Good afternoon.

I am from Brazil and I have a Moto Z Play XT1635-02 and downgraded from Android 7 to 6 and until then, I did the bootloader, root and installed TWRP and followed dowgrade procedures.

The problem happened after the downgrade removed the root I reinstalled the original recovery and downloaded through the mobile the update of the android January 7 via ota and after downloading began the installation and when restarting the cell phone he died and did not call any more and when connecting On the computer only the message in the device manager "Qualcomm HS-USB QDLoader 9008" no solution for now to resuscitate the device?

If someone has the solution and can help, thank you.

I'm having the same problem, it was in the February 1, 7.1.1 release and I unlocked it to put the 7.1.1 version of December and so put the 8.0 but in the end my z play was caught in the white light.
I already used the 2017 version files and it does not work.
I need updated with the blank flash version of February 2018 or an already updated 8.0

I was charged 200 for the repair. I'd rather wait.

 

[rafikowy]

I'm having the same problem, it was in the February 1, 7.1.1 release and I unlocked it to put the 7.1.1 version of December and so put the 8.0 but in the end my z play was caught in the white light.
I already used the 2017 version files and it does not work.
I need updated with the blank flash version of February 2018 or an already updated 8.0

I was charged 200 for the repair. I'd rather wait.

I faced the same problem... How long have you been waiting for repair? And you are saying 200 what - american dollars?

 

[SherlockDk]

I'm having the same problem, it was in the February 1, 7.1.1 release and I unlocked it to put the 7.1.1 version of December and so put the 8.0 but in the end my z play was caught in the white light.
I already used the 2017 version files and it does not work.
I need updated with the blank flash version of February 2018 or an already updated 8.0

I was charged 200 for the repair. I'd rather wait.

My friend, I'm from Brazil too. Those two hundred were charged by the authorized motorola? In Reais?

 

[brheno]

Quote:

My friend, I'm from Brazil too. Those two hundred were charged by the authorized motorola? In Reais?

No, I was not authorized, I know I will lose the guarantee. So it's best to wait.
I've been a week with this problem. and without cell phone

---------- Post added at 02:17 AM ---------- Previous post was at 02:11 AM ----------

I faced the same problem... How long have you been waiting for repair? And you are saying 200 what - american dollars?

No, in real Brazil.
by a guy who can solve it and do it with the lock or without the lock.
I saw in a post someone saying thank you for the service, and out of curiosity I asked how much it would be.

 

[rafikowy]

No, in real Brazil.
by a guy who can solve it and do it with the lock or without the lock.
I saw in a post someone saying thank you for the service, and out of curiosity I asked how much it would be.

Could you please send me this guy's email/xda profile or something?

BTW: My MZP already went to official Motorola service (in Poland). I'm gonna get an expertise tomorrow so I will let you know how much this mistake costs...

 

[brheno]

quote

Could you please send me this guy's email/xda profile or something?

BTW: My MZP already went to official Motorola service (in Poland). I'm gonna get an expertise tomorrow so I will let you know how much this mistake costs...

[email protected]


this was the email he provided.

 

[SherlockDk]

How to work on a blankflash file myself? How can I help you?

I would like to work on building a blankflash for the z play bike. To try to solve this.

 

[LosthSec]

I have the same problem...

 

[rafikowy]

Look at my case with hard bricking... If this is how Moto solves such problems, I'll never ever buy any Moto...
https://forum.xda-developers.com/moto-z-play/how-to/warning-mzp-hard-bricked-repaired-t3774307

 

[KillerDogs]

Somebody please tell me that you found the solution

 

[[email protected]]

I had a problem I was in Soak 3 and I did downgrade to 7.1.1 I lost the imei and I went back to Soak 1 and my moto Z play went off (hardbrick) and or I could recover it there is some solution

tengo un problema estaba en soak 3 e hice downgrade a 7.1.1 perdi el imei y volvi a soak 1 y mi moto z play se apago (hardbrick) y o eh podido recuperarlo existe alguna solucion

 

[aamszia]

< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM26
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 70 (0x46)
[ -0.000] ...cpu.sn = 1052478297 (0x3ebb8b59)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 1.019] ERROR: sahara_download()->IO error
[ 1.019] Check qboot_log.txt for more details
[ 1.019] Total time: 1.019s
FAILED: qb_flash_singleimage()->sahara_download()->IO error

D:\Motorola\ADDISON\blankflash_NDNS26.118-23-12-7>pause

 

[rafikowy]

< waiting for device >
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM26
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 70 (0x46)
[ -0.000] ...cpu.sn = 1052478297 (0x3ebb8b59)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 1.019] ERROR: sahara_download()->IO error
[ 1.019] Check qboot_log.txt for more details
[ 1.019] Total time: 1.019s
FAILED: qb_flash_singleimage()->sahara_download()->IO error

D:\Motorola\ADDISON\blankflash_NDNS26.118-23-12-7>pause

The only thing you can do now is to go to the service center... Your phone is hard bricked.

 

[Jaderalves]

The only thing you can do now is to go to the service center... Your phone is hard bricked.

only wait going blankflash for this version ,As soon as Oreo comes out the blankflash is released together probably

 

[echo92]

only wait going blankflash for this version ,As soon as Oreo comes out the blankflash is released together probably

Depends on if a factory image of Oreo gets leaked (not the fastboot image), which may contain the blankflash.

If not, then you'd have to wait for a leak of the Oreo blankflash.

If neither appear, then the only recourse would be a service repair.

 

[Fire21]

Yeah, for those in need of a recap:

1) Connect the bricked phone to your PC and use this blankflash: http://cloud.vache-android.com/Moto/albus/blankflash/
2) Once you boot to the bootloader, flash these files: https://drive.google.com/file/d/0B7X6bQHmiX_BY29Damx5ejEyX1U/view

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader

3) Flash 7.0 ROM like you normally would, but WITHOUT replacing the files flashed previously.
4) Profit

If you wanna use stock, don´t update it or it will brick again (we need to wait for a new release to be able to fix that).
My recommendation: use Lineage and forget about it bricking ever again.

Many thanks! I got my Moto Z Play today back to live with your blankflash

EDIT: Reason for my brick is the downgrade back to 6.0 from 7.1.1 that i made and used OTA updates.

 

[echo92]

Many thanks! I got my Moto Z Play today back to live with your blankflash

EDIT: Reason for my brick is the downgrade back to 6.0 from 7.1.1 that i made and used OTA updates.

Yeah, you cannot safely downgrade and use OTA updates, especially with downgrading from 7.1.1 to 6.0 - the downgrade appears to work okay, but you still have your newer bootloader from Nougat. As such, when you try to apply a Marshmallow OTA - or Nougat OTA that's much older than your bootloader - you'll likely have the OTA corrupt your newer bootloader and get a hard brick.

Luckily you were able to fix it, just bear in mind that if you do downgrade, please do not use OTA updates. Only use stock firmware to update.