1055 uk version 8.1 june pach
was stack on 8.0. changed plusnet sim (runs on EE network) for ( not working one) from freedompop, but didnt have other so tried) and suddenly 3 updates within hour.
first 8.1 with May security
after reboot somethin 22a fix
another reboot june security patch
must be something EE is doing to updates. i bought sim free from John Lewis but still had EE app installed after turning on phone or it instaled itself without my permision as i have put sim in slot before turning phone on. so deleted it but still couldn't get updates.
put in different sim and updated immediately .
might be bug only, but finally do have last updates
Related
This just showed up this morning, automatically downloaded and I installed. Not Marshmallow but it is the June security patches. I haven't seen any other changes they've made and the Samsung version page hasn't been updated for the versions for these security releases either.
As for the delay of Marshmallow, I suspect it's because of the bug that was found during the upgrade where users are locked out of the phone. Working in a software development shop myself, my guess is AT&T may be waiting for this to be fixed by Samsung, who would then push another build out for them to work with. I could be wrong, but that's my sense. Personally, I'd rather wait for that fix than have to deal with a workaround (disabling the fingerprint reader, etc.) or risking being locked out. Hoping for sometime this summer, but we'll see ...... anyone have any contacts on the inside that may be able to hint at something???
mattsternc said:
This just showed up this morning, automatically downloaded and I installed. Not Marshmallow but it is the June security patches. I haven't seen any other changes they've made and the Samsung version page hasn't been updated for the versions for these security releases either.
As for the delay of Marshmallow, I suspect it's because of the bug that was found during the upgrade where users are locked out of the phone. Working in a software development shop myself, my guess is AT&T may be waiting for this to be fixed by Samsung, who would then push another build out for them to work with. I could be wrong, but that's my sense. Personally, I'd rather wait for that fix than have to deal with a workaround (disabling the fingerprint reader, etc.) or risking being locked out. Hoping for sometime this summer, but we'll see ...... anyone have any contacts on the inside that may be able to hint at something???
Click to expand...
Click to collapse
I don't mind getting locked out as long as I get Marshmallow
If I am out of the country, i can download via OTA this update ?
Im already in Europe and OTA say "Current software is up to date"
I have baseband version: G900AUCU4COI5
I am having issues with firmware ending bra5 my data connection keeps on dropping and I have to turn on and off airplane mode. Can I downgrade to bql5? I think that's what I had before updating. I am on Verizon. Please help. Thank you
Become a member of the world
Nope, you can't downgrade the bootloader
Caliskyhigh said:
I am having issues with firmware ending bra5 my data connection keeps on dropping and I have to turn on and off airplane mode. Can I downgrade to bql5? I think that's what I had before updating. I am on Verizon. Please help. Thank you
Become a member of the world
Click to expand...
Click to collapse
FWIW, I'm on 3BRA6 and have had some instability on WiFi connection disconnecting.
Regarding "downgrading", generally you can as long as to older version you want to go back to has the same bootloader.
In this case, unfortunately 3BRA5 has the new V3 bootloader. So we'll just have to wait for the February security patch and hope that fixes the issue.
So I installed the new Feb security patch on Verizon note 8, it seems to be working fine for now. Thank you for the help.
Cant downgrade but you can upgrade. Can install BRA6, BRA8 or BRA9.
Caliskyhigh said:
So I installed the new Feb security patch on Verizon note 8, it seems to be working fine for now. Thank you for the help.
Click to expand...
Click to collapse
Welcome. Come back in a couple of days and let us know how it's working.
So it's confirm the Feb Verizon security patch update fixed the lte/wifi connection issues. If your having issues with let or wifi on Verizon note 8 go ahead update.
Hi. I have a nokia 7 plus TA-1046 build 00WW_2_22M
The problem is that i have this phone for last year and i am stuck at 8.1 August 1 Security update. I check regularly for updates but besides one security update nothing. I am from Romania dunno if that matters. On every forum i saw people on pie and i am stuck onto oreo. Is there any connection with my network provider or ota is from nokia. I got an android one for the fuss of being up to date. And i am behind so many other phones on updates. I did nothing on the phone downgrade upgrade kernel ROMs. Its clean. I also tries some variants that support from nokia gave me. Like remove sim and conect to wifi and try. Go into safe mode and try from there to. Clean catch from carrier service and remove sim and go and check. None work. Any ideas for a proper non warranty removed method to get an update?
Yes, just download the update and flash it yourself. It isn't very hard and the effect is the exact same as an OTA update so it doesn't void your warranty.
Better stay in oreo cause this latest pie
updates bricked my wifi and sd card
8i advice you to keep the phone with oreo.
ntzntz said:
Hi. I have a nokia 7 plus TA-1046 build 00WW_2_22M
The problem is that i have this phone for last year and i am stuck at 8.1 August 1 Security update. I check regularly for updates but besides one security update nothing. I am from Romania dunno if that matters. On every forum i saw people on pie and i am stuck onto oreo. Is there any connection with my network provider or ota is from nokia. I got an android one for the fuss of being up to date. And i am behind so many other phones on updates. I did nothing on the phone downgrade upgrade kernel ROMs. Its clean. I also tries some variants that support from nokia gave me. Like remove sim and conect to wifi and try. Go into safe mode and try from there to. Clean catch from carrier service and remove sim and go and check. None work. Any ideas for a proper non warranty removed method to get an update?
Click to expand...
Click to collapse
Buna seara / hello,
I think you should manually update. Follow this
https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774/page99
I have a TA-1046 dual SIM, international version (yours is probably the same).
I was stuck first on Oreo 8.0 in April and I had to manually update to 8.1. After that I got OTAs without any problems until the Pie update.
In September I had to manually update to Pie, but since then I got every OTA.
Everything works fine, no issues with WIFI. I do not use an SD card. Pie is better than Oreo and you need the latest security patches.
Mult succes.
It's interesting that some people don't have any issues with last updates but quite a lot of people have the same issues i have,today i tested my friend's phone and has the same firmware like i do but yet no issues for him
Btw: before you upgrade, august is last version can be unlocked
I updated my moto x4 from Oreo to pie using flash using boot loader. my boot loader is still locked and software status is official too. It still is unable to update to January security update. Please help !!
yes I have also facing same issue... i have also try by safe mode but shows something not right .... reconnecting to server... might be Moto update Services try to connect moto server which has not able to connect due some issue in server... hope so this is issue...
you can connect to moto support team let me know what they are say for this issue.
They told to reset and try again.. to do that I got to backup my data which LL take time.. so on hold as of now
Yup, same here. I got the Android 1 Google Fi model (Bootloader unlocked, unrooted). I'll try again in a week and see if it resolves itself.
And another ~ bought 2, mine showed the update 3 days before my wife's but won't start (download and install now, via wifi only and it reverts back to the settings screen). She got the notification last night and it took first try. First time I've had this issue in the 4 months I've had the phone, just glad I'm not alone here....
Since you're official/fully stock, there's not really any alternatives besides factory reset or await for full image is available to manually flash via fastboot method. You do not need to unlock long as you stick with motorola firmwares. Links in FAQs thread.
Nothing new here? Mine keeps nagging me to do the update, start it and it shows getting to 17% on step 3 of 6, then just kicks me back out to the setting screen.
This is my first android phone (from a flip), couldn't get lineageos to work with my provider (RedPocket) and have neutered as much of the google crap as possible. Right on down to disabling all permissions for Play Store. Could that be part of my issue?
It has been nagging me since last few weeks, no solution apparently
New Update:
Could actually able to fix the issue by installing a vpn and set it as a USA based server.
My phone was bought in US and I was using it elsewhere. After using an USA based IP it downloaded the update and voila.
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Apparently happens to some users when they update to December.
Just delete your old face data as it says and rescan.
WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Some have reported the same issue when updating to December via fastboot with a wipe and clean install. Sometimes a factory reset works, other times not. Luckily, the January update is around the corner. Hopefully it is fixed by then
WhiteReign said:
Enrollment was not completed
Cant store new face data. Please delete the old one first.
Any one run into this?
I am on 10.0.0 (QQ1B.191205.012.A1, Dec 2019)
Its was bought from google. Not sure what I did wrong
Click to expand...
Click to collapse
Mine happened a little different when updating to this version. My Face info was saved from the previous version but wasn't working 100% of the time. I deleted my cached face data and tried to retake but the blocks weren't showing on the face capture. So I then disabled all unlock methods, rebooted the phone and then tried to set up a pin and face again and everything worked as it should.
enrollment was not completed ( face enrolment didn't work)
ibphantom said:
Mine happened a little different when updating to this version. My Face info was saved from the previous version but wasn't working 100% of the time. I deleted my cached face data and tried to retake but the blocks weren't showing on the face capture. So I then disabled all unlock methods, rebooted the phone and then tried to set up a pin and face again and everything worked as it should.
Click to expand...
Click to collapse
It happened for me as well ( Pixel 4) after I've downgraded from Android 11 Beta to the latest stable 10.0.0 (QQ3A.200605.002, Jun 2020) via the Android Flash Tool.
I tried to factory reset my phone few times, even deleted Esim. Nothing helped ( could do register my face during phone setup or later after I skipped it)
I tried different builds but the only 1 which worked for me 10.0.0 (QD1A.190821.007, Oct 2019). I was able to register my face-unlock, lock bootloader and receive the latest OTAs.
I flashed this build with Platform Tools and also changed the configured security key instead of the Pin during setup.
Not sure if this was an issue with Android Flash Tool or Pin security.
Update
xorwin said:
It happened for me as well ( Pixel 4) after I've downgraded from Android 11 Beta to the latest stable 10.0.0 (QQ3A.200605.002, Jun 2020) via the Android Flash Tool.
I tried to factory reset my phone few times, even deleted Esim. Nothing helped ( could do register my face during phone setup or later after I skipped it)
I tried different builds but the only 1 which worked for me 10.0.0 (QD1A.190821.007, Oct 2019). I was able to register my face-unlock, lock bootloader and receive the latest OTAs.
I flashed this build with Platform Tools and also changed the configured security key instead of the Pin during setup.
Not sure if this was an issue with Android Flash Tool or Pin security.
Click to expand...
Click to collapse
Actually it stopped working in a few hours or so. Found out that this issue started from DP4 when you fastboot back to stable.
As a workaround, I opted to Beta again, where Face-Unlock Works. Then I opted out and received OTA stable and issues with Face recognition were gone. Yaaay
The latest Telstra june image fix the face id issue when downgrading from Android 11, the buid number is QQ3A.200605.002.A1
gm007 said:
The latest Telstra june image fix the face id issue when downgrading from Android 11, the buid number is QQ3A.200605.002.A1
Click to expand...
Click to collapse
What is the difference between this one and the standard version?