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.
Related
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.)
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
EDIT: Just got the OTA for the N preview, so I guess it's just a roll out thing then. Just want to leave this here for anyone else who's new to nexus devices and was wondering the same.
AnrgKrshn said:
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
Click to expand...
Click to collapse
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
brholt6 said:
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
Click to expand...
Click to collapse
Just saw this after I posted my edit lol. Thanks for the confirmation
Will the ota work with systemless root?
94SupraTT said:
Will the ota work with systemless root?
Click to expand...
Click to collapse
You need to flash stock boot and recovery images to receive it or alternatively use chainfires flashfire app.
I have tried to update my chinese XT1635-03 to 7.1.1 with OTA through ADB sideload and unfortunately it is not working.
I have sucessfully flashed the phone with reteu latest firmware with April security patch (ADDISON_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) through fastboot.
But once I try to sideload 7.1.1 OTA (Blur_Version.26.1.22.addison.retail.en.US) the process terminates at 47% with notification that the package expects product name "addison" but actual value is "addison_retcn"
Is it possible to either change the product name or disable such check of product name? It seems to me, that at the moment there is no way to flash OTA and I need to wait for full 7.1.1 image.
Reading similar questions around, I have to ask. Why you people cannot wait couple of weeks to get OTA? Instead of risking to brick your device?
New update is not bringing revolutionary/awesome/amazing/mind blowing... new features. I understand if it's update to completely new Android version or that your device/region will not get update at all.
Sent from my XT1635-02 using Tapatalk
You have XT1635-03 and the update is for XT1635-02. So if you have a reteu phone you can really update over sideload without issues. And yes, I need android 7.1.1 and I wouldn't wait one day longer. I need app-shortcuts, because I had this on my old phone, too. There was android 7.1 since the first day. But if you don't have it before you can't miss it. So you can wait much easier For me it was important for other issues, too. For example Wifi problems and stability fixes and over 100 security fixes. Many reasons for the update
Edit: And one more reason for the update: To help google to get more than 0.6% for android 7.1 We should update all, otherwise android 7.1 will never get 1%
Everybody should help to get this 1% maybe next month. So update, just do it for the 1%, yes xD
:silly::good:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
The point is, how can you change the channel...
freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
OK, makes sense for you but for many/most others is just matter of time.
I'm not blaming anyone. Do whatever you want with your phone, just be ready if something goes wrong
The surprise was a different phone name. Different channel is usually not a problem
freeman_g said:
The surprise was a different phone name. Different channel is usually not a problem
Click to expand...
Click to collapse
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
flashallthetime said:
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
Click to expand...
Click to collapse
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
allrightlite said:
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
Click to expand...
Click to collapse
I have no idea
flashallthetime said:
I have no idea
Click to expand...
Click to collapse
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
allrightlite said:
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
Click to expand...
Click to collapse
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
dandrumheller said:
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
Click to expand...
Click to collapse
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
allrightlite said:
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
Click to expand...
Click to collapse
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
dandrumheller said:
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
Click to expand...
Click to collapse
It feels not like a beta. It's more like a big bug fix with much patches. For example my Wifi is now stable as hell and never reconnections anymore. Hope it keeps stable, but looks very very good. I think this beta will be the final release in few months, or weeks? But it's much better than 7.0. And better than LOS14.1, which is not so stable (on my other phone). And I have no app crashes anymore. Gboard was crashing with 7.0 one time and few other apps like firewall. So, 7.1.1 is pure stable as hell and must have :laugh:
Afaik, it's not beta. It's soak. So, if test users reported as stable, it will be pushed to all as the final build. If not, Moto has to fixed and not all users around the world will be affected.
Regular and recommend way of releasing update.
Sent from my LG-V940n using Tapatalk
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
If you are on XT1635-03 with reteu frmware you will not receice any OTA. My experience told that you can't even sideload an update. So no worry about bricks.
Very often devices are hardbricked when you are downgrading bootloader but once I have hardbricked my Nexus 6 with OTA (sideloading it). Well, it was not full brick, but I can't load the system (only fastboot) and my bootloader was locked. Without system loaded you can't allow unlocking procedure so the first thing I do with new phone is unlocking.
allrightlite said:
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
Click to expand...
Click to collapse
I know the build is not a beta. I'm referring to the fact that once you leave the official upgrade path, taking any update is a scenario not tested by Moto. So you are testing for them. Maybe you win, maybe you brick.
It seems that the problem with "addison_retcn" may be fixed with editing build.prop but in this case systemless root is required (AFAIK there us no systemless root for Nougat)
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 .
Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
sheri.khan said:
Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
Click to expand...
Click to collapse
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Jimi Mack said:
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Click to expand...
Click to collapse
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
sheri.khan said:
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
Click to expand...
Click to collapse
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Jimi Mack said:
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Click to expand...
Click to collapse
Thanks brother.
I don't seem to get why the RETGB firmware isn't released.
I literally can't find anyone except i guess two or just 3 people who have the same software channel.
Thanks again!
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
jzamalot said:
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
Click to expand...
Click to collapse
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
sheri.khan said:
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
Click to expand...
Click to collapse
Thanks, just wondering because the blackberry priv bootloader was also never unlocked or ever rooted
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.