Related
I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?
kmandel said:
I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?
Click to expand...
Click to collapse
I have run all the MRA builds (K, N, R) on T-Mobile and they all support and have fully functioning WiFi calling, Band 12 support, and VoLTE. Not sure what's specific about X but I decided to switch to it just because it's "official".
Sent from my Nexus 6 using Tapatalk
nnorton44 said:
I have run all the MRA builds (K, N, R) on T-Mobile and they all support and have fully functioning WiFi calling, Band 12 support, and VoLTE. Not sure what's specific about X but I decided to switch to it just because it's "official".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
How did you switch? Did you flash a 5.1.1 factory image and then take the OTA?
kmandel said:
How did you switch? Did you flash a 5.1.1 factory image and then take the OTA?
Click to expand...
Click to collapse
For X I flashed the factory ProFi 5.1.1 then sideloaded the 48I to 58X OTA.
T-Mobile and ProFi will both use X.
Sent from my Nexus 6 using Tapatalk
I hope there's a factory release. Please post here if anyone gets it
kmandel said:
I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?
Click to expand...
Click to collapse
Someone posted about this on the Android Central comments section: http://www.androidpolice.com/2015/1...etting-an-over-the-air-update-to-marshmallow/
Looks like if you are on K you will get the X updated OTA
blazinazn said:
Someone posted about this on the Android Central comments section: http://www.androidpolice.com/2015/1...etting-an-over-the-air-update-to-marshmallow/
Looks like if you are on K you will get the X updated OTA
Click to expand...
Click to collapse
According to the T-mobile document
https://support.t-mobile.com/docs/DOC-18109
It's only the L* releases that can be updated with the OTA.
kmandel said:
According to the T-mobile document
https://support.t-mobile.com/docs/DOC-18109
It's only the L* releases that can be updated with the OTA.
Click to expand...
Click to collapse
I don't see where it says *only* L releases get the update but it may just be a matter of semantics.
"To be able to update to the current software version, the below requirements must be met:"
^^^ I take this to mean that you must have at least L to get the update. If you are on M already then you still meet that requirement. That's just my thoughts though. Dez is always in the know and that's what he said. Guess we'll just have to wait and see.
i am completely unable to install mra58x no matter how i try to sideload the update from 5.1.1
Tmobile goes back to MRA58K
It confused me.
https://i.imgur.com/vQYNKiL.jpg
I got the ota today, from 28m
Sent from my Nexus 6 using XDA Free mobile app
joshtb86 said:
i am completely unable to install mra58x no matter how i try to sideload the update from 5.1.1
Click to expand...
Click to collapse
I noticed that your signature says "Nexus 6 rooted". If that is in fact the case, you will not be able to install any OTA. Neither via sideloading nor "over the air". The installer looks at the system file, and if there is ANY change from stock (including being rooted), it will abort the install. I've had it fail, even with a couple of apps frozen.
It looks like the document
https://support.t-mobile.com/docs/DOC-18109
has been updated. It now list MRA68K as eligible for the OTA to MRA68X. Earlier
it just listed the L* releases.
cam30era said:
I noticed that your signature says "Nexus 6 rooted". If that is in fact the case, you will not be able to install any OTA. Neither via sideloading nor "over the air". The installer looks at the system file, and if there is ANY change from stock (including being rooted), it will abort the install. I've had it fail, even with a couple of apps frozen.
Click to expand...
Click to collapse
yeah tried on a clean flash without root, still not luck
i installed mra58k clean rom from the andriod dev page until someone makes an X rom
Wow
And for those with MRA58N currently, there was a hint that TMO would OTA push MRA58X as well.
I am starting to think that was Des speaking before he had the details
Sent from my Nexus 6 using Tapatalk
Dougshell said:
I am starting to think that was Des speaking before he had the details
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Check their support web site
Sent from my Nexus 6 using Tapatalk
I see they added it. Well again, sitting here with a nexus device, waiting.
Sent from my Nexus 6 using Tapatalk
BigDig said:
Check their support web site
Click to expand...
Click to collapse
TMO's update site is questionable in and of itself.
New update just pushed to my Verizon S6 Edge. Not sure what was in it yet. Can't seem to find a changelog anywhere. I'll do some more looking and post back if I find something. May be just another Security Update?
Software Version: NRD90M.G925VVRU4DQF3
This software update provides:
The latest Android® security patches
Fixes ringback tone playback to non-Verizon Wireless phones
Actually after I used VZW software upgrade assistant (I switched to Tmobile, so can not do update by OTA), the version is DQH1, not DQF3.
Android Safety Patch is 8/1/17.
[email protected] said:
Actually after I used VZW software upgrade assistant (I switched to Tmobile, so can not do update by OTA), the version is DQH1, not DQF3.
Android Safety Patch is 8/1/17.
Click to expand...
Click to collapse
I believe the updates are specific to your carrier. This update was specific to Verizon users. If you are now on T-Mobile, you should receive a different update when T-Mobile issues one.
I can not receive update from Tmobile. My phone is from Verizon. They are different in some hardware I believe.
Zelmo88 said:
I believe the updates are specific to your carrier. This update was specific to Verizon users. If you are now on T-Mobile, you should receive a different update when T-Mobile issues one.
Click to expand...
Click to collapse
I thought I'll make this thread for the Australian Mate 20 Pro Owners.
As we may all know already, Optus and other ozzy telcos are extremely slow with releasing there updates for our devices, it's very frustrating as we have to wait for important updates and fixes.
In this thread I'll love to hear from other Australians and there opinions on this matter. Also to discuss firmwares that have been flashed from other regions on our devices etc
All topics about our devices are all welcome
I have the L29. Currently with Telstra (Prepaid)
My last OTA update was 168 which I received around the end of December.
I recently unlocked my bootloader and updated to 182 following a guide in these forums
I also rooted my device using the same guide.
I don't really have too much to say on the speed of our updates, as I've only had my Mate 20 Pro since the 28th of Dec. It's my first android phone and I'm loving it so far. I've been wanting to get away from Apple for years, but the jailbreaking scene kept me with them. Now that the scene is almost dead I decided it was time.
So now I'm getting my head around rooting.
LYA-L29 here.. C636 SPCSEAS region on mine.
Have done the fh 171 update.. Now on unlocked bootloader and rooted 182. Tried the custom 182 rom but no joy with magisk in hiding safety net stuff for Google pay.. However with the stock 182 I was able to hide the safety net checks with magisk help.
What might be of interest to people to is I've been able to downgrade back to 171 and relock bootloader which previously was said could not happen. Back on 182 though now.
Currently running an L29 bought from eBay AU but originated in the UK as far as I can tell (based on the charger mains plug)
Latest version It'll update to is .168, it started off at .109 and has done 2 updates in the 2 days I have had it.
I've ordered a BL code and will look at rooting once I have it, there seem to be 2 different guides in this forum at the moment. Still working out which way to go. One of the methods definitely involves rebooting into recovery every time in order to get root, not sure if the other method does as well.
I find the 182 firmware to be a great one, I have noticed more of a battery drain on this one but nothing to really worry about.
I find it awesome that the hwota method works and we are now able to flash the same or higher firmwares with pretty much ease now. To be honest everytime I fiddled with my phone before the hwota method came out I would stuff something up then use funky Huawei to bring it back to life lol that was beginning to be an expensive venture haha.
This device shows alot of promise, I am currently using magisk and have used modules to pass safety net. Also used titanium backup to remove some system apps I never use. I froze Huawei home and now use nova launcher and used the Google framework module to install the Google phone and contacts app which I find much better. I am happy to say I now have the device exactly where I want it to be. I have also added a 64gb Huawei nano memory card to my device, as it may be expensive I thought why not. Now all my photos get saved to memory card
Minotaur said:
Currently running an L29 bought from eBay AU but originated in the UK as far as I can tell (based on the charger mains plug)
Latest version It'll update to is .168, it started off at .109 and has done 2 updates in the 2 days I have had it.
I've ordered a BL code and will look at rooting once I have it, there seem to be 2 different guides in this forum at the moment. Still working out which way to go. One of the methods definitely involves rebooting into recovery every time in order to get root, not sure if the other method does as well.
Click to expand...
Click to collapse
The patched_boot.img method is what I'm using basically when the phone reboots it automatically boots up the patched_boot and goes straight into the os, you don't even notice it which is great
souljasteve84 said:
The patched_boot.img method is what I'm using basically when the phone reboots it automatically boots up the patched_boot and goes straight into the os, you don't even notice it which is great
Click to expand...
Click to collapse
Which one is that? Can you provide a link to the thread/guide?
Cheers.
Minotaur said:
Which one is that? Can you provide a link to the thread/guide?
Cheers.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-20-pro/how-to/guide-unlocking-bootloader-magisk-root-t3885422
Minotaur said:
Which one is that? Can you provide a link to the thread/guide?
Cheers.
Click to expand...
Click to collapse
Basically grab the recovery_ramdisk IMG and use that in magisk to get a patched_boot.img that would be the best way but in the guide it's got all the info you need there.
souljasteve84 said:
Basically grab the recovery_ramdisk IMG and use that in magisk to get a patched_boot.img that would be the best way but in the guide it's got all the info you need there.
Click to expand...
Click to collapse
According to that page, that method requires booting into recovery mode all the time?
Minotaur said:
According to that page, that method requires booting into recovery mode all the time?
Click to expand...
Click to collapse
It doesn't it does it automatically you won't even notice
LYA-L09 from Optus here still on .122, with .146 due end of this month. Optus update schedule is a joke. As soon as FH .182 is safety net approved, I'm doing it. Don't really want to pay the $70 to unlock bootloader but will likely do that too eventually.
Yes Optus is a joke. Hopefully they start working on .171 which is supposed to have a unlock bootloader although I am sure optus will modify it to stay locked.
Sent from my HUAWEI LYA-L09 using XDA Labs
Optus are still stuffing everyone around with not yet releasing an almost 2 months old firmware. All they can do is give you a recorded message.
They certainly are the most pathetic telecommunications company.
Sent from my HUAWEI LYA-L09 using XDA Labs
It seems to have come to light that optus won't be supplying firmware updates, 2 reasons were mentioned today
1 is that huawei have not issued a software licence and will not provide optus with firmware.
2 is that optus have abandoned huawei firmware updates because of the huawei 5G and US ban with regards to spying.
All the times optus have mentioned testing firmware for the mate 20 Pro has been lies, it now is apparent that they were never testing anything.
This matter via being addressed by me in writing to both Huawei and optus, if they fail to respond or provide a firmware update solution. Consumer Affairs Victoria will be filing a complaint against them con VCAT Court.
Sent from my HUAWEI LYA-L09 using XDA Labs
Is your phone Optus branded specifically? Could you go and buy a Telstra prepaid SIM, chuck that in, and update the phone?
Minotaur said:
Is your phone Optus branded specifically? Could you go and buy a Telstra prepaid SIM, chuck that in, and update the phone?
Click to expand...
Click to collapse
It's got the optus splash screen and has firmware modified by optus and huawei for optus specific handsets.
Sent from my HUAWEI LYA-L09 using XDA Labs
Minotaur said:
Is your phone Optus branded specifically? Could you go and buy a Telstra prepaid SIM, chuck that in, and update the phone?
Click to expand...
Click to collapse
No, updates are handled by the firmware supplier(Optus) no matter what SIM you put in it
Optus is awesome
Android Software Updates - 07/12/2018
On Hold, waiting for updates on DBU
Click to expand...
Click to collapse
Android Software Updates - 21/12/2018
Update – VoWiFi + preloaded Google input
Build: LYA-L09 9.0.0.146(C34E11R1P16)
Status: Testing
Estimated release: Early – Mid January
Click to expand...
Click to collapse
Android Software Updates - 07/01/2019
Update – VoWiFi + preloaded Google input
Build: LYA-L09 9.0.0.146(C34E11R1P16)
Status: Testing
Predicted release: Late January
Click to expand...
Click to collapse
Android Software Updates - 29/01/2019
Update – VoWiFi + preloaded Google input
Build: LYA-L09 9.0.0.146(C34E11R1P16)
Status: Testing
Predicted release: Late January
Click to expand...
Click to collapse
Android Software Updates - 07/02/2019
Upgrade to 9.0.0.183
Status: Testing
Estimated testing completion timeframe: mid-late February
Click to expand...
Click to collapse
So what, they get so far and over a month just to give up on .146 ... I can't wait for another month of testing .183 just for them to give up on that
Xalies said:
No, updates are handled by the firmware supplier(Optus) no matter what SIM you put in it
Optus is awesome
Android Software Updates - 07/12/2018
Android Software Updates - 21/12/2018
Android Software Updates - 07/01/2019
Android Software Updates - 29/01/2019
Android Software Updates - 07/02/2019
So what, they get so far and over a month just to give up on .146 ... I can't wait for another month of testing .183 just for them to give up on that
Click to expand...
Click to collapse
They are not testing .183 they are supposed to be working on .188 but at this point optus don't have a software licence from Huawei, and huawei are refusing to release the firmware until they get a licence approved.
This could be months or not even happen at all
They also have never been testing any firmware because huawei have never released any to them for testing as to date.
Here is the message I received from Optus last week.
Hey Darren,
This is what I recieved internally from our Tech devs,
For Australian carriers, Huawei will release MR every 2 months. They do not know the release details until about 1 month before the release. They have skipped .146 and .183 because they did not meet Optus requirements. We are going to get .188 for testing which is the later version than .183. The only way for the customer to get .183 is to buy an open market handset.
So we're all still on .122 ?
I want to say "un ****ing believable" but it's really not.
It's simply not good enough
Hi all,
I bought an unlocked note 9 from eBay which arrived today. I got it set up and went to begin installing a different firmware to be able to get the one UI update - only to find out it's a N960U1! I'm in the UK so was expecting/hoping for a N960F.
It's all working, calls work, I've pulled over 3GB of data today all nice and fast, texts working etc. If I was the 'average user' I wouldn't know that it's not a UK one...
My question is, am I likely to hit any road blocks? As long as the radios all work I can't imagine there being any and the play store has all the apps I use available. I'm just wondering if I'm at any advantage/disadvantage?
Thanks
spears93 said:
Hi all,
I bought an unlocked note 9 from eBay which arrived today. I got it set up and went to begin installing a different firmware to be able to get the one UI update - only to find out it's a N960U1! I'm in the UK so was expecting/hoping for a N960F.
It's all working, calls work, I've pulled over 3GB of data today all nice and fast, texts working etc. If I was the 'average user' I wouldn't know that it's not a UK one...
My question is, am I likely to hit any road blocks? As long as the radios all work I can't imagine there being any and the play store has all the apps I use available. I'm just wondering if I'm at any advantage/disadvantage?
Thanks
Click to expand...
Click to collapse
I'm on the same boat (I mean, a similar situation because I'm not in the UK I'm in El Salvador). When I received my phone I started looking for the new UI, but I noticed that I had a very old android build version (I was in September security patch, I received my phone February 11) I started reading about and found out that N960U is the branded version of the note in the US. I wanted to update by Odin to one UI but I was afraid to get my phone carrier locked so after reading a lot more, I found that you can update using the right firmware for the phone (N960U) you don't lose carrier unlock and in my case after installing updates, I don't even have any bloatware.
Now, after this context history, I can tell you that the only thing that will affects is any "radio band enhance" or "carrier feature" and that's because you will not be able to install any UK carrier software to that version because N960U and N960F are different hardware, not just software.
Maybe there is another road block that is about updates, I'm on 9.0 but with January security patch, I have not received any new update. To be hones I'm not sure if there is a new one, so I need to wait to confirm that OTA updates are working for me, if not I will take the time to update by ODIN again haha so that's not something that will drive me crazy, and also related to this I think that N960U android versions are coming faster than I thought, some of my friends with N9600 are still stuck on 8.1
If you want to upgrade go to the following thread, there you will have enough information to update.
https://forum.xda-developers.com/galaxy-note-9/how-to/guide-upgrade-oreo-to-pie-one-ui-t3888711
Awesome, nice one dude
I used Odin on my previous S8+ to be able to install the one UI beta and that worked fine. Though it did come with a couple of apps that were a part of that carriers firmware (three UK)
I'm aware that the F uses an exynos processor whereas the U is Snapdragon and have seen a couple of guides already. Though they use AT&T firmware and, from what I've seen, have bloatware that would literally be useless to me.
I'll have a look at the guide you linked.
I'd like to have one UI again, but can happily live with the Samsung experience UI if I had to.
spears93 said:
Awesome, nice one dude
I used Odin on my previous S8+ to be able to install the one UI beta and that worked fine. Though it did come with a couple of apps that were a part of that carriers firmware (three UK)
I'm aware that the F uses an exynos processor whereas the U is Snapdragon and have seen a couple of guides already. Though they use AT&T firmware and, from what I've seen, have bloatware that would literally be useless to me.
I'll have a look at the guide you linked.
I'd like to have one UI again, but can happily live with the Samsung experience UI if I had to.
Click to expand...
Click to collapse
What's the software version that you currently running?
kevindevonwilliams said:
What's the software version that you currently running?
Click to expand...
Click to collapse
8.1 with Samsung experience 9.5
Build number ends ARL1
spears93 said:
8.1 with Samsung experience 9.5
Build number ends ARL1
Click to expand...
Click to collapse
Option1:
You can flash the Pie beta since you're running U1, there isn't an official release of Pie as yet.
Option2:
You can switch your device to the U firmware and flash the latest OTA however you would have to manually update each time because you won't be getting an update automatically.
kevindevonwilliams said:
Option1:
You can flash the Pie beta since you're running U1, there isn't an official release of Pie as yet.
Option2:
You can switch your device to the U firmware and flash the latest OTA however you would have to manually update each time because you won't be getting an update automatically.
Click to expand...
Click to collapse
How come the U firmware wouldn't get OTAs?
My S8+ was flashed to get the beta and that received OTA updates.
If I'm to go onto one UI I'd want it to get OTA updates still. If that means waiting for an official release then so be it
On a different note, I installed an app to get the FM radio working today. Can't do that with the UK exynos version ?
spears93 said:
How come the U firmware wouldn't get OTAs?
My S8+ was flashed to get the beta and that received OTA updates.
If I'm to go onto one UI I'd want it to get OTA updates still. If that means waiting for an official release then so be it
On a different note, I installed an app to get the FM radio working today. Can't do that with the UK exynos version
Click to expand...
Click to collapse
Because on the U most OTA comes from the carrier (ATT & VZW) while the rest comes from Samsung.
U1 all updates come from Samsung but U1 updates are months behind.
Advantage of running U firmware is you always get to be on the latest OTA as one is available.
kevindevonwilliams said:
Because on the U most OTA comes from the carrier (ATT & VZW) while the rest comes from Samsung.
U1 all updates come from Samsung but U1 updates are months behind.
Advantage of running U firmware is you always get to be on the latest OTA as one is available.
Click to expand...
Click to collapse
So correct me if I'm wrong but to simplify what you're saying:
The U gets the latest updates sooner but comes with carrier bloat
The U1 gets non bloated updates but Samsung doesn't release then until months later?
I'll leave it and wait if that's the case. I'd be more bothered about having bloat than One UI
spears93 said:
So correct me if I'm wrong but to simplify what you're saying:
The U gets the latest updates sooner but comes with carrier bloat
The U1 gets non bloated updates but Samsung doesn't release then until months later?
I'll leave it and wait if that's the case. I'd be more bothered about having bloat than One UI
Click to expand...
Click to collapse
Well yes the U comes with bloatware but the amount varies according to carrier, but since you're in the UK. Your CSC will read as XAA/XAA so therefore I doubt you would have any bloatware.
I know this because I myself had own a US device while using in the UK.
kevindevonwilliams said:
Well yes the U comes with bloatware but the amount varies according to carrier, but since you're in the UK. Your CSC will read as XAA/XAA so therefore I doubt you would have any bloatware.
I know this because I myself had own a US device while using in the UK.
Click to expand...
Click to collapse
Right, I'm with you, thanks.
My current carrier software version version is XAA/XAA and theres no bloat so I know what I'm hunting for now
Cheers for your help mate
spears93 said:
Right, I'm with you, thanks.
My current carrier software version version is XAA/XAA and theres no bloat so I know what I'm hunting for now
Cheers for your help mate
Click to expand...
Click to collapse
Right so even if you switch to U firmware it would still remain XAA/XAA because that would be the default CSC code for Unbranded for American model. F model is normally XEU or BTU
kevindevonwilliams said:
Right so even if you switch to U firmware it would still remain XAA/XAA because that would be the default CSC code for Unbranded for American model. F model is normally XEU or BTU
Click to expand...
Click to collapse
When I did the S8+ I had to go through a pretty big list to find the BTU firmware so assumed I'd have to do the same for the N9
I might give it a go if I get a chance this week
Seeing as you have the US variant of the Note 9. You may have issues receieving connecting to certain networks outside the US. As most US Networks use a different LTE band from the EU/UK
I bought a used galaxy s21 ultra from a local store that buys & sells and used phones. It's network unlocked with att firmware. It is using Android 11 and one is 3.1. Its latest security patch is Sept 1 2021 When I attempt to update, the phone, it tells me that it's up to date.
Is it normal for a recent flagship device to be over a year behind on security updates and coming now it's about to be 2 Android versions behing
What is the version of your s21 ultra...
SM-G998U
You can check here what the latest firmware is for the phone:
https://samfrew.com/model/SM-G998U/
Change CSC maybe?
Can you post the exact build?
Prob someone manually flashing the wrong firmware on it so no AT&T OTAs will work, but easily fixed.
If you post the version it should be obvious.
trucker253 said:
I bought a used galaxy s21 ultra from a local store that buys & sells and used phones. It's network unlocked with att firmware. It is using Android 11 and one is 3.1. Its latest security patch is Sept 1 2021 When I attempt to update, the phone, it tells me that it's up to date.
Is it normal for a recent flagship device to be over a year behind on security updates and coming now it's about to be 2 Android versions behing
Click to expand...
Click to collapse
There are ways to manually update it, using a PC
Electronic Punk said:
Can you post the exact build?
Prob someone manually flashing the wrong firmware on it so no AT&T OTAs will work, but easily fixed.
If you post the version it should be obvious.
Click to expand...
Click to collapse