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

[giri.shiva]

Service center is 3rd party here and they wont touch bootloader unlocked phones - they check ESN/IMEI and wont touch. If you can suggest a place to send it to in North America that will take it - I would send it off today!

You talk to Motorola USA about this issue and send the device

 

[OrBy]

Motorola USA support keeps referring me to Canada support. If you have a direct contact for a USA service center I can send it to I would try that.

 

[kunch]

I read somewhere the in case of io error in blankflash press the power and vol down buttons so I tried and everytime I pressed the buttons the sound of disconnecting and reconnecting of external device comes from the computer and the log file in the blankflash folder increases. I don't know much about this stuff but I hope someone can help me fix my phone. The log file's link is below.

https://drive.google.com/file/d/0B_exu_JVrHgFOVM1dGR0dk54aVU/view?usp=sharing

 

[nate0]

I read somewhere the in case of io error in blankflash press the power and vol down buttons so I tried and everytime I pressed the buttons the sound of disconnecting and reconnecting of external device comes from the computer and the log file in the blankflash folder increases. I don't know much about this stuff but I hope someone can help me fix my phone. The log file's link is below.

https://drive.google.com/file/d/0B_exu_JVrHgFOVM1dGR0dk54aVU/view?usp=sharing

Same I/O error everyone else is getting.

 

[highjack2k]

work in progress! (not working yet)
Current status: does not work (but should!), exact reason unknown (to me).

I have tried a dozen programmer blobs with qboot and the qualcomm flasher utility. And nothing works.

The apply_patch_check update method is a stupid nonsense in the flasher, with the intention to lock up the phones. At least there is some check in the method. I did not find the source of motorola.update_gpt, which should be source of the brick.

I build my own images and multi boot devices since Android 2.1 on my HTC Desire. Unbricked my Xperia Z Ultra without recovery image. And all works fine. Till now. It's really a shame of Motorola to lock the phone. I have paid for it and cannot use it, because of such a ****ty company policy.

Thank you for your good intention. It was a great help while searching for information and solutions.

 

[Alekyxander Almeida]

Alguma novidade?

 

[RamboGYN12]

Moto Z Play

And the guys who got the blank flash pro moto z play my tbm was already brickou and no more and only appears as Qualcomm HS-USB QDLoader 9008 when it plugs into the computer?

 

[DerSal3m]

bricked another one

Just for u to know. I briked another one. How did it happen:
- Android 7.0.1 Installed -> April OTA Patch -> Reflash to Android 7.0.1 January Patch -> BL Unlock/Rooted -> few weeks on 7.0.1 Jan -> Reflash to 7.0.1 to remove root to get OTA back -> OTA April incoming -> Phone rebooting -> Update process -> Reboot -> phone bricked QLOADER 9008
I still had the loader.img from exactly this phone but it is not booting
So two phones are waiting for a new blank-flash file.

 

[b00tbu9]

Can we make this thread sticky and rename to How not to brick Moto z play... There are lots of people bricking the phone by wrongly flashing.

 

[giba_11]

And every day that passes only increases the number of Moto Z Play as paper weight ....

And by the way we will not have a solution so soon for this and unfortunately I will continue with my saved in the box in new state.

 

[nosiobadx]

I don´t know if this can help you guys:
You have to flash latest twrp
Boot into twrp
Sideload the kernel from this thread https://forum.xda-developers.com/moto-z-play/development/kernel-stock-kernel-f2fs-patched-t3546732
Afterward sideload again the ROM you want
Maybe it helps

 

[Roman1311]

I don´t know if this can help you guys:
You have to flash latest twrp
Boot into twrp
Sideload the kernel from this thread https://forum.xda-developers.com/moto-z-play/development/kernel-stock-kernel-f2fs-patched-t3546732
Afterward sideload again the ROM you want
Maybe it helps

hahah, yeeyy boy it helps)

 

[jrgomes91]

Moto z play bricked, does not start. Help me. Thank you

 

[DerSal3m]

That's not helping us. We cannot sideload if the phone only shows up as QLOADER 9008 ... fastboot is not working if it does that

I don´t know if this can help you guys:
You have to flash latest twrp
Boot into twrp
Sideload the kernel from this thread https://forum.xda-developers.com/moto-z-play/development/kernel-stock-kernel-f2fs-patched-t3546732
Afterward sideload again the ROM you want
Maybe it helps

 

