I purchased a Z2 Play (Freedom Mobile in Canada, XT1710-01, retca channel). I proceeded to unlock the bootloader, install TWRP and root (Magisk 13.3, then upgraded to v14). However, doing this obviously makes installing OTAs not possible. Unfortunately I didn't do a stock backup of anything before doing the above.
From my understanding, installing OTAs requires stock recovery and an unmodified system partition. So, I tried installing just the stock recovery from the RETAIL stock ROM (from here. Then I did a full uninstall of Magisk, expecting (hoping) that would put my phone back into a state (unmodified system partition) that would allow me to install OTA updates.
I presently have an OTA update pending (NPS26.118-15 which has July security updates and Moto Mods 2.0 support, among other things).
However, when I try to install it, my phone reboots and it displays the "Installing system update" screen for a few seconds, then goes to an "Error!" screen, with the green android laying down and an red exclamation mark coming out of his belly. OTA failed.
I am able to restart and boot back into Android, and get the message indicating the OTA failed and nothing was changed.
Can anyone offer any other thoughts or help on things I could try to get the OTA updates to apply? (Just for funsies, I did also try Chainfire's Flashfire, but had no luck with that either.)
I have Z2 Play from Freedom Mobile as well. I'm currently at NPSS26.118-19-4. I was bootlooping into TWRP and I had no other choice and took the risk and chanced flashing the ROM from Junior Passos over at his site. Can't post links but Google motozbrasil.
It says XT1710-07 but it's working fine for me. I'm rooted and passing SafetyNet as well. The ROM automatically detected and says retca on software channel and changed the last bit of string on the baseband as NA_Cust.
I can confirm it works but like I said was my only option. Please be careful. I'm not responsible if it doesn't work for you.
Edit: My SKU in Hardware Information displays XT1710-01 as well not XT1710-07.
atheart said:
I have Z2 Play from Freedom Mobile as well. I'm currently at NPSS26.118-19-4. I was bootlooping into TWRP and I had no other choice and took the risk and chanced flashing the ROM from Junior Passos over at his site. Can't post links but Google motozbrasil.
It says XT1710-07 but it's working fine for me. I'm rooted and passing SafetyNet as well. The ROM automatically detected and says retca on software channel and changed the last bit of string on the baseband as NA_Cust.
I can confirm it works but like I said was my only option. Please be careful. I'm not responsible if it doesn't work for you.
Edit: My SKU in Hardware Information displays XT1710-01 as well not XT1710-07.
Click to expand...
Click to collapse
That's great to hear. I've seen his ROM, but had concerns about flashing it on our device. Glad to hear, I'll probably give that a go, then.
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Thanks for sharing this. I was wondering why "nobody" has tried to flashed the RETAIL stock image (which came from a motorola server) and is mirrored at
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
?
romhippo.com said:
Thanks for sharing this. I was wondering why "nobody" has tried to flashed the RETAIL stock image (which came from a motorola server) and is mirrored at
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
?
Click to expand...
Click to collapse
It's one and the same. On Junior's site, the download link he has links the the lolinet.com one.
(http://motozbrasil.blogspot.ca/2017/09/firmware-moto-z-play-xt1710-07-firmware.html)
Junior just has helper files and instructions to make it easy.
TravellingGuy said:
It's one and the same. On Junior's site, the download link he has links the the lolinet.com one.
(http://motozbrasil.blogspot.ca/2017/09/firmware-moto-z-play-xt1710-07-firmware.html)
Junior just has helper files and instructions to make it easy.
Click to expand...
Click to collapse
Ok, great. I guess, when I read "Junior's site" , I had this site in mind at https://www.androidfilehost.com/?w=files&flid=195559&sort_by=date&sort_dir=DESC which basically contains the "stock backup" of his XT1710-07 phone.
I should not have skimmed your posts. My bad
TravellingGuy said:
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Click to expand...
Click to collapse
That's good to hear man. Now that's two so far that were successful including mine. Seems like ROM is cross compatible.
atheart said:
That's good to hear man. Now that's two so far that were successful including mine. Seems like ROM is cross compatible.
Click to expand...
Click to collapse
I also tried this RETAIL image, and it seems cross compatible in my case too. I flashed only the "service.xml" with RSD lite and did not lose any data. Software channel and model did not change either.
TravellingGuy said:
Just to finish off this thread, I successfully installed @Junior Passos's ROM and everything is working great.
I didn't root or install TWRP (left it at stock) this time, I'm curious if future OTAs will work for me now.
Click to expand...
Click to collapse
An update from me on this. I mentioned I installed Junior Passos's ROM (the August update one), but then left my phone at stock (no root, no TWRP) to see if OTAs would work. Good news, I got the notification about the September OTA update yesterday, and I was able to download and install it with no issues! Sweet.
TravellingGuy said:
An update from me on this. I mentioned I installed Junior Passos's ROM (the August update one), but then left my phone at stock (no root, no TWRP) to see if OTAs would work. Good news, I got the notification about the September OTA update yesterday, and I was able to download and install it with no issues! Sweet.
Click to expand...
Click to collapse
Do you have updates in English after doing all of this? I just got my Z2 Play from Amazon today and noticed that it is on the RETLA channel and all of my system updates are in Spanish. The phone still functions in English, and so far I have found nothing else that is not in my language. However, it kind of bothers me that my updates are not tied to my region, so I'm really hoping that there is a way to get my phone on the RETUS channel, or at the very least, get my update notes in my language.
Related
New firmware T700ZSU1ANL1 and T800ZSU1ANL1 (Hong Kong both).*
Can i install these in europeans tablets?
Thanks
Any ideas?
I have installed it on the US WiFi only version, so I don't see it being a problem, if it doesn't install you can always Odin back to your stock rom... if you have a 3/4g type tablet then you may want to not flash it..... I'm digging the new kernel personally.
Itchiee said:
I have installed it on the US WiFi only version, so I don't see it being a problem, if it doesn't install you can always Odin back to your stock rom... if you have a 3/4g type tablet then you may want to not flash it..... I'm digging the new kernel personally.
Click to expand...
Click to collapse
Thanks
I have installed it in european firmware, portuguese one to be exact (FNAB), no issues at all.
Zootopia said:
I have installed it in european firmware, portuguese one to be exact (FNAB), no issues at all.
Click to expand...
Click to collapse
I installed, thanks, no issues.
Tavocampana said:
I installed, thanks, no issues.
Click to expand...
Click to collapse
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Restorer said:
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Click to expand...
Click to collapse
Theres an app calplled root cloak to hide root from apps. I dont really care on being on stock rom just to get ota lollipop. There would most liekly be a custom rooted lollipop rom when lollipop is out.
DUHAsianSKILLZ said:
Theres an app calped root cloak to hide root from apps. I dont really care on being on stock rom just to get ota lollipop. There would most liekly be a custom rooted lollipop rom when lollipop is out.
Click to expand...
Click to collapse
Unfortunately none of the cloaking apps work on Sky Go or Barclays and other banking apps. Neither does RootCloak or RootCloak Plus Xposed mods .
That is why I asked the question. Not really bothered if it just means losing OTAs - provided everything else is still 100% official unrooted after Odin upgrade of UK tab with HK firmware. That's why I ask will this be the case?
Restorer said:
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Click to expand...
Click to collapse
I do not know.
My intention when the Lollipop version is released is to repeat the procedure and flash via Odin. I live in Argentina and here things come too late.
Tavocampana said:
I do not know.
My intention when the Lollipop version is released is to repeat the procedure and flash via Odin. I live in Argentina and here things come too late.
Click to expand...
Click to collapse
Yeah, I'd do that too. But these apps are too important to me to risk losing them so I will probably just chicken out and wait for the OTA. Thing is, if the update works, I can't see any reason why the root-checking apps would be able to tell except if they were spotting non-UK codes. I do know their checks are a lot more sophisticated than looking only for the presence of SU and busybox. They for sure examine parts of the kernel and the DRM files as well.
My logic tells me that if the apps don't work with the HK firmware then all I need do is to flash back to the official UK XXU1 version. That's why I am just asking is anyone knows of any other differences that might be exposed using the Odin method to update?
Hi everyone!
New Android 7 Developer RUU is out. I remember that there were several problems with the last Android 6 security updates in September and October. So it wasn't possible to root with the latest SuperSU.zip
Instead you had to use an older version and update to the latest version with Play Store later.
Before I flash the Android 7 RUU, I would like to know if anyone already has experience with rooting latest Stock ROM?
Any problems which occurred? And if the root process was successful, which SuperSU Version have you used? Thanks in advance!
Njoatun said:
Hi everyone!
New Android 7 Developer RUU is out. I remember that there were several problems with the last Android 6 security updates in September and October. So it wasn't possible to root with the latest SuperSU.zip
Instead you had to use an older version and update to the latest version with Play Store later.
Before I flash the Android 7 RUU, I would like to know if anyone already has experience with rooting latest Stock ROM?
Any problems which occurred? And if the root process was successful, which SuperSU Version have you used? Thanks in advance!
Click to expand...
Click to collapse
I've used this to root stock Nougat ROM and it worked fine https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Anyway make a backup.. just in case it doesn't work
EDIT: It will reboot the phone at least 2 times before booting into system
Mat08.cc said:
I've used this to root stock Nougat ROM and it worked fine https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Anyway make a backup.. just in case it doesn't work
EDIT: It will reboot the phone at least 2 times before booting into system
Click to expand...
Click to collapse
Do we need to modify system in twrp? before installing this?
shaygia said:
Do we need to modify system in twrp? before installing this?
Click to expand...
Click to collapse
No there's no need, at least I didn't change anything and it worked well
I just wanted to add this as a note as I did not see anyone else having these issues in nougat (7.0). Do not install SuperSU 2.78-201609011115. If you do your mobile data option in the notification bar will be grayed out. Your cell signal will have a slash through it and cell signal will no longer work. I do not know if other versions of SuperSU will also cause this symptom.
If this happens to you restore from a backup in recovery or if need be run the RUU again.
Mat08.cc's linked version of SuperSU does work!!!! Thanks!
My m9 doesn't want to upgrade. After it download the Nougat ,it says that I'm running modified system. My phone is att but converted to developer edition. The way I was updating my phone each time so far was with RUU file and I didn't gave any issues until now. Please help . Thanks in advance.
dohcvtec said:
My m9 doesn't want to upgrade. After it download the Nougat ,it says that I'm running modified system. My phone is att but converted to developer edition. The way I was updating my phone each time so far was with RUU file and I didn't gave any issues until now. Please help . Thanks in advance.
Click to expand...
Click to collapse
Excuse me, I did not understand.. The phone has received the upgrade but can not install it?
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
dohcvtec said:
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
Click to expand...
Click to collapse
Have you installed this one << https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip >> ? (2.78-SR5)
dohcvtec said:
Yes, that is correct. The issue was that my CID was 11111111. Changed it to BS_US001, downloaded, installed successfully. Now I just ran in another issue. Tried to root it so I did: twrp 3.0.2, then installed supersu-v2.78, device booted, cinfirmed rooted but doesn't recognize that there is a sim card inside. Ideas? Thank you!!!
Click to expand...
Click to collapse
Definitely an incorrect SuperSU apk. Use the one in OP of http://forum.xda-developers.com/one-m9/general/nougat-coming-t3513698
Okay. Will try and get back to you. Thanks
P. S. Am I the only ine who is experiencing Messages failing and sending reports to HTC? Ever since I switched to Nougat, every time when I receive/send a text the app fails and when I try to access notifications it fails automatically as well. Ideas? Thank you
idontkn1 said:
Definitely an incorrect SuperSU apk. Use the one in OP of http://forum.xda-developers.com/one-m9/general/nougat-coming-t3513698
Click to expand...
Click to collapse
Reporting back:
After installing the SuperSU that you gave, everything works normally. Thank you very much.
There is an update which my phone didn't want to install. It said that the update is for himaulatt and my phone is himaul. Is it because phone is rooted and with twrp recovery? When I install the update manually via RUU from laptop, works fine. It just pisses me off cause I have tk start from scratch with my phone but update is successful. Had this issue for a while now amd was trying to figure it out. I really don't want to keep wiping the phone every single time there is an update. Thank you in advance.
Best Regards
dohcvtec said:
Reporting back:
After installing the SuperSU that you gave, everything works normally. Thank you very much.
There is an update which my phone didn't want to install. It said that the update is for himaulatt and my phone is himaul. Is it because phone is rooted and with twrp recovery? When I install the update manually via RUU from laptop, works fine. It just pisses me off cause I have tk start from scratch with my phone but update is successful. Had this issue for a while now amd was trying to figure it out. I really don't want to keep wiping the phone every single time there is an update. Thank you in advance.
Best Regards
Click to expand...
Click to collapse
You might want to read the latest posts in the TWRP thread. The important part starts here.
Flippy498 said:
You might want to read the latest posts in the TWRP thread. The important part starts here.
Click to expand...
Click to collapse
I just read the threads you gave me. I understood the process. I will search for the zip file cause this seems to stop me right now. Everything else makes sense from top to bottom. Thank you very much once again.
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.
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 bought an honor 7x in december, it came from China, and the sellers changed the software version from BND-AL10 to the one from Europe BND-L21, I had upgraded my phone once using firmware finder, but I´m a little nervous about doing the big upgrade, I don´t know if there will be any problem because of the version change.
Also, I haven´t recieved any official upgrade, I don´t if it´s because of that or because of my country (I live in Mexico), I´ll appreciate your help
I'm in the same boat. I was wondering if it would be better to flash the AL10 or L21 version of Oreo.
Worst case scenario, I can just choose to wipe the device and flash the AL10 version from scratch for Treble.
The upside, as I just recently found out, is that the bootloader comes unlocked already. It's pretty fortunate considering that they took down the website to unlock the bootloader.
ahmad.o said:
I'm in the same boat. I was wondering if it would be better to flash the AL10 or L21 version of Oreo.
Worst case scenario, I can just choose to wipe the device and flash the AL10 version from scratch for Treble.
The upside, as I just recently found out, is that the bootloader comes unlocked already. It's pretty fortunate considering that they took down the website to unlock the bootloader.
Click to expand...
Click to collapse
Yes I know want too
Well, I used Firmware Finder to download the Oreo update and, to my surprise, it worked perfectly. I went straight from B101 to the newest version. After updating I formatted the device and installed phh's GSI, and it's working great.
ahmad.o said:
Well, I used Firmware Finder to download the Oreo update and, to my surprise, it worked perfectly. I went straight from B101 to the newest version. After updating I formatted the device and installed phh's GSI, and it's working great.
Click to expand...
Click to collapse
Hi Ahmad, just curious. Where are you based and which if the 2 options did you consider to download the firmware and also did the checking firmware access mention it is not approved for your device or was it approved. Thanks for your feedback in advance.
My experience as mentioned by someone else in the forum was that it is not approved and hence even after downloading the files it didn't get installed.
wifeS3 said:
Hi Ahmad, just curious. Where are you based and which if the 2 options did you consider to download the firmware and also did the checking firmware access mention it is not approved for your device or was it approved. Thanks for your feedback in advance.
My experience as mentioned by someone else in the forum was that it is not approved and hence even after downloading the files it didn't get installed.
Click to expand...
Click to collapse
I'm from Canada, and I chose the second-last option for 8.0 on the L21-C432 section of Firmware Finder. It said it was approved, although in the past when I tried updating even if it was approved it didn't work.
Thanks bro. Appreciate the prompt response. Guess I will just have to wait till my turn comes in India