Develop Bugs

Problem with RETEU firmwares on chinese ADDISON_RETCN (XT1635-03)

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)

December ROM update for BLN-L24

My 6X just received an OTA. The security patch level went from March 1st to Oct 5th. The EMUI version was updasted to 5.0.1. So far so good, I haven't used it much.

Akopps said:
My 6X just received an OTA. The security patch level went from March 1st to Oct 5th. The EMUI version was updasted to 5.0.1. So far so good, I haven't used it much.
Click to expand...
Click to collapse
But, those updates are gradual? since my cell phone has not received it

I have gotten an OTA update as well. Not sure if it's going to remove my root or not so I'm not going to update

patrick8996 said:
I have gotten an OTA update as well. Not sure if it's going to remove my root or not so I'm not going to update
Click to expand...
Click to collapse
Same here.

Yep it will remove you current root... Cause i just updated too it a few hours ago which i did not have root but i had my bootloader unlock. And yep my bootloader is locked ... I have always herd ota updates doeisnt relock the bootloader???
Not going too unlock it again cause i was waiting for 8.0 if and when it comes anyways. That and i have my phone setup the way i want it not going threw it again at the moment lol..

iamshadow2008 said:
Same here.
Click to expand...
Click to collapse
You can't update without removing root

iamshadow2008 said:
Same here.
Click to expand...
Click to collapse
You need to remove root, flash stock boot and stock recovery before you download the ota for installation.

Just updated but now Google Assistance no longer works and fail to connect.
I have to clear Google app all data to make it run

e20140 said:
Just updated but now Google Assistance no longer works and fail to connect.
I have to clear Google app all data to make it run
Click to expand...
Click to collapse
Factory reset..

Wow. Two system updates in the last 10 days. Just updated BLN-L24C567 to B366 from B365. Security patch is Nov. 6.

I guess this makes Huawei/Honor phones a lot better than Lenovo Moto phones. Once I recommended my father to buy a (Lenovo) Moto X Pure. The phone received updates something twice a year (!), and its Nougat update came 13 months (!) after the official Nougat release, and maybe 10 months after when Lenovo promised this update would be available. Huawei has a better track record than Lenovo IMHO.

13 months is a lot, and yes, Huawei/Honor has been better in the recent years when it comes to updates

Indeed. They give update if want to else simply discard. btw see what Apple was doing with regular updates.. they admitted and was a let down for many (but accepting it needs some real guts for a brand like Apple)
Who knows other OEMs who gives regular updates are doing similar things

edit: scratch that

Moto Z2 Force not getting OTA updates

I have a ATT branded Moto Z2 with a Cricket SIM. I got the phone in late november, and it came with Android 7.1.1 with the June 1 SPL. I know that ATT has released several updates, the latest in December with the November 1st SPL,
but everytime I check for updates it says that my phone is up-to-date.
So far I tried to check for updates after a factory reset, and also tried to do an OTA update with an old ATT SIM in it. Nothing seems to be working.
I have posted on the lenovo support page but so far I have not got any answer. I am not the guy that has to have the latest software running, but the updates fixed the BlueBorne security hole...
Othat than using a Cricket SIM, the phone is stock, not rooted.
has anybody encountered the same problem? Thank you

So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
ululi said:
I have a ATT branded Moto Z2 with a Cricket SIM. I got the phone in late november, and it came with Android 7.1.1 with the June 1 SPL. I know that ATT has released several updates, the latest in December with the November 1st SPL,
but everytime I check for updates it says that my phone is up-to-date.
So far I tried to check for updates after a factory reset, and also tried to do an OTA update with an old ATT SIM in it. Nothing seems to be working.
I have posted on the lenovo support page but so far I have not got any answer. I am not the guy that has to have the latest software running, but the updates fixed the BlueBorne security hole...
Othat than using a Cricket SIM, the phone is stock, not rooted.
has anybody encountered the same problem? Thank you
Click to expand...
Click to collapse

Chrisy8s said:
So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
Click to expand...
Click to collapse
At least the T-Mobile versions can be rooted. As far as I know, the ATT cannot as of yet.

theres only been one update since august and thats a fixed august. the other being the oreo update thats available now
if you would like to update your phone we have the ota updates and can get you updated without unlocking your bootloader just let me know [email protected] on hangouts

