I was wondering what you guys use for getting notified when a firmware update arrives? As I'm rooted, I won't receive official OTA notifications. I can check Frija manually or any other firmware website, but is there a neat app that does the trick on the smartphone itself? Something like Oxygen Updater on OnePlus devices?
Ive never seen an app for this. As you alluded to yourself, the issue here is for it to notify you on your phone. It is very simple to write a script on a computer to look for a version change on the website and notify you. You can run most desktop scripts in Termux but there's no way to schedule it so its still a manual process. You need an app that can scrape websites for version info but I have zero experience in that area to even know where to start.
I have now found multiple ways of checking for an update in case anyone is wondering:
CheckFirm: https://play.google.com/store/apps/details?id=com.illusion.checkfirm
You can try to scan for a new firmware. It uses other users to find a new firmware but according to the dev, it might be able to scan automatically in the future (though no ETA)
Use Samsung's own version.xml: https://fota-cloud-dn.ospserver.net/firmware/DBT/SM-G998B/version.xml
This is an example (replace DBT with the CSC code and SM-G998B with your model version. It will list all firmwares with the newest firmware number at the top.
Use Samsung's changelog: https://doc.samsungmobile.com/sm-g998b/dbt/doc.html
This is an example (replace DBT with the CSC code and SM-G998B with your model version.
There are plenty of services online that check for any changes on a public website. Most of them are restricted to a certain number of websites or only check every 24 hours. But checking those two official websites from Samsung would make it possible to get a firmware update notification.
Since you can't update the firmware on the device itself while being rooted, a notification is enough for me. I still have to use ODIN on a Windows PC anyway
Thanks was looking for this
Related
I recently purchased a Galaxy Note (Unlocked) and am loving the device. I was reading online that there was a newer open european firmware (LA3) but was perplexed as my phone was saying there are no upgrades for it. I installed Kies (the UK version) and it updated it's self to 2.2 yet it still does not show any newer firmware than what is on my phone (KKA).
Is there a way to force Kies to let me update? or am I missing a step (I never did create a samsung account).
Thank you in advance...
Hi there,
I also recently purchased a Note, and have been spending FAAAR tooo much time lurking on this forum trying to work out whats what with rooting/roming and all things GNote.
Fairly new to all this android malarky and tbh i'm kinda just responding to your question as a way to clarify what, i have, thus far, gleaned from by lurksome xda ways! And as an attempt to stop lurking so much and try and give back some of the understanding xda has given me.
Your question is something I was also rather confused by, but from what I understand - It seems that Samsung rolls out OTA and Kies updates to phones with different CSC codes at different times.
I think it is only the German (DBT) phone which has had the latest LB1 update. I know that my XEU phone is also still on KKA, with no ota or kies updates available.
From what I understand, the way one gets the updates without rooting is through flashing them with a Windows app called PC Odin with the phone in download mode.
Or via rooting your KKA rom
http://forum.xda-developers.com/showthread.php?t=1329360
and then flashing the updated firmware with either Mobile Odin or Clockwork Mod.
In all cases I believe you must download the firmware from either the sammobile site or http://forum.xda-developers.com/showthread.php?t=1424997
If any (or all!) of that is totally wrong - please someone with greater experience wade in and put me straight, but I just thought that seeing as no-one else had responded - i'd try and make something of all the hrs i've spent lurking on here since i got this phone
Anyhow I'm sure if you just follow the links i've posted to the brilliant work of Dr Ketan - you won't go far wrong
Personally, I've not actually put any of this to the test yet - wanna make sure I really do know my arse from my elbow or in this case - my dalvik from my build.prop before I go messing with a £500 phone....
knowayback said:
Hi there,
I also recently purchased a Note, and have been spending FAAAR tooo much time lurking on this forum trying to work out whats what with rooting/roming and all things GNote.
Fairly new to all this android malarky and tbh i'm kinda just responding to your question as a way to clarify what, i have, thus far, gleaned from by lurksome xda ways! And as an attempt to stop lurking so much and try and give back some of the understanding xda has given me.
Your question is something I was also rather confused by, but from what I understand - It seems that Samsung rolls out OTA and Kies updates to phones with different CSC codes at different times.
I think it is only the German (DBT) phone which has had the latest LB1 update. I know that my XEU phone is also still on KKA, with no ota or kies updates available.
From what I understand, the way one gets the updates without rooting is through flashing them with a Windows app called PC Odin with the phone in download mode.
Or via rooting your KKA rom
http://forum.xda-developers.com/showthread.php?t=1329360
and then flashing the updated firmware with either Mobile Odin or Clockwork Mod.
In all cases I believe you must download the firmware from either the sammobile site or http://forum.xda-developers.com/showthread.php?t=1424997
If any (or all!) of that is totally wrong - please someone with greater experience wade in and put me straight, but I just thought that seeing as no-one else had responded - i'd try and make something of all the hrs i've spent lurking on here since i got this phone
Anyhow I'm sure if you just follow the links i've posted to the brilliant work of Dr Ketan - you won't go far wrong
Personally, I've not actually put any of this to the test yet - wanna make sure I really do know my arse from my elbow or in this case - my dalvik from my build.prop before I go messing with a £500 phone....
Click to expand...
Click to collapse
I appreciate the help to answer your question you are in part correct (from what I can gather). Samsung does issue updates based on CSC codes and there is nothing for the UK CSC code. However they also release what is called open updates. Meaning any carrier in a given country can use a open update for that country. Beyond that they release what is called open European updates that any unlocked phone in Europe can use.
My question is the latest open European update is LXA or LLA or something like that which is farther along than the KK5 I am on. Since it is open European I should be able to update to it I would think. There could be something to the fact that the UK is considered part of the EU so it might not fall under even an open European release and if that is the case than so be it.
I am just trying to find out why my unlocked international version of the note can not seem to update to the latest open European update
Ok, so from the sounds of it - i think your definitely better informed than me on Samsung update protocol
Haven't heard any of that before. I was under the impression that the XEU code was the unlocked open euro code....
Anyway, just thought i'd let u know that i took the plunge today - deciding that I trusted XDA more than Samsung to update my phone
Rooted my stock KKA rom using dr ketans posts as my guide, then flashed the stock LB1 firmware and have since flashed Franco's kernel.....all seems well so far
Although one thing i did notice is that my Antutu score was significantly lower after flashing Lb1, but before flashing Franco's kernel (haven't tested since)....
Anyway good luck waiting for an official update - in my limited experience - I wouldn't hold your breath waiting for OEM's to issue OTA updates...
Valdeck said:
I am just trying to find out why my unlocked international version of the note can not seem to update to the latest open European update
Click to expand...
Click to collapse
This is cool. But how to find whether my phone is locked or not?
And what about if we try to involve the Samsung support on this question? I'm also stuck with kk5 and i'm also in Europe.
Spo0f said:
This is cool. But how to find whether my phone is locked or not?
And what about if we try to involve the Samsung support on this question? I'm also stuck with kk5 and i'm also in Europe.
Click to expand...
Click to collapse
If you want to know what region your phone is from plug it into the computer after you have installed samsung kies. Once you do if you look at the screen for your phone you will see three sets of letters and numbers. The last one in the string will have your CSC once you get that do a google for where it is from.
If you are on kk5 like me then you probably have a UK code.
An phone is unlocked by default when you import it from Europe as they use a different model for cell carriers than we do in the states.
The simple way to get the latest updates is....change your CSC with *#272*imei# in the dialer pad to the lastest update ( csc)! You don't need root or odin or mobile odin. Just change your country code. This will wipe your phone...but after restart you will get a promt to update your software as soo. As wou are connected to a wifi. There are many post about it...the csc change is described in sgs2 foruns and all over the net. About the country code, please visit sammobile.com and in firmware section you will find detailed info about those codes.
P.S. My note was originaly in XEH ( open Hungary), I'm from Romania so I changed my CSC to Open Germay (DBT-debitel) and after restart i got 2 consecutive updates.
Hope to help, sorry for my bad english
Sent from my GT-N7000 using xda premium
The easiest way to get updates is via XDA. Download PC Odin, and choose whatever Rom you fancy from the first sticky thread in Note development.
Hello,
in my company we are developing an android app. The lowest android version this app supports is android 4.3.
The company bought several testing devices including a AT&T branded Samsung Galaxy S4 Active. With Android 4.2.2 (Buid Number: JDQ39.I9295UCUAMF3)
I tried it for a while now, but I can't get the OTA Update to work. It says "Software update interrupted. Try again in 24 hours".
I can bypass the 24h lock by changing the date of the phone. But even after ~30 tries the phone is not updating.
There is no SIM Card in the phone. Is a AT&T SIM Card needed to update the device? I am not able to get one, because I am located in Germany.
Can I update the phone manually with Kies or something?
I don't have admin right on my machine so I need to know what to do, before I contact the admin to install a required software.
Could a blocked port be an issue? I do have access to the internet, but if Samsung (or AT&T) uses some non standard port, my company could be blocking it.
(Root is not an option.)
Kind regards
Cliff
Cliff666 said:
Hello,
in my company we are developing an android app. The lowest android version this app supports is android 4.3.
The company bought several testing devices including a AT&T branded Samsung Galaxy S4 Active. With Android 4.2.2 (Buid Number: JDQ39.I9295UCUAMF3)
I tried it for a while now, but I can't get the OTA Update to work. It says "Software update interrupted. Try again in 24 hours".
I can bypass the 24h lock by changing the date of the phone. But even after ~30 tries the phone is not updating.
There is no SIM Card in the phone. Is a AT&T SIM Card needed to update the device? I am not able to get one, because I am located in Germany.
Can I update the phone manually with Kies or something?
I don't have admin right on my machine so I need to know what to do, before I contact the admin to install a required software.
Could a blocked port be an issue? I do have access to the internet, but if Samsung (or AT&T) uses some non standard port, my company could be blocking it.
(Root is not an option.)
Kind regards
Cliff
Click to expand...
Click to collapse
Hi Cliff. I can't say for sure, but my guess is you can't access the OTA because you're not in the right region (someone correct me if I'm wrong). As far as I know, you shouldn't need a SIM to update, again could be wrong. More importantly, there are other ways to update. You could probably try Kies, but I wouldn't recommend it, it seems like users always have issues with Kies. I would strongly recommend you try updating the phone with Odin, a tool by Samsung that let's you change around your phone's firmware (among other things) when the phone is in download mode.
There is an exhaustive guide linked to here that thoroughly explains how to go from any version of android (official, for this phone) to any other version. In simpler terms, that link shows you how to manually update, which is what I think you're looking for. Also the files you'll need to download are located here. Hope I've helped, and good luck updating! :good:
Oh, just re-read your caveats: you almost certainly don't need a SIM for Odin to work, and you definitely don't need root either.
thisisapoorusernamechoice said:
Hi Cliff. I can't say for sure, but my guess is you can't access the OTA because you're not in the right region (someone correct me if I'm wrong). As far as I know, you shouldn't need a SIM to update, again could be wrong. More importantly, there are other ways to update. You could probably try Kies, but I wouldn't recommend it, it seems like users always have issues with Kies. I would strongly recommend you try updating the phone with Odin, a tool by Samsung that let's you change around your phone's firmware (among other things) when the phone is in download mode.
There is an exhaustive guide linked to here that thoroughly explains how to go from any version of android (official, for this phone) to any other version. In simpler terms, that link shows you how to manually update, which is what I think you're looking for. Also the files you'll need to download are located here. Hope I've helped, and good luck updating! :good:
Oh, just re-read your caveats: you almost certainly don't need a SIM for Odin to work, and you definitely don't need root either.
Click to expand...
Click to collapse
Thank you for your answer. Yes, maybe AT&T does region lock the update -.-
I've used Odin on my old Galaxy S2 some years ago.
I'll have a look into it and decide if this is the way to go.
Odin will do it as long as there are full install files for you to use.
Cliff666 said:
Thank you for your answer. Yes, maybe AT&T does region lock the update -.-
I've used Odin on my old Galaxy S2 some years ago.
I'll have a look into it and decide if this is the way to go.
Click to expand...
Click to collapse
You need an AT&T SIM card in the phone in order to install AT&T OTA updates. You can't use Kies to update because AT&T won't let Samsung post AT&T firmware on Kies. So your only option is to use Odin and the guide posted above.
I was cleaning out my phone for resale or donation and noticed that AT&T's site now lists a newer firmware of I537UCSCOC8. Has anyone not actively using service from said provider actually been able to receive this update or found the firmware available? I don't seem to be able to get it through either the phone's update check or Kies (I presume they are both getting it from Samsung, which doesn't list this update).
It's a baseband update. Not sure what for, but, cool nonetheless.
Hey, just an idea. Could we trick our phones into thinking that there's an update on the OTA server?
We know that you can check for updates in the "download updates manually" settings page (screenshot 1).
But, is it possible to essentially 'redirect' my phones request to Samsung's server and point it do my own server by tinkering with my wifi settings on a router?
That way, I can download and place any supported, official Samsung firmware faster on my own server and let phone download and install it. Remember, OEM firmware will be digitally signed and will pass the integrity checks so it shouldn't be a problem for the phone to accept and flash it.
16010487 said:
Hey, just an idea. Could we trick our phones into thinking that there's an update on the OTA server?
We know that you can check for updates in the "download updates manually" settings page (screenshot 1).
But, is it possible to essentially 'redirect' my phones request to Samsung's server and point it do my own server by tinkering with my wifi settings on a router?
That way, I can download and place any supported, official Samsung firmware faster on my own server and let phone download and install it. Remember, OEM firmware will be digitally signed and will pass the integrity checks so it shouldn't be a problem for the phone to accept and flash it.
Click to expand...
Click to collapse
yeah its called downloading the firmware manually and applying it.
u can use samfirm tool 0.3.6 to download the firmware on your pc
and Odin 3.13.1 to flash it on the phone.
Thanks bobber10113, will this trigger Knox? My region firmware isn't listed on Sammobile. Could I flash another N960F firmware from a different region?
What is your csc
Sent from my SM-N960F using Tapatalk
16010487 said:
Thanks bobber10113, will this trigger Knox? My region firmware isn't listed on Sammobile. Could I flash another N960F firmware from a different region?
Click to expand...
Click to collapse
sammobile has all of them. so does updato.com
but anyways go to system about phone /software
find your csc 3 letter csc code as previously stated and feed that to samfirm tool.
so enter phone model in the app then under, the 3 letter code
bober10113 said:
yeah its called downloading the firmware manually and applying it.
u can use samfirm tool 0.3.6 to download the firmware on your pc
and Odin 3.13.1 to flash it on the phone.
Click to expand...
Click to collapse
or samsung efota advanced license
bober10113 said:
yeah its called downloading the firmware manually and applying it.
u can use samfirm tool 0.3.6 to download the firmware on your pc
and Odin 3.13.1 to flash it on the phone.
Click to expand...
Click to collapse
Actually, the question is very much on-spot. For one, Odin is not very useful for a mac os system. Second, the person applying the update doesn't or should need to have the technical knowledge required to run Odin. Sometimes stuff occurs like a defective USB line on a device, making it impossible to establish a wired connection to a computer. Thus, a still workable wireless device becomes a burden for unnecessary repair, especially if it's a cheaper device. Some of us need to actually have and run our own effective equivalent of MS WSUS for phones, Samsung being the most popular after Apple.
In light of that, the original question stands: can we (and how) set up a local Galaxy update server and populate it with images?
I've got an unrooted xz1c that came with some sort of non-US stock firmware - which I know, because the fingerprint reader works. It's been nagging me to update it to Pie since I bought it, and I'm thinking I'd like to do it via the "official" (OTA) route, since it claims to be able to do it in-place, without having to reinstall apps, restore data, etc. What I want to avoid, though, is ending up with a US update, losing my fingerprint reader, and having to jump through hoops to get it back.
The build number in About Phone says 47.1.A.12.270. Is there some way of determining the current region, and confirming what region the update plans to install (without starting the update) - and/or forcing the region to match what I currently have? My google accounts, phone #, etc. are all US-based, if that makes any difference in terms of the update deciding what region is appropriate.
I was looking at a guide for installing specific region firmware via xperifirm/newflasher, but it indicated that the result would be a wiped phone, and I don't have time to deal with re-configuring everything from scratch right now.
Firmware customization does not change by applying OTA update. It will install the update of the same region that is already installed.
meeotch1 said:
I don't have time to deal with re-configuring everything from scratch right now.
Click to expand...
Click to collapse
In the past the OTA updates have famously locked thier owners out of thier phones by not regonising the unlock code that has been set, so make sure you disable it before you start.
Also, updating from 8 to 9 leaves some apps glitchy and there have been several reports of phone problems that can only be resolved by a full factory reset.
If you want the best experiance from your phone, wiping it would be the best option when upgrading.
Use Xperia transfer to back up apps/call history/contacts/text history. Then restore once you've wiped your phone.
@meeotch1 If you are happy with Oreo and without the latest security patches and updates, just let the phone OTA update it to the final Oreo version 47.1.A.16.20 and leave it there.
You can force close the Software update app from app settings to make it stop nagging about the update. And with adb you can even disable it permanently (and enable later if you wish to go for Pie).
Thanks for the advice. Good to know that the nag is disableable. So I take it that OTA upgrades *within* major versions (so Oreo 47.1.A.12.270 to 47.1.A.16.20) do not suffer the glitches mentioned by the first reply above?
Also, when I eventually go Pie, what's the least painful / most reliable restore method after wiping the phone? Is the built-in Xperia backup/restore available in Settings good enough? I'd prefer not to upload all my data to Google, unless there's some guarantee that it's encrypted. Don't need the NSA digging through my messages to radical terrorists and international drug lords.
To find out the customization, go to the service menu and select "Software Info".
You'll see an entry named "Customization Version" with a number like "1310-4371_R6C".
You can then look in XperiFirm at the column named "CDA".
On the example I gave, "1310-4371" corresponds in XperiFirm to "Customized US".
You can also look further down in the software info at "Current Modem Config" where the format will be something like:
/system/etc/customization/modem/amss_fsg_lilac_tmobile_us_ims_tar.mbn"
That tells me that my SIM card matched a mobile operator that is recognized as having a valid modem configuration file for my customization's region and, as such, loaded the correct modem file for that operator.
It also shows that I'm using T-Mobile US as my operator (tmobile_us) and I have some kind of VoLTE available (ims).