[GUIDE] Unbrick MOTO Z Play (not working yet)
- Thread starter benzinerwin
- Start date
I have unbricked my phone thanks to you. I have one more question: Is there any way to re-lock bootloader?
You are welcome. Relock bootloader is not possible.
But unlocked bootloader is not any problem. OTA updates is working with unlocked bootloader as well.
But unlocked bootloader is not any problem. OTA updates is working with unlocked bootloader as well.
Cool! i'm only concerned about play store's "device certification status" which is uncertified.
Edit: Fixed with magisk.
Last edited:
Hello guys, i have a question: right now i'm running 7.1.1 latest update and i would like to downgrade to stock MM. I'm rooted and i have TWRP installed. If i create a nandroid backup (all partitions) adn then i install stock MM firmware from my computer (adb flash) are there any chances to brick my phone if i want to go back to 7.1.1 using TWRP nandroid restore ? As far as i know a device is bricked if the user installs OTA after downgrade.
Disclaimer: There are only assumptions so far, none will give you guarantee.
The trigger of the brick is assumed to be in the update of the bootloader. If you omit bootloader when flashing old version, OTA probably won't work but also should not cause a brick if done accidentally.
Okay, I'll have to try it myself. Not sure if I should count on my warranty since the bootloader is unlocked. Thanks for answer.
Sent from my XT1635-02 using Tapatalk
Sent from my XT1635-02 using Tapatalk
It worked
I got it. uhuuullll
Thanks thanks thanks very much..:laugh:
I got it. uhuuullll
Thanks thanks thanks very much..:laugh:
Last edited:
I use it command.
See this terminal information in ubuntu 17.10.
My story
I had downgraded (LineageOS 7.1) to 6.0 (stock) which requested via OTA to upgrade to 7.0. I did. And my phone brick.
I pulled the cable out and replaced it with several button sequences and executed the command script. And one of the sequences was successful at the very moment when the command began again.
(Sorry my english)
That is, it has some sequence that starts the emergency download mode. This is what should be missing for the blankflash to work 100%.
That is, this blankflash is functional. it works!
Code:
sudo ./qboot blank-flash singleimage.bin
Code:
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
[sudo] senha para erick:
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.013] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.013] Check qboot_log.txt for more details
[ 4.013] Total time: 4.013s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.017] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.017] Check qboot_log.txt for more details
[ 4.017] Total time: 4.017s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.022] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.022] Check qboot_log.txt for more details
[ 4.022] Total time: 4.022s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.043] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.043] Check qboot_log.txt for more details
[ 4.043] Total time: 4.043s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.036] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.036] Check qboot_log.txt for more details
[ 4.036] Total time: 4.036s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.015] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.015] Check qboot_log.txt for more details
[ 4.015] Total time: 4.015s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.023] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.023] Check qboot_log.txt for more details
[ 4.023] Total time: 4.023s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.024] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.024] Check qboot_log.txt for more details
[ 4.024] Total time: 4.024s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.036] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.036] Check qboot_log.txt for more details
[ 4.036] Total time: 4.036s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.037] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.037] Check qboot_log.txt for more details
[ 4.037] Total time: 4.037s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 4.029] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.029] Check qboot_log.txt for more details
[ 4.029] Total time: 4.029s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash singleimage.bin
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.003] ...cpu.id = 70 (0x46)
[ 0.003] ...cpu.sn = 2551762972 (0x9818d01c)
[ 0.003] Opening singleimage
[ 0.062] Loading package
[ 0.068] ...filename = singleimage.pkg.xml
[ 0.072] Loading programmer
[ 0.074] ...filename = programmer.mbn
[ 0.074] Sending programmer
[ 0.279] Handling things over to programmer
[ 0.279] Identifying CPU version
[ 0.284] Waiting for firehose to get ready
[ 3.298] ...MSM8953 1.1
[ 3.298] Determining target secure state
[ 3.299] ...secure = yes
[ 3.310] Configuring device...
[ 3.314] Flashing GPT...
[ 3.314] Flashing partition:0 with gpt_main0.bin
[ 3.314] Initializing storage
[ 3.328] ...blksz = 512
[ 3.391] Re-initializing storage...
[ 3.391] Initializing storage
[ 3.446] Flashing bootloader...
[ 3.463] Flashing aboot with emmc_appsboot.mbn
[ 3.729] Flashing rpm with rpm.mbn
[ 3.803] Flashing tz with tz.mbn
[ 4.094] Flashing devcfg with devcfg.mbn
[ 4.124] Flashing cmnlib with cmnlib.mbn
[ 4.201] Flashing cmnlib64 with cmnlib64.mbn
[ 4.273] Flashing keymaster with keymaster.mbn
[ 4.344] Flashing prov with prov.mbn
[ 4.415] Flashing sbl1 with sbl1.mbn
[ 4.537] Rebooting to fastboot
[ 4.539] Total time: 4.539s
[email protected]:~/Downloads/blankflash$I had downgraded (LineageOS 7.1) to 6.0 (stock) which requested via OTA to upgrade to 7.0. I did. And my phone brick.
I pulled the cable out and replaced it with several button sequences and executed the command script. And one of the sequences was successful at the very moment when the command began again.
(Sorry my english)
That is, it has some sequence that starts the emergency download mode. This is what should be missing for the blankflash to work 100%.
That is, this blankflash is functional. it works!
Is it possible to update from 6.0 to 7.0 and unbrick to 7.1.1 and get OTA in preparation for 8.0?
Usually the brick happens when we try to flash an old rom on top of a new one. Because there are files that once uploaded can not be downgraded. And 8.0 all files are news.
I updated my phone to 7.1.1 after the unbrick .. (October update) or so from now on there are only new roms. even before using LineageOs 8.0.
(Correct me if I'm wrong)
sorry my english
You would only likely brick if you've downgraded your device firmware at some point (e.g. you previously had 7.1.1 stock firmware and downgraded to 6.0/7.0). The brick doesn't usually occur with the downgrade, rather it occurs with trying to update with OTA updates. The OTA updates appear to only check if your system is matching the expected patch and signatures, and does not check your bootloader version. Rather, it appears to assume your bootloader is of the same patch level, which if you downgraded is not the case, and thus could corrupt a newer bootloader with older bootloader updates, leading to a hard brick.
If you have downgraded your stock firmware, I would recommend flashing the 7.1.1 stock firmware for your device/region if possible. By flashing via fastboot, you reduce the chances of bricking. Furthermore, don't always depend on the blankflash - at the moment, it appears the Moto Z2 Play (albus) blankflash is working, but as Motorola issues updates to firmware, including the bootloader, the blankflash may cease to work. Be careful and try to not brick your device in the first place
I tried so many time this method, and finally it worked
1. Blank-flash (IMPORTANT - hold both Volume down + power key while run script at first)
2. Fastboot G5plusbootloader --> enter bootloader
3. RSD lite to flash stock
1. Blank-flash (IMPORTANT - hold both Volume down + power key while run script at first)
2. Fastboot G5plusbootloader --> enter bootloader
3. RSD lite to flash stock
Last edited:
i can confirm that following post #181 (only the blankflashfile) and #249 works
my phone is a Moto Z Play XT 1635-02 and got bricked by a failure at upgrading from 6 to 7 via OTA, thank you so much guys.
my phone is a Moto Z Play XT 1635-02 and got bricked by a failure at upgrading from 6 to 7 via OTA, thank you so much guys.
Just so I can be with no doubt: Can this fix hard brick too? I mean my phone is not able to go to fastboot at all. Can it still work for me? I wanna get my phone out of USA and fix it myself. The company doesn't want to help as my phone was not under warranty after one month.
I would be so happy if that works for me.
I finally had some time to play with my phone and unbricked the device.
I had the same error as many in this thread.
I put it on a 8GiB SD Card and initialising the flash worked for me.
Finally I updated all the stuff on a lvm volume on my pc and flashed it with the recovery back to the phone. Only the oem image did not work.
But my patch level ist 1st of august 2017. Is there no newer image of android for the moto z play?
The twrp crashed panics always while pushing the images over adb. One of the following lines solved or hides the problem.
I had the same error as many in this thread.
I got it only to work by placing a sd card with the stuff XT1635-02_ADDISON_RETEU-EMEA_MPN24.104-25_cid50_subsidy-DEFAULT_regulatory-XT1635-02_CFC_EMEA.xml.zip.
I put it on a 8GiB SD Card and initialising the flash worked for me.
Finally I updated all the stuff on a lvm volume on my pc and flashed it with the recovery back to the phone. Only the oem image did not work.
But my patch level ist 1st of august 2017. Is there no newer image of android for the moto z play?
The twrp crashed panics always while pushing the images over adb. One of the following lines solved or hides the problem.
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/0B7X...x5ejEyX1U/view
Code:
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.
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19
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/0B7X...x5ejEyX1U/view
Code:
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.
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19
The google drive link doesn't work.
I just naively accepted a security update and my z play is stuck on TWRP boot
New?
Any news? I recently upgraded android 7.1.2 with new February patch. When I downgraded to 7.0, I was wrong to allow ota update and I got the hardbrick.
Any news on new functional blankflash?
Sorry for my English, google translate.:laugh:
Any news? I recently upgraded android 7.1.2 with new February patch. When I downgraded to 7.0, I was wrong to allow ota update and I got the hardbrick.
Any news on new functional blankflash?
Sorry for my English, google translate.:laugh:
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