This sounds dumb but i just hardbricked my Z Play. Any help ?
Did you take the OTA update whilst downgraded?
If so, you could try the blankflash here https://forum.xda-developers.com/showpost.php?p=73402033&postcount=181 but I suspect your bootloader might be too new for this blankflash.
Otherwise, your options would be to get the motherboard replaced (expensive), hope that a newer blankflash comes out (no idea if that will even happen) or consider paying for a new device.
Related
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.
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?
Can Oreo be downgraded after Oreo update with August flash all Nougat files ?
Need to get the phone back on Nougat.
If not can someone like me to the oreo TMobile z2 stock firmware that can be fastboot flashed.
As far as I know, not yet. I ACCIDENTALLY downgraded, and was luckily saved by the Oreo flash-all...I had lost data connectivity. My advice? DON'T do it. Too risky.
sabrdawg said:
As far as I know, not yet. I ACCIDENTALLY downgraded, and was luckily saved by the Oreo flash-all...I had lost data connectivity. My advice? DON'T do it. Too risky.
Click to expand...
Click to collapse
DO NOT TRY TO DOWNGRADE. I had to replace my device because when I tried, it bricked my bootloader (not sure how) but it did. $150 to replace.
byt3b0mb said:
DO NOT TRY TO DOWNGRADE. I had to replace my device because when I tried, it bricked my bootloader (not sure how) but it did. $150 to replace.
Click to expand...
Click to collapse
Exactly. I was very thankful that one of the devs saved me! I thought I'd have to replace my phone!
Could you tell the reasons WHY you wanna downgrade to Nougat instead of remaining with Oreo?
Maheshwara said:
Could you tell the reasons WHY you wanna downgrade to Nougat instead of remaining with Oreo?
Click to expand...
Click to collapse
I need to get my phone to stock and locked on Oreo
For a warranty without the system modified splash screen wether it be on Nougat or Oreo
Thanks - I thought because of bugs and malfunction. Flashed it today and it has REALLY left a good impression to me up to now.
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
I know its bootloader is locked, but what happens if I try to flash trough fastboot? I mean, in the black kinda console screen after you press Power button + Vol Down button.
ADB interface recognize this, but I'm pretty afraid to make my Moto Z a hard dead block. So, have anyone did this?
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
rusa-raus said:
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
Click to expand...
Click to collapse
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
echo92 said:
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
Click to expand...
Click to collapse
Understood, seems like Verizon is not gonna update Moto Z Play...