[sp5it]

I googled "QLOADER 9008" and it seems a lot of phones different manufacturers were recovered from brick.
Did you read through?
MIke

 

[Silencer-22]

I googled "QLOADER 9008" and it seems a lot of phones different manufacturers were recovered from brick.
Did you read through?
MIke

Check:
http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/

 

[EspElement]

I am in the same boat here. I flashed the original 7.0 (Jan patch) from the soak test (7.1.1) and then proceeded with installing the OTA updates and it bricked on the first one. I suspect this is that April update you all are referring too...

---------- Post added at 02:48 PM ---------- Previous post was at 01:59 PM ----------

Can anyone help me understand how to get my device detected? Right now it sticks at detecting device then ERROR.

---------- Post added at 03:04 PM ---------- Previous post was at 02:48 PM ----------

Just for u to know. I briked another one. How did it happen:
- Android 7.0.1 Installed -> April OTA Patch -> Reflash to Android 7.0.1 January Patch -> BL Unlock/Rooted -> few weeks on 7.0.1 Jan -> Reflash to 7.0.1 to remove root to get OTA back -> OTA April incoming -> Phone rebooting -> Update process -> Reboot -> phone bricked QLOADER 9008
I still had the loader.img from exactly this phone but it is not booting
So two phones are waiting for a new blank-flash file.

Mine bricked very similar to this. I was shocked when I took the OTA and it was not turning on...

 

[EspElement]

**** Log buffer [000001] 2017-06-30_21:35:54 ****

[ -0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 70 (0x46)
[ 0.005] ...cpu.sn = 2524198637 (0x967436ed)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.007] ...filename = singleimage.pkg.xml
[ 0.009] Loading programmer
[ 0.009] ...filename = programmer.mbn
[ 0.010] Sending programmer
[ 0.220] Handling things over to programmer
[ 0.221] Identifying CPU version
[ 0.225] Waiting for firehose to get ready
[ 61.435] Waiting for firehose to get ready
[121.581] ...MSM8953 unknown
[121.581] Determining target secure state
[121.585] Waiting for firehose to get ready
[181.724] ...secure = no
[181.735] Waiting for firehose to get ready
[241.872] Configuring device...
[241.876] Waiting for firehose to get ready
[302.010] Waiting for firehose to get ready
[362.146] Waiting for firehose to get ready
[422.283] Waiting for firehose to get ready
[482.417] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[482.418] Check qboot_log.txt for more details
[482.419] Total time: 482.420s
[482.419]
[482.419] qboot version 3.40
[482.419]
[482.419] DEVICE {
[482.419] name = "\\.\COM4",
[482.419] flags = "0x64",
[482.419] addr = "0x61FE5C",
[482.419] sahara.current_mode = "0",
[482.419] api.buffer = "0x12CD020",
[482.419] cpu.serial = "2524198637",
[482.419] cpu.id = "70",
[482.419] cpu.sv_sbl = "0",
[482.419] cpu.name = "MSM8953",
[482.419] storage.type = "eMMC",
[482.419] sahara.programmer = "programmer.mbn",
[482.419] module.firehose = "0xF78A48",
[482.420] cpu.ver = "0",
[482.420] cpu.vername = "unknown",
[482.420] api.bnr = "0xE78450",
[482.420] }
[482.420]
[482.420]
[482.420] Backup & Restore {
[482.420] num_entries = 0,
[482.420] restoring = "false",
[482.420] backup_error = "not started",
[482.420] restore_error = "not started",
[482.420] }
[482.420]

It's much further than I've gotten before, that's for sure. Maybe if the singleimage.bin file can be decompressed, we can try using eMMC Software Download Tool from QPST?

I am getting the same thing here. I finally got it to connect. I changed ports like 100 times. Lol

 

[EspElement]

Guys,

What would I need to replace in my phone to fix it? The logic board? Could I use something that is in a Moto Z or something else possibly? I am looking for broken phones on eBay that I may be able to salvage to make one working one. I am hoping we can find a solution here soon instead though!

Thanks!

 

[EspElement]

I guess we are waiting for a new blank-flash on the next release?