Related
http://www.theandroidsoul.com/andro...dule-samsung-htc-sony-motorola-manufacturers/
Google announced the Android 5.0 Lollipop a couple of days back and we’re already hearing news from various Android manufacturer partners for their Android 5.0 Lollipop update schedule. Major companies like HTC and Motorola announced their update plans right after a few hours of Google’s announcement, while Sony took a day to announce its update plans.
Just to be clear, the source article states that Samsung has NOT announced any plans to update to Lollipop, and the article goes on to speculate what those dates might be "based on past update cycles". So any of the dates are nothing more than pure guesses anyway. And the "date" given for the S4 Active would be a guess for the non-branded version supplied directly by Samsung. Anything that might or might not come for an AT&T version would come many months later, if at all. Just to be clear. Personally, while it would be fantastic to get Lollipop, I'm not holding my breath...
^_^
didn't get my kitkat update yet and you guys are talking about lolipop .... how sad am i !?
same here no update still on 4.2
I don't know about ota update, but people use official kitkat around 6 months. Install update via odin and job is done.
MiZoSpaDe said:
didn't get my kitkat update yet and you guys are talking about lolipop .... how sad am i !?
Click to expand...
Click to collapse
You're just gonna skip directly to lollipop. No trouble.
You can install the kitkat update from any country it will work I did it as I know that my country will be listed
How to upgrade
Yeah! Can you tell us how you upgrade? Cause I cant upgrade to KK yet, and Lolipop i almot here?...
You should download the firmware from sammobile and it will explain you how to do it
5.0.1 come
It came.. NEE
mahferer said:
It came.. NEE
Click to expand...
Click to collapse
Wait---you received "Lollipop"? If so, care to share some links?
Nevermind----It looks like a slim chance. I'll be sticking with my trusty Optimus pro for now.
http://forum.xda-developers.com/gal...-i9295-5-0-1-android-lollipop-update-t3044134
mahferer said:
It came.. NEE
Click to expand...
Click to collapse
Isn't that the Finland release for the international model, i9295 ?
mahferer said:
http://forum.xda-developers.com/gal...-i9295-5-0-1-android-lollipop-update-t3044134
Click to expand...
Click to collapse
Yeah and if you actually read that, that release is for the i9295, not the i537. Don't confuse people
Is here only for i537?
Don't confuse your own..
mahferer said:
Is here only for i537?
Don't confuse your own..
Click to expand...
Click to collapse
Lollipop has been available for the international model (i9295) for months, it's called Cyanogenmod 12. The only people in this forum unable to use lollipop are those with the U.S. model (i537). Along with the fact that the title of that thread you linked to has the actual model number in its title (and the firmware build number does too), I'm not entirely sure what rebuttal you just failed to articulate, but I'd wager it's inaccurate.
thisisapoorusernamechoice said:
Lollipop has been available for the international model (i9295) for months, it's called Cyanogenmod 12. The only people in this forum unable to use lollipop are those with the U.S. model (i537). Along with the fact that the title of that thread you linked to has the actual model number in its title (and the firmware build number does too), I'm not entirely sure what rebuttal you just failed to articulate, but I'd wager it's inaccurate.
Click to expand...
Click to collapse
Firstly, this thread never implied its about the us variant i537, so his rebuttal was very accurate.
Secondly, The official Lollipop release only came a couple of days ago for the i9295, which is clearly what the OP of the thread begun talking about. Many people in this forum were unable to use lollipop as not many people count a port of Cyanogenmod stable enough to use daily.
Hope that helps you understand this thread better =)
any danger from manual update?
Hi friends. Sure most of you knows about the official 5.0.1 update for S4active which released for nordic countries on sammobile.
I am sill on 4.2.2 in Saudi arabia. My question is : should i update manually to kitkat firstly befor i install lollipop? And is there any dangers for updating my phone to this European update?
Attached my phone info and the update info
GS4 Active to Lollipop OTA
delphimon said:
Just to be clear, the source article states that Samsung has NOT announced any plans to update to Lollipop, and the article goes on to speculate what those dates might be "based on past update cycles". So any of the dates are nothing more than pure guesses anyway. And the "date" given for the S4 Active would be a guess for the non-branded version supplied directly by Samsung. Anything that might or might not come for an AT&T version would come many months later, if at all. Just to be clear. Personally, while it would be fantastic to get Lollipop, I'm not holding my breath...
Click to expand...
Click to collapse
I have an unlocked AT&T GS4 Active that I'm currently using through MetroPCS. I still have an AT&T sim card. If I put the AT&T sim card back in the phone, would I have the ability to get the Android 5.0 update? I assume the answer is No as the AT&T sim is not provisioned, but would the sim allow me to get the update over the air? Do all carriers look at the make, model, build # and carrier of all devices to make sure the phone is compatible? I'm assuming if this doesn't work, rooting is the only way. Also, since I have service through MetroPCS, will they update to Lollipop once available or does my model number, SGH-i537, make them think I have AT&T ( and will not update software for the phone )?
Does having an unlocked phone prevent software updates specifically when the phone was made for one carrier only ( AT&T Active )?
Will MetroPCS automatically push software updates to all their customers or to just those that have an approved device from Metro?
David182 said:
I have an unlocked AT&T GS4 Active that I'm currently using through MetroPCS. I still have an AT&T sim card. If I put the AT&T sim card back in the phone, would I have the ability to get the Android 5.0 update? I assume the answer is No as the AT&T sim is not provisioned, but would the sim allow me to get the update over the air? Do all carriers look at the make, model, build # and carrier of all devices to make sure the phone is compatible? I'm assuming if this doesn't work, rooting is the only way. Also, since I have service through MetroPCS, will they update to Lollipop once available or does my model number, SGH-i537, make them think I have AT&T ( and will not update software for the phone )?
Does having an unlocked phone prevent software updates specifically when the phone was made for one carrier only ( AT&T Active )?
Will MetroPCS automatically push software updates to all their customers or to just those that have an approved device from Metro?
Click to expand...
Click to collapse
You need to have an active AT&T sim card to get the update automatically. MetroPCS nor any other carrier will never provide updates to an AT&T phone. This is similar to asking if Honda will upgrade the engine of your Ford truck, it's never going to happen. Your only option is to update the phone manually using the guides provided in this forum.
Devo7v said:
You need to have an active AT&T sim card to get the update automatically. MetroPCS nor any other carrier will never provide updates to an AT&T phone. This is similar to asking if Honda will upgrade the engine of your Ford truck, it's never going to happen. Your only option is to update the phone manually using the guides provided in this forum.
Click to expand...
Click to collapse
to
I've noticed that a couple of the carriers are rolling out different firmware versions. CSAA and CSAB for the Pie Updates. Anyone on XFinity that got the official OTA Pie update that can tell me if its CSAA or CSAB please? I don't want to miss future OTAs because my firmware isnt correct. I'm running the update.zip CSAA universal leaked update. If I need to be on CSAB I gotta get to flashing back to Oreo and taking the OTA.
Sent from my SM-N960U using Tapatalk
sinisin said:
I've noticed that a couple of the carriers are rolling out different firmware versions. CSAA and CSAB for the Pie Updates. Anyone on XFinity that got the official OTA Pie update that can tell me if its CSAA or CSAB please? I don't want to miss future OTAs because my firmware isnt correct. I'm running the update.zip CSAA universal leaked update. If I need to be on CSAB I gotta get to flashing back to Oreo and taking the OTA.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Who pushed CSAB? The only carriers to release Pie in the US pushed CSAA.
Mr. Orange 645 said:
Who pushed CSAB? The only carriers to release Pie in the US pushed CSAA.
Click to expand...
Click to collapse
To be honest I'm not exactly sure where I saw it. It appeared to be TMO or Verizon but it wasn't really clear(I was skimming). Pretty sure it was from one of the other Android specific forums, don't wanna name names here. The article said they were adding a feature other carriers were not yet. The SS they had, had CSAB for Firmware Version. If it was Verizon I may need the same firmware as XFinity Phones are always the same firmware as Verizon.
In my catching up on Android stuff today I see about the one firmware across all the carriers tho. That should be awesome. All the dev's can work on it all together instead of being locked to working on their carriers version. Should make for good ROMs and amazing themes. And make for much faster updates from Samsung. Hopefully Treble gets them on track.
If I find that darn article again I'll send you the link but its MIA. I cant find it anywhere but I know I saw it. It was in my Google Feed which has as many Android news sources as I can pack in to it.
Sent from my SM-N960U using Tapatalk
sinisin said:
To be honest I'm not exactly sure where I saw it. It appeared to be TMO or Verizon but it wasn't really clear(I was skimming). Pretty sure it was from one of the other Android specific forums, don't wanna name names here. The article said they were adding a feature other carriers were not yet. The SS they had, had CSAB for Firmware Version. If it was Verizon I may need the same firmware as XFinity Phones are always the same firmware as Verizon.
In my catching up on Android stuff today I see about the one firmware across all the carriers tho. That should be awesome. All the dev's can work on it all together instead of being locked to working on their carriers version. Should make for good ROMs and amazing themes. And make for much faster updates from Samsung. Hopefully Treble gets them on track.
If I find that darn article again I'll send you the link but its MIA. I cant find it anywhere but I know I saw it. It was in my Google Feed which has as many Android news sources as I can pack in to it.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
You sure it wasn't referring to the S9/+? Because all the carriers released CSAB for those devices. I would be shocked if T-Mo and Verizon released a different build than ATT and Sprint for the Note 9. It defeats the purpose of the carrier switching firmware.
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
Hello everyone
Just curious when we gonna get Android 10 oneui 2.0 update.
I got Verizon Note 9 SM-N960U.
All The Exynos Models international and korean already got updated and their firmware is already available to download on sammobiles.com.
Any ideas when for snapdragon models ?
Thanks and i hope y'all having a good day
No one knows dude. U just have to wait..
Next month. Confirmed by Samsung.
Well that roadmap that came out last year did say we were supposed to all have it January 2020. So who knows.
I am just hoping we get this month in January.
I heard lot of goodies about android 10+oneui 2 and can't wait to try it out.
Trex888 said:
I am just hoping we get this month in January.
I heard lot of goodies about android 10+oneui 2 and can't wait to try it out.
Click to expand...
Click to collapse
you can flash U1CSJ1 and update to the unlocked beta version.i have the same type of phone and been running A10 since the first day sprint released it.
They updated that list and made it February. Every other phone on that list has gotten the update on time, as it was listed. I'm not saying every carrier will release it, but I think the OTA file will leak and we can all sideload it just like Android 9
The OTA Images download page lists two images.
One normal one, and one "KDDI only".
What exactly is KDDI? My take from Googling it is that it's some Provider.
The device I got came with said "KDDI only" Image on it (Build Number ends with ...021.A1), and VoLTE and VoWiFi aren't working, and I somehow suspect it might be the wrong image.
Makes me wonder if I can just sideload the non-KDDI OTA image to fix it? Anyone happens to have any insight there?
Edit: Just sideloading the non-KDDI OTA image does not work. Downgrade-Prevention kicks in.
Same here in the UK. My phone is running (RD1A.200810.021.A1, Oct 2020, KDDI only) but surely since i brought direct from Google, it should be (RD1A.200810.020, Oct 2020)?
I've posted on the Google product forums, to see if anyone can shed any light on the matter.
Dilbert83 said:
Same here in the UK. My phone is running (RD1A.200810.021.A1, Oct 2020, KDDI only) but surely since i brought direct from Google, it should be (RD1A.200810.020, Oct 2020)?
I've posted on the Google product forums, to see if anyone can shed any light on the matter.
Click to expand...
Click to collapse
https://gadgets.ndtv.com/mobiles/ne...ges-published-android-developers-site-2311265
KDDI network subscribers in Japan
Hey there from Germany. I pre-ordered mine direct from Google and it was delivered from UK to Germany.
Mine also has the KDDI firmware preinstalled
Same here in france, tried to install magisk with the kddi boot img and it didnt worked
I also have the 021.A1 ROM on my Pixel in Germany, I rooted with the boot image from the international 020 build however - that worked fine, and I also pass SafetyNet on basic attestation with the HideProps module. @SOSODU13016 what issues did you have exactly? Did the root not get applied when booting up? Or did your device simply not boot?
The root did not applied ?, but booting was fine
SOSODU13016 said:
The root did not applied , but booting was fine
Click to expand...
Click to collapse
Try to patch the boot image yourself in Magisk Manager, and flash it another time. It also took two tries for me for some reason until Magisk finally was installed. I've also read from others that they had to reboot multiple times.
https://forum.xda-developers.com/newreply.php?do=newreply&p=83752561
Click to expand...
Click to collapse
I'm confused, how do i know if i choose the wrong boot.img ? will i enter in a bootloop ? i'll try to patch myself with the kddi version since i'm on the 021.A1
EDIT : Ok i used my own boot.img patched with magisk based on the 021.A1 boot.img from google and it worked. Thanks everyone !
My Pixel 5 sold by Amazon UK. Came with RD1A.200810.021.A1
The box says Imported into UK & EU by Google Ireland. So doesn't look like a Japanese version.
Sent from my Pixel 5 using Tapatalk
thesebastian said:
My Pixel 5 sold by Amazon UK. Came with RD1A.200810.021.A1
The box says Imported into UK & EU by Google Ireland. So doesn't look like a Japanese version.
Click to expand...
Click to collapse
Same here but bought from Carphone Warehouse.
I'm in France, bought it from the google store, I've a kddi image too. So I don't think it's related to an oper
I've been using the Pixel 5 since Monday, but this morning I should restart my phone for a system update.
It was on version RD1A.200810.020, Oct 2020
and now RD1A.200810.021.A1, Oct 2020, KDDI only
I live in Germany and the phone also comes from Ireland.
The update process seems to be bugged.
Hi,
I've actually sent an email to the Google support regarding this topic, enquiring if it is normal for a phone purchased on the French Google Store to have a Japanese carrier variant pre-installed.
For now the request has gone through 3 different departments at Google as none of them feel sufficiently qualified to answer the question.
I'll let you know if I get any real feedback.
Hi,
same here. Bought on the german Google Store and got my Pixel 5 from Ireland shipping with RD1A.200810.021.A1
Would be interesting to see if it is possible to flash the "global" november factory image without getting a downgrade warning.
Also it would be interesting to know what the actual differences are between the global and the kddi versions.
klopsknoedel said:
Hi,
same here. Bought on the german Google Store and got my Pixel 5 from Ireland shipping with RD1A.200810.021.A1
Would be interesting to see if it is possible to flash the "global" november factory image without getting a downgrade warning.
Also it would be interesting to know what the actual differences are between the global and the kddi versions.
Click to expand...
Click to collapse
Hey I managed to install the "RD1A.200810.020" version using the android flash tool (https://www.youtube.com/watch?v=1Aadgx7fDUQ)
cheptii said:
Hey I managed to install the "RD1A.200810.020" version using the android flash tool (
)
Click to expand...
Click to collapse
Interesting. Did you notice any differences between both versions?
I'm still waiting for feedback from Google that I will likely never get. I do hesitate though to "go global" as :
1) most (if not all) European pixel 5 have been delivered with KDDI version here in Europe. Must be a reason to this.
2) I have no idea about the changes between both
3) I actually have no issues with KDDI version. I even get WiFi calling here in France from French network operator.
Will keep my eyes open.
LuMe96 said:
Interesting. Did you notice any differences between both versions?
I'm still waiting for feedback from Google that I will likely never get. I do hesitate though to "go global" as :
1) most (if not all) European pixel 5 have been delivered with KDDI version here in Europe. Must be a reason to this.
2) I have no idea about the changes between both
3) I actually have no issues with KDDI version. I even get WiFi calling here in France from French network operator.
Will keep my eyes open.
Click to expand...
Click to collapse
I didn't notice any difference. But I am sure that the global versions will be updated before the carrier specific versions.
lol, that's kinda strange.
You guys bought the Pixel 5 from EU Google store and got Japanese carrier-based firmware while I bought the Pixel 5 from Google Store Japan and got normal variant firmware.
Google changed the description with the November-Update today and it seems that they've mixed it up previously.
So the current regional versions are:
RD1A.200810.020, Oct 2020, AU & JP carriers
RD1A.200810.020.A1, Oct 2020, KDDI only
RD1A.200810.021.A1, Oct 2020, EU carriers
RD1A.200810.021.B3, Oct 2020, Verizon
RD1A.200810.022.A4, Oct 2020 (global?)
RD1A.201105.003, Nov 2020, JP carriers
RD1A.201105.003.A1, Nov 2020, AU carriers
RD1A.201105.003.B1, Nov 2020, EU carriers
RD1A.201105.003.C1, Nov 2020 (global?)
Anyway. As said, I bought my Pixel 5 from the german google store and not from a german carriers store. So I expect to be on "RD1A.201105.003.C1" instead my phone updated to "RD1A.201105.003.B1".
Still confusing but at least the "KDDI only" - discussion is solved. I guess. ?