Please can someone clarify some things regarding over the air updates, e.g. for Froyo/2.2:
1. If one carrier pushes the update before another, can the update be shared with others and applied to any handset/ network, without root?
2. What happens with people who have bought unbranded/ unlocked devices? Should they get OTA from whatever network they are now on?
nb8k said:
Please can someone clarify some things regarding over the air updates, e.g. for Froyo/2.2:
1. If one carrier pushes the update before another, can the update be shared with others and applied to any handset/ network, without root?
2. What happens with people who have bought unbranded/ unlocked devices? Should they get OTA from whatever network they are now on?
Click to expand...
Click to collapse
First off bit early innit!! lol.......
Secondly as its android i should imagine it will be like any other OTA, with all normal rules applying.
1), If the carrier pushes the OTA, it proberly would not be a good idear to share, as some are custom boot logos etc..
2), I expect that will be the case, or it will simple be a download from the HTC site
regards,
Rich.
Related
Believe it or not after searching the web I haven't found a concrete answer on the subject, so I have two questions regarding OTA updates: 1) Can t-mobile flash an OTA on a non-stock android rom? 2) If so, what ways can I prevent it? After doing this much work on my phone, it would really suck if I lost root... Thanks
petraman said:
Believe it or not after searching the web I haven't found a concrete answer on the subject, so I have two questions regarding OTA updates: 1) Can t-mobile flash an OTA on a non-stock android rom? 2) If so, what ways can I prevent it? After doing this much work on my phone, it would really suck if I lost root... Thanks
Click to expand...
Click to collapse
No.. T-Mobile MUST ALWAYS ask for your permission usual in a message that will pop-up on your screen asking you to flash to newest.. ROM/RADIO sometimes doing so will break your ROOT and S-OFF until someone fixes.. please keep in mind.. when you choose to flash if you do..
T-Mobile is a company they SOLD you a Third-Party Product (HTC SLIDE) Renamed HTC Espresso because it uses T-Mobiles SENSE or Espresso Drivers.
T-Mobile is your Service Provider.. They may only ASK you to flash a new ROM to your phone but they have no right as the phone now belongs to you.
so no worries T-Mobile will not flash a OTA rom to your phone to break your root
So I tried updating while rooted, and found that that couldnt be done.
So I unrooted, and now when I check for updates, it says everything is up to date.
I have had this thing since launch, so I know theres a few updates to download.
If anyone can help that would be awesome.
I also did clear cache
OTAs
Sawdizzle said:
So I tried updating while rooted, and found that that couldnt be done.
So I unrooted, and now when I check for updates, it says everything is up to date.
I have had this thing since launch, so I know theres a few updates to download.
If anyone can help that would be awesome.
I also did clear cache
Click to expand...
Click to collapse
I'm rather new to Android and rooting, but I've been rooted on my SGS3 since the beginning of July, so I've experienced several OTA notifications. I know you cannot apply an OTA when rooted, generally, but that most Developers will actually update their custom ROMs when a new OTA is pushed. That has been my experience thus far, and how I've "kept" my phone up-to-date. In the change logs you can usually identify which OTA their ROM is based on, and make your decision from that information. Also, I believe most OTAs are carrier-based and not necessarily intended to update the OS or UI, so some of them may not be necessary. The important thing is the baseband (modem) version, as this can directly impact your reception and data speed. There is an excellent tool intended strictly for flashing a new modem, developed by clark44. The link is here: http://forum.xda-developers.com/showthread.php?t=1816530
I would suggest starting at the top of the list, running that modem for at least 2-3 days, then flashing the next one and repeating the process - until you find the one that works for your phone, in your area, based on the places you visit the most frequently.
I hope this helps.
Dear XDA developers.
I'm not an expert in this and i need someone to help or guide me through please to update my Note 10 + AT&T (N975USQU1ASGO) to Andriod 10. the last Security patch i got is July 2019. I tried:
1- Update the software... nothing works
2- Use Smart switch update, it does not provide any updates, always says I'm up to date.
3- Talked to AT&T customer service, they don't know anything. Same with Samsung guys.
It's noted that I unlocked the Phone to work on my T-mobile sim card. Is this a reason why I'm not getting any updates?
Any help is appreciated.
Thanks,
Mido
mazarsc1 said:
Dear XDA developers.
I'm not an expert in this and i need someone to help or guide me through please to update my Note 10 + AT&T (N975USQU1ASGO) to Andriod 10. the last Security patch i got is July 2019. I tried:
1- Update the software... nothing works
2- Use Smart switch update, it does not provide any updates, always says I'm up to date.
3- Talked to AT&T customer service, they don't know anything. Same with Samsung guys.
It's noted that I unlocked the Phone to work on my T-mobile sim card. Is this a reason why I'm not getting any updates?
Any help is appreciated.
Thanks,
Mido
Click to expand...
Click to collapse
Could be that you need an active AT&T SIM Card installed before you can receive the updates.
Some say this is no longer necessary with AT&T devices, but, if you know of someone who can lend you their AT&T SIM Card, at least you can rule it out one way or the other.
Odin... Don't wait for ATT to give updates. If it's unlocked just bypass them... Unless you need wifi calling voLTE...
All you need is samfirm or the other one, the current CSC that has the updated Android os, and Odin
No root required.
Use the home_csc to keep all user data. I'm willing to help if needed
GDHAMTON7 said:
Odin... Don't wait for ATT to give updates. If it's unlocked just bypass them... Unless you need wifi calling voLTE...
All you need is samfirm or the other one, the current CSC that has the updated Android os, and Odin
No root required.
Use the home_csc to keep all user data. I'm willing to help if needed
Click to expand...
Click to collapse
Yes please, I'd be glad if you can help me out. I don't need the wifi calling.
KOLIOSIS said:
Could be that you need an active AT&T SIM Card installed before you can receive the updates.
Some say this is no longer necessary with AT&T devices, but, if you know of someone who can lend you their AT&T SIM Card, at least you can rule it out one way or the other.
Click to expand...
Click to collapse
Thank you for your advice. you mean if i just put an At&T active sim then it should get the updates somehow?
mazarsc1 said:
Thank you for your advice. you mean if i just put an At&T active sim then it should get the updates somehow?
Click to expand...
Click to collapse
As long as it's active, yes.
Again, I'd borrow one from someone, if you can.
Its been a couple years since I last had an unlocked AT&T phone, I bit the bullet and bought a prepaid AT&T Card (with phone/data) for this very reason & was able to immediately download any pending updates.
No guarantees that this will work, as some state that this isn't necessary any more.
IDK if you bought the phone new direct from AT&T, but, if you got it anywhere else, someone may have altered the original firmware/software, & perhaps that, if it's the case, could be the culprit.
My 1st stop would be calling AT&T Tech support, that's where I found out about needing an AT&T SIM Card for d/l updates. Again, this was a couple/few years ago, but, that would be my first move.
bro pudiste solucionarlo, tengo el mismo problema
Translation: Bro you could solve it, I have the same problem.
Go to a Samsung Experience at a Best Buy. They can flash it with latest AT&T firmware.
Not sure why you want it though as Pie is a better OS. I keep AT&T updates package blocked at all times.
No issues. Up until a year ago was still running on Kitkat.
The scope storage issue with Q looks real ugly and has to impact performance.
Android is just an Apple coming out of the closet...
Hello guys!
I have a sim unlocked Galaxy S20 (SM-G980F) from Orange Romania and I want the new update (Android 12 and OneUI 4) and to get rid of the pre-installed apps from Orange. Apparently it is a known fact that some mobile network operators tend to postpone the new firmware updates (which I think it's stupid) because they have to 'test' it and load it with a bunch of useless apps that nobody needs. It wouldn't have been such a problem if this would happen in a timeframe of a few days, but usually it takes months. I contacted Orange and they said the upcoming update is being 'tested' and it will probably be released sometime in March (which again, it's just stupid).
I am looking for a way to change the Software Service Provider from ORO to ROM (or something else, to get the update directly from Samsung and not Orange); Samsung and Vodafone already rolled the update.
So, I have a few questions:
1. Can I change the Service Provider? (SM-G980F on Android 11)
1.1. If yes, how can I do it? Can you guys kindly guide me towards a tutorial?
1.2. Can I do it for free?
2. Should I just install a custom ROM? (I have seen many on this forum, but most of them seem to have problems if the high refresh rate is enabled etc... any reccomendations?)
Thank you guys! Any advice is much appreciated!
PS: I am kind of unfamiliar with these things, i used to flash custom ROMs on my old phones back when Cyanogenmod was a thing and I've used Android since 1.5. I don't know what changed and what's new so any help is welcome! Thank you!
First off, why do you even want Android 12 so badly? Early adopters catch all the bugs. And moreover, if you want to mod your phone, you'll quickly notice that a lot of popular mods aren't yet available for Android 12. As of today:
There still is not an official Magisk release for Android 12 (only Canary/pre-release builds).
Xposed module GravityBox for Android 12 has not been released.
Xposed module Firefds Kit for Android 12 has not been released.
And if you start modding, you're likely to find more things that just don't exist for A12 yet.
1. Can I change the Service Provider? (SM-G980F on Android 11)
Click to expand...
Click to collapse
Yes.
1.1. If yes, how can I do it? Can you guys kindly guide me towards a tutorial?
Click to expand...
Click to collapse
It used to be fairly easy. You could open the Preconfig dialog with a dialer code and change your CSC code. Loss of this functionality in recent software is lamented loss of this functionality in recent software is lamented here. There are many discussions about changing CSC code that make mention of the commercial software and service Samkey such as this and this; I have no personal experience with their offering so I can't recommend them. Interestingly it seems from the discussions that there is typically some lag between an Android release and support for that release from Samkey, so the trend I just referenced above is hardly an isolated phenomenon.
It's worth mentioning that the changing of CSC codes has been discussed extensively throughout the forum. One of the downsides of XDA though is that discussion is heavily segregated by device, so you can easily miss what you're looking for if you search only in a sub-forum for your device.
1.2. Can I do it for free?
Click to expand...
Click to collapse
With root, certainly. Otherwise, it is not so clear based on the above.
You can launch the Preconfig dialog from a root shell:
am start -n com.samsung.android.cidmanager/.preconfig.PreconfigActivity
I've noticed that in some configurations (notably when CSC code is VZW), the Preconfig dialog seems to be somehow disabled. However, with root access you can also simply edit /efs/imei/omcnw_code.dat.
2. Should I just install a custom ROM? (I have seen many on this forum, but most of them seem to have problems if the high refresh rate is enabled etc... any reccomendations?)
Click to expand...
Click to collapse
That's your choice. Browse the ROM section and see if there is anything available for your device that you like. Custom ROMs vary greatly in user experience as a consequence both the ROM's objectives and the developer's skill.
They all have a few things in common though: they will irrevocably trip the warranty void bit and cause a loss of Knox-related functionality (notably including Samsung Pay). They also will prevent you from receiving official OTA updates.
Another option is that you can simply root your device and start modding away yourself. Basically, that workflow is something like this:
OEM Unlock.
Boot into download mode with vol up + vol down + insert USB cable connected to PC.
Volume up to confirm unlock.
Flash TWRP from ODIN.
Flash Multi-disabler from TWRP.
Wipe /data from TWRP.
Install Magisk from TWRP.
Once you have root, you can not only change your CSC code as desired, but edit the read-only filesystems on your device, notably including the filesystems containing the CSC. It's even possible to blow away the CSC content completely and integrate the CSC content from the ROM of another region.
Of course, it goes without saying that you need to back up anything important on your phone before you start any experiments. Of particular importance, be sure to back up efs and sec_efs with TWRP and make sure the backups are stored somewhere safe (e.g., on a PC) before you start attempting any changes to efs partitions. A damaged efs partition is one of the easiest ways to render your phone useless. Note also that custom ROM installation almost always involves wiping /data somewhere along the way.
So, the bloatware you talk about is located in /product , /hidden or /odm depending on how your phone is configured. I can help you out contact me on telegram @cha0scl0wn. Regards.
Thank you guys so much for your replies!
I managed to launch the Preconfig dialog (dialing *#272*62826# in the stock phone app - other codes did not work, also tried the google phone app - nothing) but the only options to change the CSC are those in the picture (AMO - Orange Spain, FTM - Orange France etc). Basically I can select another Orange CSC which does not help. I want to change it to unbranded, to get the firmware updates directly from Samsung.
Now, if I root the phone, will I be able to change ORO to unbranded? But I'm a bit confused because rooting cancels OTAs, right? So I need to root, change CSC to unbranded (if possible) and then install the update myself? But then I will have to manually install every update?
If I root, change CSC to unbranded, install the update, unroot will I get the OTAs?
Rooting also kills Knox and Samsung Pay?
Thanks again guys for responding! I appreciate it! Cheers!
I managed to launch the Preconfig dialog (dialing *#272*62826# in the stock phone app - other codes did not work, also tried the google phone app - nothing) but the only options to change the CSC are those in the picture (AMO - Orange Spain, FTM - Orange France etc). Basically I can select another Orange CSC which does not help. I want to change it to unbranded, to get the firmware updates directly from Samsung.
Click to expand...
Click to collapse
Wow--you got lucky: I wasn't expecting the dialer code to work based both on my own experience and reports here on the forum. The Preconfig dialog is really just a testing tool: it allows you to select other CSC codes that already exist within the firmware and see the effects of those setting changes. I don't know if there is an effective unbranded configuration included on the OXM package (i.e., similar to XAA in the OYN package).
I don't have a lot of experience with the OTA updates (all my devices are unlocked).
Now, if I root the phone, will I be able to change ORO to unbranded? But I'm a bit confused because rooting cancels OTAs, right? So I need to root, change CSC to unbranded (if possible) and then install the update myself? But then I will have to manually install every update?
Click to expand...
Click to collapse
You'll still be able to select any CSC. I suppose in theory you could create your own CSC configuration for an imaginary carrier, but the route that I took was different. I stripped out all the unwanted junk out of the optics and prism images (along with de-bloating I did in a lot of other places in the ROM). I also edited all the XML configuration files that ship with the CSC to my liking (think: call recording on, shutter sound menu on, etc). After installing the resulting ROM, there was pretty much no carrier-specific software running on the device; splash screens, sounds, and other markings were also gone. I actually ended up adding a handful of carrier-specific content back to my ROM to get Wi-Fi calling working since it appears that the carrier I use (VZW) has a slightly nonstandard implementation of the feature.
But yes, once you head down this path, you'll be updating your phone by yourself, and it likely won't be the most enjoyable activity. I also don't feel the need for every single update, and I especially have no interest of moving to A12 in the foreseeable future.
Keep in mind that you should be able to pm disable bloatware packages that are really bothering you even without rooting/unlocking your bootloader.
My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?
The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/
Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?
If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.
TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.
chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.
chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!