Just got an update this morning, but it's still 8.1 and is merely the December security update. Baseband is N960USQS1ARL2 as shown below. I'm guessing this means the US rollout of Pie is still more than a couple weeks away.
Related
Bought a brand new UK simfree P10 yesterday expecting to see a few updates from when i switched it on, to my surprise I've had nothing it saying phones up to date yet it still stuck on March security patch and B120 firmware.
https://forum.xda-developers.com/p10/help/p10-vtrl09-question-t3735087
updated using firmware finder now on Jan security patch
I have similar issue, VTR-L29C636 running B171, but 172 is approved, yet no updates. Even routing via FF proxy doesn't show new updates.
So, i bought this phone and i was in the July security patch then it got updated to the october with an update around 1gb...since then i didn't receive any OTA of November and i Flashed from mi flash tool an older version on purpose to see if its gonna be the same...same thing happened October update but when searching for new updates got nothing. Then i flashed November rom from the xiaomi site 9.6.16 and still haven't got 9.6.17 that so many ppl are talking about that they got...
To summarise my phone didn't get any November OTA and i was stuck in October (9.6.15) now i flashed 9.6.16 manually and still no OTA to 9.6.17
Is that normal???
Currently running Baseband Version N960USQU1CSC1, Android Security Patch level: March 1, 2019.
I have never received an OTA update since buying my phone in Aug 2018. For the Android Pie update and all updates since, I have been performing them via ODIN.
Neither AT&T not Samsung have been able to troubleshoot this issue. Appreciate any help on how I can setup my phone to receive OTA updates.
Thanks!
wisconsindesi said:
Currently running Baseband Version N960USQU1CSC1, Android Security Patch level: March 1, 2019.
I have never received an OTA update since buying my phone in Aug 2018. For the Android Pie update and all updates since, I have been performing them via ODIN.
Neither AT&T not Samsung have been able to troubleshoot this issue. Appreciate any help on how I can setup my phone to receive OTA updates.
Thanks!
Click to expand...
Click to collapse
The new firmware is in another post. Just Odin and you'll be current.
I have unlocked on AT&T , and just got the April update this morning, all OTA. Never had to Odin the updates , but definitely not as quick as the carrier branded models. I have only added the APN names when I got the phone(preorder so August 2018) and that's the only setting I changed.
Didnt think flashing instead of waiting for OTA would cause any troubles, but Samsung is sneaky sometimes. Have you thought that maybe you flashed the incorrect files, maybe carrier vs unlocked? Also, factory wipe and reset ? I know the pie update did some screwy things for me and it seemed better after a wipe .
Sent from my Samsung SM-N960U1 using XDA Labs
960U1UES1CSD1 is what I am on now
Has anyone actually received the update to ATK1? I was on ATJ5 with the October update however I saw the ATJ1 in Frija. The phone was saying I was up to date so I am manually flashing it. I am just curious if my phone was going to get the update or not as I am running a SIM unlocked ATT device on the unlocked firmware.
I received the ATK1 update OTA last week. I'm on ATT with a factory unlocked phone.
mvmorr01 said:
I received the ATK1 update OTA last week. I'm on ATT with a factory unlocked phone.
Click to expand...
Click to collapse
ditto for me.
Recieved the update on the 24th. Same date as the previous month's update. Both times I had to manually check for updates before it showed up. On Mint with a factory unlocked.
I'm USA unlocked on T-Mobile and was tired of waiting for the update. They are always last to push it. So I used the guide that was posted on this forum on how to change your CSC to check for and download the update. Worked perfect. Had the new update installed in like 5 minutes.
It seems Google mistakenly pushed VZW firmware as the "latest" update, so it's a Google side problem that should be resolved with the December update.
If you're not using a Verizon branded device, it's not recommended that you install this firmware.
Thanks to @MishaalRahman for discovering this.