Chrisy8s said:
So I have two Tmobile versions of this phone. one rooted/unlocked, one not. I am also having a problem with receiving OTA. Mine stock device is on an August Security patch and there have been two released patches since then. I just got off the phone with both motorola and tmobile and they are both useless. I explained over and over that i wasn't calling about the oreo release, that i was calling about ANY updates and they couldn't get that through their head. Further, tmobile states they haven't released an 8.0 ota which we all know is false since several people on this forum have received it.... very frustrating. I may have to unlock my stock device if I ever want an actual update.
Click to expand...
Click to collapse
What OTA for Tmobile? Mine has NCX26. 7 as stated in Tmobile support site, I do know that OCX oreo release is suppose to be live but support site doesn't show it andy phone hasn't gotten it.

Found a way to get it to download updates.
So, after wasting my time with Motorola and ATT so-called "technical support", I decided to try something: I rebooted the phone in recovery mode (VOlume down + Power button) and put it in recovery mode. Rebooted from recovery mode, and bingo, it downloaded the next update (September SPL). It now shows "background installation..." in progress. Hopefully this is going to be the solution.

I did the update manually using the file nash_opx 27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC. Xml. zip and it worked perfectly.

djsboy said:
I did the update manually using the file nash_opx 27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC. Xml. zip and it worked perfectly.
Click to expand...
Click to collapse
I think I may have found the right recipe. The trick is to check for updates while NOT on WiFi. So move away from WiFi coverage, but still within Cell coverage, with Data on. Check for updates. It will say that an update is available and will be download when within WiFi range. Move back to where you have WiFi, and bingo, it will start downloading. I did it twice yesterday afternoon, once to go from the Sept to the Oct SPL, and then from the Oct SPL to the Nov SPL, which is the last available update according to the ATT page. All of this with my Cricket SIM. WHy this works is beyond my pay grade to figure out. I will eagerly wait for the next update to be posted to see if this trick works consistently. Again,
this seems to work with my ATT branded phone.

My ATT Z2 force, starting from last evening (1/24/2018), kept getting security update, from September, 2017. Then this morning, October 2017 and November 2017. Does this mean we are going to get Oreo update soon ?

So I've had my Moto zforce 2 for 3 days now. We're is the Oreo update ? T-Mobiles site says it was released Dec 22nd ?

lcc014 said:
My ATT Z2 force, starting from last evening (1/24/2018), kept getting security update, from September, 2017. Then this morning, October 2017 and November 2017. Does this mean we are going to get Oreo update soon ?
Click to expand...
Click to collapse
Dude..Let us know when u get Oreo update....So am I

Anyone on TMobile receive the ota update ?

There are issues with calling and sms on the T-Mobile variant. The update has been pulled while they sort out the issues.

Well that makes sense why I'm not seeing it then.

I am still not able to get the AT&T update past June. I tried the reboot into recovery and nothing. Is there a way to manually install the update from an SD card which would allow for OTA updates in the future?

TheLooq said:
There are issues with calling and sms on the T-Mobile variant. The update has been pulled while they sort out the issues.
Click to expand...
Click to collapse
Good. On my account we got 2 of them for Christmas. A few days after Christmas, one of them updated to Oreo. At this point, the Galaxy S7 Edge on our account could not hear the Z2 Force. Went through everything with T-Mobile support including network settings reset, factory resetting both the Samsung and Motorola phones. Didn't fix it. Meanwhile, the Z2 Force that was still on Nougat was fine. A few days later, it also updated to Oreo, and now neither Z2 Force can be heard on the Samsung. I hope they get this mess cleaned up soon since it's been a month.

It seems to be only between those two phones. Until the next update/patch is released, the workaround is to disable VoLTE in call settings on the z2.

Got AT&T update to 8.0.0 this morning.

I received notice of the Tmobile Oreo update, downloaded it, but cannot install it. It only says something went wrong and didn't install the update. I have the bootloader unlocked and Magisk installed. I followed the instructions for Magisk dual partition updates. I uninstalled Magisk using Restore Images and did not reboot. I went to System Updates and downloaded the update again. It never went to Security Update Installing, step 1. I am on Magisk v 16.0 which passes the SafetyNet check, ctsProfile: true and basicIntegity: true. At this point, should I completely uninstall Magisk, flash the OreoFlashAll.zip or the NASH_TMO_C_OCX27.109-36_subsidy-TMO-regulatory-DEFAULT_CFC.xml.zip? Or something different?

