Hi
I have updated my stock naugat to feb 2018 but now i want to sideload 8.0 so i have to go back to dec patch how can i do that?
Use caution if you do this, it's my understanding that a couple of users have done this, and were subsequently hard bricked.
In addition to dandrumheller's reply, I would not recommend downgrading and then try to apply the OTA Oreo update. This appears to be a nasty hardbrick and the blankflashes we have do not seem to work.
Safest way would be to wait for the official Oreo OTA or the official Oreo fastboot ROM, as I mentioned previously to you.
Related
Can anyone grab the OTA either from DP2 to stock 7.0 (Beta unenroll) or DP2 to final 7.1.1? (yet to come) please?
I'm stuck on this situation:
http://forum.xda-developers.com/nex...device-corrupted-screen-t3511780#post69945696
Flashing 7.1.1 DP2 went wrong and now the device is stuck with a corrupt device right to recovery scenario and a 11 november 2016 date for otas, that means that there is not any ota able to flash over it (because new otas from december are from 26october and 1november... wtf). The bootloader is locked.
So I would need the ota that google sends back to unenroll from 7.1.1 Android Preview DP1 or DP2, because they presumably don't check for build dates and just flash the stock partitions .
The device is stuck corrupted until google wants to release an OTA flashable in recovery (not staged) with a >11 nov date.
Thanks in advance!
---
EDIT: The OTA from DP2 to final 7.1.1 may also work if it's not staged! if someone can, please capture it to help me
Thanks!!!!
RusherDude said:
Can anyone grab the OTA either from DP2 to stock 7.0 (Beta unenroll) or DP2 to final 7.1.1? (yet to come) please?
I'm stuck on this situation:
http://forum.xda-developers.com/nex...device-corrupted-screen-t3511780#post69945696
Flashing 7.1.1 DP2 went wrong and now the device is stuck with a corrupt device right to recovery scenario and a 11 november 2016 date for otas, that means that there is not any ota able to flash over it (because new otas from december are from 26october and 1november... wtf). The bootloader is locked.
So I would need the ota that google sends back to unenroll from 7.1.1 Android Preview DP1 or DP2, because they presumably don't check for build dates and just flash the stock partitions .
The device is stuck corrupted until google wants to release an OTA flashable in recovery (not staged) with a >11 nov date.
Thanks in advance!
---
EDIT: The OTA from DP2 to final 7.1.1 may also work if it's not staged! if someone can, please capture it to help me
Thanks!!!!
Click to expand...
Click to collapse
OP request to close...
THREAD CLOSED
hi i need the OTA zip file for the Moto Z Play because i used to have free unlimited wifi hotspot until i updated the phone,
I already have the Android 7.1.1 update but things keep crashing all the time, is it posible for me to downgrade the os?
the phone is unlocked
model : XT1635-02
Below is the method I know of but it seems people have had issues after upgrading to 7.1.1 so you may not be able to down grade at this moment.
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
I will advise you that it is a bad idea to downgrade. After the April 7.0 patch, downgrading to Marshmallow and OTAing back to Nougat will result in a hard brick, which cannot be repaired without the necessary blank flash files, which are not available.
IncendiaryPyro said:
I will advise you that it is a bad idea to downgrade. After the April 7.0 patch, downgrading to Marshmallow and OTAing back to Nougat will result in a hard brick, which cannot be repaired without the necessary blank flash files, which are not available.
Click to expand...
Click to collapse
I've read about this issue. So basically only for those who had the April 7.0 patch on their Moto Z play will hard brick the device? When they downgrade and update? I've downgraded plenty of times, but decided not to OTA back to nougat.. Now I'm worried if I accidently OTA to Nougat will my phone get hard bricked?
Dchoi229 said:
I've read about this issue. So basically only for those who had the April 7.0 patch on their Moto Z play will hard brick the device? When they downgrade and update? I've downgraded plenty of times, but decided not to OTA back to nougat.. Now I'm worried if I accidently OTA to Nougat will my phone get hard bricked?
Click to expand...
Click to collapse
According to a user here, the brick happens when you install the April security update, downgrade to Marshmallow, then OTA back to Nougat, typically bricking on the first, initial update to Nougat. I've downgraded from the January patch once back to Marshmallow, then OTA'd to Nougat + February, then N + March whenever my carrier released it without any issues. I have not received the April patch yet though, but I think you're good.
Awesome. I think it's time to stop flashing roms now lmao.. I dont wanna brick my phone.
Dchoi229 said:
Awesome. I think it's time to stop flashing roms now lmao.. I dont wanna brick my phone.
Click to expand...
Click to collapse
I just got the April patch today, and it has not bricked my phone, so if you've never installed that update, you should be okay to OTA.
ok, im confused, I want to downgrade from nougat 7.1.1 to android mm 6.0 with adb, my phone is not rooted i just want to downgrade normally to have hotspot again
robertriverabula said:
ok, im confused, I want to downgrade from nougat 7.1.1 to android mm 6.0 with adb, my phone is not rooted i just want to downgrade normally to have hotspot again
Click to expand...
Click to collapse
you can't downgrade unless you unlock the bootloader, and are ok with potentially turning your phone into a brick.
robertriverabula said:
ok, im confused, I want to downgrade from nougat 7.1.1 to android mm 6.0 with adb, my phone is not rooted i just want to downgrade normally to have hotspot again
Click to expand...
Click to collapse
Ah, I finally find out that I am not the only one with hotspot issue on 7.1.1. But 7.1.1 is so good that I am not going to downgrade only for the hotspot issue. I will wait for the Official 7.1.1 release to fix that issue.
IncendiaryPyro said:
I just got the April patch today, and it has not bricked my phone, so if you've never installed that update, you should be okay to OTA.
Click to expand...
Click to collapse
Great. I've heard that the reason for why people are bricking their phone is because of the updated bootloader? The April patch updates the BL to C1.07 and mine right now is 1.05. Do you think I can flash the Xenon HD rom (7.1.1) and if for some reason i want to downgrade again i wont brick my phone?
Dchoi229 said:
Great. I've heard that the reason for why people are bricking their phone is because of the updated bootloader? The April patch updates the BL to C1.07 and mine right now is 1.05. Do you think I can flash the Xenon HD rom (7.1.1) and if for some reason i want to downgrade again i wont brick my phone?
Click to expand...
Click to collapse
Hi just wondering what is the security patch you have? I mean you have c1.05 is it MM?
Kap_Tutan said:
Hi just wondering what is the security patch you have? I mean you have c1.05 is it MM?
Click to expand...
Click to collapse
dont get confused. I never downloaded the april security patch. my bootloader version is c1.05 which i believe is the feb patch. the april patch is c1.07. If you downloaded the April patch and downgraded do not try to install the ota. it will brick your phone.
What's the reason for hard brick ?
When downgrading then receiving OTA Update .
I have several Moto Z Plays here; two are retus and one is reteu. The reteu one is running 7.1.1 (official version, not a soak test, NPN26.118-22) because I downloaded the official update and sideloaded it yesterday. It has the July security patch. I was never a soak tester, either. The retuses are still on 7.0, May security patch (NPN25.137-24.4).
Here's the issue. When I sideload NPN26.118-22 (7.1.1. official) on a retus, I get an error saying "E3002: Package expects build thumbprint of 7.1.1/NPN26.118-22/21:user/release-keys or 7.0/NPN25.137-24.3/4:user/release-keys; this device has 7.0/NPN25137-24.4/5:user/release-keys," and it fails. (This also happened on reteu, but I happened to have the package it wanted to see, so I installed it first. See below.)
So, my next move is to replicate what worked on reteu, which was to flash the other package I have first, but I get another error saying "E3002: Package expects build thumbprint of 7.0/NPN25.137-24.3/4:user/release-keys or 7.0/NPNS25.137-24-1-9/10:user/release-keys; this device has 7.0/NPN25.137-24.4/5:user/release-keys."
I'm sort of at a loss from here of what to do, since the May security update for retus does seem to prevent compatibility with flashing any new package. The reason this wasn't an issue on the reteu one was, I'm assuming, because it was on the April security update, and I was able to install the second package, and then finally official 7.1.1 to get it current.
Anyone have any ideas? I can't be the only one running this freaking NPN25.137-24.4 (May) update on the retus Z Play that is preventing me from sideloading official 7.1.1. Thanks in advance!
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Zeljko1234 said:
Let me ask again (not you, in general). Why do you so desperately want 7.1.1? And risk hard bricking flashing images?
Mine Play is also retus and got May security patch last week. I'm not noticing any bugs. 7.1.1 is not bringing something revolutionary. It's still 7.x after all. I'm even thinking to not accept update. Don't fix it if is not broken.
Click to expand...
Click to collapse
I appreciate your reply, but this isn't really relevant to my question at all. I acknowledge there are risks with flashing, but I did it successfully on one of my devices and it's really not the scariest thing I've ever done on ADB.
If you're content to wait, that's fine; what I want to know is the reason why I can't seem to do it on 2/3 of my devices. I'd appreciate responses that are relevant to my question.
I replied to your post on reddit, but I'll share it here too. Someone may even correct me here on XDA if I've got any info wrong.
The 7.1.1 that was released to most of us (retbr, retca, etc) require the build number NPN25.137-24.3 (May 2017 security patch) to be installed.
The May security patch on retus has the build number of NPN25.137-24.4 (I guess there was a change that warranted the .4 over .3). All retus phones will have this build number if they've installed the May patch.
This is why you were getting errors when trying to sideload 7.1.1 onto the retus phones (trying to install an update not meant for the device). retus will likely get a different install package for Android 7.1.1
How do you sideload using stock recovery? I tried adb devices and my device is not listed. I want to sideload Google stuff to stock ROM, any idea how to do that? Tried to install the APK files manually but I got force closed after that. Thank you.
how to downgrade from 8.0 to nougat?
ZeroVirus said:
how to downgrade from 8.0 to nougat?
Click to expand...
Click to collapse
Just a friendly reminder, never ever downgrade your bootloader and accept/install OTA's unless you are ready and prepared to unbrick your device. Many folks had brick their devices when they downgrade their bootloader and accept ota. If u are in a soak test firmware then best thing to do is wait until they release the 2nd or final soak firm. :good:
ZeroVirus said:
how to downgrade from 8.0 to nougat?
Click to expand...
Click to collapse
Just flash 7.1.1 firmware
LabLab...28 said:
Just a friendly reminder, never ever downgrade your bootloader and accept/install OTA's unless you are ready and prepared to unbrick your device. Many folks had brick their devices when they downgrade their bootloader and accept ota. If u are in a soak test firmware then best thing to do is wait until they release the 2nd or final soak firm. :good:
Click to expand...
Click to collapse
But what if i am just flash other thing accept bootloader?
ZeroVirus said:
But what if i am just flash other thing accept bootloader?
Click to expand...
Click to collapse
Downgrading your stock firmware generally will not downgrade your bootloader (you'll usually see a security downgrade error and/or pre-flash validation error if you try).
So if you do downgrade, you'll likely have an (newer) Oreo bootloader and (older) stock Nougat system. If you attempt to use a stock Nougat OTA update, the Nougat OTA may corrupt your newer Oreo bootloader and hard brick your device. OTA updates appear to only check if your system is the correct patch level, and do not appear to determine if your bootloader is of the same patch level. As you've downgraded, this mismatch of bootloader/stock system patch levels and stock OTA corruption is why downgrading is risky. The act of downgrading won't cause you issues, the use of stock OTA updates (regardless of whether they're from XDA or Motorola) may well cause you issues.
If you downgrade to the December 2017 7.1.1. firmware and it emerges that the next OTA update you receive is the Oreo OTA, you may be okay. However, if you downgrade and receive a Nougat OTA (e.g. you downgraded to the Nov 2017 firmware, or there is another Nougat OTA before the Oreo OTA), you may encounter serious trouble. We saw similar issues when the 7.1.1 soak test got leaked - users would downgrade from 7.1.1 to 7.0 and proceed to hard brick when they attempted to use OTA updates (because they had a newer bootloader). Luckily, we had a blankflash then, I do not know if the blankflash will still work for Oreo bootloaders.
As mentioned above, you can wait for the soak test OTA updates to be leaked or wait for the Oreo stock firmware to be captured, which should be safer to update with.
I just updated to
Version
10.0.12.HD65AA
Updated on
August 11, 2020
Now I am having a problem with texts, is there a site where I can get the July update, and how do I go about making the downgrade. Can I do it through the phone update, or do I have to use TWRP or fastboot?
Thanks