I have the 1635-03 variant of MZP. I just successfully restored the stock firmware (RETCN_6.0.1) and immediately after launched the update to 7.0.1 Nougat. downloaded and promoted to install, began installation. phone reboot, update installing then bam.. a total blackout.. black screen; unable to boot or even enter fastboot..
Don't know what happened :crying::crying::crying:
Please help me find out what happened
(Still got a valid warranty, but have unlocked the bootloader, so don't think they'll accept to take it back)
Hey.. Sorry that I'm the one to break the bad news, but you just hard bricked your moto z play. If you downgraded to MM when you have already had the April Nougat Patch, and upgraded back to nougat then it'll turn the phone into a paper weight. Theres other post on xda of people reporting the problem. No fixes as of right now. You'll have to sit on it till a solution comes up.
Dchoi229 said:
Hey.. Sorry that I'm the one to break the bad news, but you just hard bricked your moto z play. If you downgraded to MM when you have already had the April Nougat Patch, and upgraded back to nougat then it'll turn the phone into a paper weight. Theres other post on xda of people reporting the problem. No fixes as of right now. You'll have to sit on it till a solution comes up.
Click to expand...
Click to collapse
Thanks for the info.. any suggested threads to follow ?
https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
Best of luck to you.
Related
Hi there Guys. GoodDay. I just wanna ask. I recently bought Nexus 5x. And i see nougat is ready for update. But before that Ive found out on internet that some users that updated from MM to Nougat got stuck on bootloop and seems they cant figured it out i dont know if its model related(h791/h798). Google Employee says hardware. Here 's a qoute of a report. from androidauthority website.
"We’ve been hearing an increasing number of reports from Nexus 5X owners about bootloop issues after upgrading to Android 7.0 Nougat.
Many folks have been claiming that, after installing the Android 7.0 Nougat OTA, their Nexus 5X devices would unexpectedly crash and begin to randomly reboot after a few hours, or even days, of use. Some users say downgrading to Android 6.0 Marshmallow does the trick, while others say reflashing the Android 7.0 Nougat September update fixes the problem. Most people, unfortunately, have yet to find a good fix for the problem.
So if you run into this issue, what should you do?
Orrin, a Google employee, had this to say in the Nexus Help Forums:
We understand that a very small number of users are experiencing a bootloop issue on the Nexus 5X. We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue. For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options.
We’re sorry for the inconvenience and appreciate your continued patience."
Im afraid that if i update via OTA just like them. chances it might or might not happen to me. and if did, can a tool like Wugfresh' NRT save it? or should i root and manually update to nougat via some toolkit or manually, is it safer? Thank You very much for your suggestions.
BtW: im on
LG H791 Android 6.0
Build MDA89E
Security Patch Oct.1,2015
ryuhagaming said:
Hi there Guys. GoodDay. I just wanna ask. I recently bought Nexus 5x. And i see nougat is ready for update. But before that Ive found out on internet that some users that updated from MM to Nougat got stuck on bootloop and seems they cant figured it out i dont know if its model related(h791/h798). Google Employee says hardware. Here 's a qoute of a report. from androidauthority website.
"We’ve been hearing an increasing number of reports from Nexus 5X owners about bootloop issues after upgrading to Android 7.0 Nougat.
Many folks have been claiming that, after installing the Android 7.0 Nougat OTA, their Nexus 5X devices would unexpectedly crash and begin to randomly reboot after a few hours, or even days, of use. Some users say downgrading to Android 6.0 Marshmallow does the trick, while others say reflashing the Android 7.0 Nougat September update fixes the problem. Most people, unfortunately, have yet to find a good fix for the problem.
So if you run into this issue, what should you do?
Orrin, a Google employee, had this to say in the Nexus Help Forums:
We understand that a very small number of users are experiencing a bootloop issue on the Nexus 5X. We are continuing to investigate the situation, but can confirm that this is strictly a hardware related issue. For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options.
We’re sorry for the inconvenience and appreciate your continued patience."
Im afraid that if i update via OTA just like them. chances it might or might not happen to me. and if did, can a tool like Wugfresh' NRT save it? or should i root and manually update to nougat via some toolkit or manually, is it safer? Thank You very much for your suggestions.
BtW: im on
LG H791 Android 6.0
Build MDA89E
Security Patch Oct.1,2015
Click to expand...
Click to collapse
Wouldn't you rather it boot loop now then later when it's no longer covered under warranty?
Boot loop is a hardware issue that becomes exposed during the install process. You gain nothing by waiting and the same thing could be triggered every time the device is rebooted.
Sent from my Nexus 5X using XDA-Developers mobile app
Did you update? I'm in the exact same situation, afraid to update because I just got my phone from amazon and it's running Marshmallow...same model as yours. H791 I don't know if I even have a warranty for it
I suggest you update because it is possible that you might not have that hardware issue, I bought mine a month back and hadn't read any forums or anywhere online about the bootloop. I updated right when I got the phone to android 7.0 xD and my phone has been fine since.
sickofusernames said:
Did you update? I'm in the exact same situation, afraid to update because I just got my phone from amazon and it's running Marshmallow...same model as yours. H791 I don't know if I even have a warranty for it
Click to expand...
Click to collapse
Yeah, ive managed to successfully update it to nougat including the latest build 7.0.1. i think there is just some certain phone that are affected. just see to it that your bootloader is unlock before you update. just in case, you can still go to your recovery.
X3NOM said:
I suggest you update because it is possible that you might not have that hardware issue, I bought mine a month back and hadn't read any forums or anywhere online about the bootloop. I updated right when I got the phone to android 7.0 xD and my phone has been fine since.
Click to expand...
Click to collapse
wow. that's nice :good:
ryuhagaming said:
Yeah, ive managed to successfully update it to nougat including the latest build 7.0.1. i think there is just some certain phone that are affected. just see to it that your bootloader is unlock before you update. just in case, you can still go to your recovery.
Click to expand...
Click to collapse
Thanks for the reply, it gave me the courage to just do it! So far so good, no issues
I've been searching high and low for a full nougat firmware package for the RETUS model... and i cant find one. Has anyone else found one?
I know there are OTAs out there, I'm looking for an FXZ that can be used with fastboot.
filefactory, mirrors.lolinet, etc... seem to have most 7.0 firmware packages EXCEPT for RETUS which only have 6.0 packages.
I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.
Jimi Mack said:
I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.
Click to expand...
Click to collapse
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.
FanDroid09 said:
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.
Click to expand...
Click to collapse
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
What did you do to root? Unlock bootloader then what?
chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.
EspElement said:
What did you do to root? Unlock bootloader then what?
Click to expand...
Click to collapse
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
FanDroid09 said:
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.
Click to expand...
Click to collapse
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.
Does anyone know where to get the latest either RETAIL or RETUS stock firmware with the May 1st security update? NPN25.137-24.4
chris23445 said:
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.
Click to expand...
Click to collapse
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader
EspElement said:
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader
Click to expand...
Click to collapse
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
Is it worth after all?
chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
I've been there done that that's for sure. I just bricked one of my Moto Z plays last week doing what you were about to do.
StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.
tpx00 said:
StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.
Click to expand...
Click to collapse
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh
EspElement said:
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh
Click to expand...
Click to collapse
Ya I'm about to go pick up a nexus 6 from craigslist until mine comes back from Motorola.
Ok long and short; reverted to MM base, wiped clean, accepted the OTA for 7.0. Did not get an error message in stock recovery while it updated. It finished went to reboot and nothing. When I plug it in , led flashes. unplug it and led turns off. Plug in and out of computer. And the PC recognizes something is plugged in but can't find any hardware changes in device manager. Not sure what I ca try next????
Attempted
fast boot - no device
Adb - no device
Computer - makes sound when plugged or unplugged but not in window explorer
Rsd lite- no device.
I feel like the battery died while writing battery charging files or something???
Willing to try anything
Thanks guys. Matt
RETUS xt1635-02 / sec. patch either August or November 2016 mm 6.0.1
It's a hard brick. Sad, there is nothing you can do to fix it. Except You will need to send it back to the manufacturer or change the logic board.
The reason of the brick is accepting 7.0 ota after downgrading to MM.
Yousvel said:
It's a hard brick. Sad, there is nothing you can do to fix it. Except You will need to send it back to the manufacturer or change the logic board.
The reason of the brick is accepting 7.0 ota after downgrading to MM.
Click to expand...
Click to collapse
Yup, can confirm. Sorry OP.
Sent from my XT1635-02 using Tapatalk
Another one. Sucks bro...
The issue did indeed come from downgrading and then accepting the OTA. When you downgrade firmware on a moto phone you can NOT flash the downgraded bootloader. It can cause problems like this.
That's what I figured,wasn't worried since I was on November security patch. why is it that I was able to do so a couple months ago? Was on MM ota'd then custom rom and when I had problems I flashed MM and ota'd back to 7.0? I
tpx00 said:
That's what I figured,wasn't worried since I was on November security patch. why is it that I was able to do so a couple months ago? Was on MM ota'd then custom rom and when I had problems I flashed MM and ota'd back to 7.0? I
Click to expand...
Click to collapse
It was possible with any patch before the April one. Since April, no dice.
FanDroid09 said:
Another one. Sucks bro...
The issue did indeed come from downgrading and then accepting the OTA. When you downgrade firmware on a moto phone you can NOT flash the downgraded bootloader. It can cause problems like this.
Click to expand...
Click to collapse
If i downgrade without flashing bootloader and gpt, will I be able to receive and install OTA?
Guys, i'm literally in panic. I really need some help, please.
I have an unlocked bootloader, was using Nougat 7.1.1 with december security patch, but these sec. patch "bricked" my cam, so i downgraded to marshmallow but without flashing gpt.bin and bootloader.img, I upgraded to 7.0, and then upgraded to april sec. patch 2017, but after the ota was being installed, the phone bricked, i was not able to do anything. My led doesn't appears after anything. I tried a lot of blankflash files, but none of them worked for me, since those files were for users who were in 7.0(I guess), so i literally need your help guys, what to do? will Motorola release blankflash for us? I want my phone back, i use it all the time, I don't know what to do, i'm almost crying for this lost.
Please help me!
I've searched on the forum, but nothing worked.
IM IN PANIC OMG!
follow : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
and you should attach error log from blankflash.
xdaVTU said:
Guys, i'm literally in panic. I really need some help, please.
I have an unlocked bootloader, was using Nougat 7.1.1 with december security patch, but these sec. patch "bricked" my cam, so i downgraded to marshmallow but without flashing gpt.bin and bootloader.img, I upgraded to 7.0, and then upgraded to april sec. patch 2017, but after the ota was being installed, the phone bricked, i was not able to do anything. My led doesn't appears after anything. I tried a lot of blankflash files, but none of them worked for me, since those files were for users who were in 7.0(I guess), so i literally need your help guys, what to do? will Motorola release blankflash for us? I want my phone back, i use it all the time, I don't know what to do, i'm almost crying for this lost.
Please help me!
I've searched on the forum, but nothing worked.
IM IN PANIC OMG!
Click to expand...
Click to collapse
location/country?
what firmware have you been using?
RSD lite?
KrisM22 said:
location/country?
what firmware have you been using?
RSD lite?
Click to expand...
Click to collapse
I'm from Brazil, so channel retbr
I was using latest version of 7.1.1 (NPNS26.118-22-12)
RSD Lite i was using the 6.2.4 version
Remember that I downgraded to 6.0.1 and upgrde through OTA to 7.0, with that OTA my phone gt bricked.
I can't reboot into bootloader to flash anything, that's why I want the blankflash
Edit. As I want my device ASAP, I've gone to a assistance. He said he was gonna send my device to another city to their software team. If they get the problem and solve it, I'll just pay 80 reais(my currency), if not, i don't pay anything.
What do you think? Do you think it's possible to fix it without changing the motherboard? And about the board, do you think that it's worth it changing it?
xdaVTU said:
I'm from Brazil, so channel retbr
I was using latest version of 7.1.1 (NPNS26.118-22-12)
RSD Lite i was using the 6.2.4 version
Remember that I downgraded to 6.0.1 and upgrde through OTA to 7.0, with that OTA my phone gt bricked.
I can't reboot into bootloader to flash anything, that's why I want the blankflash
Edit. As I want my device ASAP, I've gone to a assistance. He said he was gonna send my device to another city to their software team. If they get the problem and solve it, I'll just pay 80 reais(my currency), if not, i don't pay anything.
What do you think? Do you think it's possible to fix it without changing the motherboard? And about the board, do you think that it's worth it changing it?
Click to expand...
Click to collapse
follow what @ Ax1qwer said above, or change it. Never download to MM.
Ax1qwer said:
follow : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492
and you should attach error log from blankflash.
Click to expand...
Click to collapse
i'm not able to download his file, i get error 401 when i click the link.
Anyway, my phone is with the assistance now, tuesday i'll get it back either they fixed it or not, but i hope they solve it...
I downloaded others blankflashes.bat but all of them didn't work, i got this everytime(attached)
The attached file is just one of the logs i got, i tried others files, but I deleted them... sorry
After having upgraded from Nougat 7.1.1 to Oreo using the OTA update I'm not feeling the love for it and it breaks a few thing I need to work.
Can anybody point me in the direction of a guide that works to perform the downgrade ? I'm really attached to my Moto Z Play and I don't want to brick it .
Is your bootloader unlocked?
rampare99 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No it isn't but I don't see any challenge in unlocking it. Having said that I'm starting to come around to liking Oreo on the Moto.
Iceworkz said:
No it isn't but I don't see any challenge in unlocking it. Having said that I'm starting to come around to liking Oreo on the Moto.
Click to expand...
Click to collapse
I'm glad to hear that. If you still want to go back to Nougat you'd need to unlock your bootloader, flash TWRP and then flash this zip (after a factory reset) from shamu17:
https://androidfilehost.com/?fid=889964283620776181
And that's it. If you want to go back to Oreo, you'll need to flash shamu17's Oreo rom.
The only thing I'm noticing since going to Oreo on my Z Play is apps will download to 100% from the Play store but wont install unless I swipe away app from recent apps. Already cleared cache and all that but still goes back to not installing apps. Annoying.
I'd suggest just installing official LineageOS 14.1
Chase down @SupahCookie and guide.
also my guide
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530
Iceworkz said:
After having upgraded from Nougat 7.1.1 to Oreo using the OTA update I'm not feeling the love for it and it breaks a few thing I need to work.
Can anybody point me in the direction of a guide that works to perform the downgrade ? I'm really attached to my Moto Z Play and I don't want to brick it .
Click to expand...
Click to collapse
Don't feel bad. After I got the Oreo update, all my weather and clock widgets stopped working. They are either frozen in time, or completely invisible on my home screen. My phone ran smooth as silk on Nougat, so I'm less than happy with this new operating system.
use the "alternative"
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530