lcc014 said:
Got AT&T update to 8.0.0 this morning.
Click to expand...
Click to collapse
Let us know if you lose the animated home button as I did after the At&t update. I asked the question in the room and no one answered. Hopefully I didn't break any rules by asking here. Thank you.
Sent from my Moto Z (2) using Tapatalk

OTA update with bootloader unlocked, no root, 2 XL

I am a bit confused by all the posts about this subject
I would like to unlock my phone, for future rooting, when everything is more stable, meanwhile I want to get OTA updates on the phone "automaticaly", is that possible

You can definitely unlock the bootloader and still receive OTA.
And for your first point, rooting is plenty stable already, so no need to wait for that. Though if you aren't well versed in fastboot or root upgrade processes, you should definitely read all the most recent guides on it to make your transition smoother.

Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time

melorib said:
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
Click to expand...
Click to collapse
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.

wtherrell said:
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
Click to expand...
Click to collapse
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions

melorib said:
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
Click to expand...
Click to collapse
There's issues with Magisk and some other phones, but topjohnwu has a Pixel 2 I believe, so he tests on that.
Magisk for our phones is perfectly stable, the only issue is people don't like the dtbo image being edited to remove AVB 2.0/dm-verity.

My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October

canemaxx said:
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
Click to expand...
Click to collapse
Strange, there was at least an update in January

Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device

canemaxx said:
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
Click to expand...
Click to collapse
Why? I want OTA updates...

I'm not sure why they just have not come to my phone.

canemaxx said:
I'm not sure why they just have not come to my phone.
Click to expand...
Click to collapse
You only unlocked the bootloader? Maybe because it is Verizon, the bootloader is supposed to to be locked!

I can't see that being the reason as I bought the phone from the Google store

canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
Sounds strange, maybe you updated before OTA was available for Verizon...
In 2 weeks I get mine, going to unlock before any update, it was bought December, so it has at least one update missing...

canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.

v12xke said:
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
Click to expand...
Click to collapse
Thanks I know how to sideload or flash the full image but just was hoping I wouldn't have to again and again

Are your phones enrolled on the Android Beta Program ? My P2 was and I never got the Jan. Update till I Unenrolled from the beta program. Immediately afterwards I checked and Jan update was available.

Android 9 Pie update

Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?

Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.

Not yet available on my nokia 6.1. I think we are a couple of weeks away from the update.

Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Which TA....?

Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)

EricH7001 said:
Which TA....?
Click to expand...
Click to collapse
TA-1045

prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I'm on the June 1st level

prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?

Mobe1969 said:
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Click to expand...
Click to collapse
That makes sense cause I keep getting installation failure and not sure if it even downloaded.

Ozonethegreat said:
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Click to expand...
Click to collapse
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way

prg318 said:
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
Click to expand...
Click to collapse
Are the WW images the chinese version I seen floating around here? If not, where did you get them?

Ozonethegreat said:
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Click to expand...
Click to collapse
Nope - don't think its Chinse - it appears to be a "global" or international version. I don't really notice a difference from my original stock.
I got it from here: https://forum.xda-developers.com/no...-to-flash-global-firmware-pl2-222e-0-t3831764
And was able to flash the "extracted version" with fastboot. I used some fastboot instructions that I found for a chinese rom and changed the filenames to match the worldwide filenames and it worked without the OST tool

Ozonethegreat said:
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Click to expand...
Click to collapse
Can you locate the downloaded OTA and post it here?

Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Were you able to update to Android pie?

Danny1976 said:
Were you able to update to Android pie?
Click to expand...
Click to collapse
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...

Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Can you check under system partition and look for Data/OTA
---------- Post added at 04:37 PM ---------- Previous post was at 04:14 PM ----------
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
Check system partition under data/ota.

Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
You should have pulled the OTA link from a logcat so the rest of us can download the update files and upgrade ourselves :/

I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.

Danny1976 said:
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Click to expand...
Click to collapse
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?

neowlchaz said:
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
Click to expand...
Click to collapse
I got the July update in July and then I got the August update on August. I don't know why yours took a while to update. Mine and other that I know, get the update for the month the same month.