Title says it all, is there a non root way to hurry up the update? I haven't had the popup to update android and was hoping there's a way to check for updates
Settings/system I believe, to check for updates or you can download and sideload the update.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Sideload the OTA
NippleSauce said:
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Click to expand...
Click to collapse
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
pcriz said:
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
Click to expand...
Click to collapse
You're pretty much correct here. I suppose that Google was a bad example to use. But essentially, the carrier builds allow the applicable carrier to also push apks through when you pull the update OTA. They're not necessarily packaged within the factory image - so I had some horrible word choices in my initial post as they don't really modify the image lmao. But (when looking at the older builds) if you just install the stock build instead of flashing one of the carrier builds, then you won't have to worry about any carrier apps being pulled in along with your OTA update.
But heck, if you're rooted and want to maintain root (and are thus manually updating whilst having OTA disabled), then you wouldn't have to worry about this at all, haha.
Samsung phones were a better example of this, as whenever I would do an OTA update on my S21U, it would also install around 4-5 T-Mobile bloatware apps. But if you manually installed the stock image, that wouldn't happen anymore when updating OTA.
Related
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.
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Capture the URL for it ?
Here is the link: https://ota.googlezip.net/packages/ota-api/google_marlin_marlin/d872269d3aff80d3b7f81d28c972d1d59f36f8f6.zip
(I'm not allowed to link to it directly due to my account age - sorry!)
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
This happened to me. I have a Verizon version dePixel8 and sideloaded E build a few days ago. Today I got the update message and it upgraded to K in about 2 minutes.
Gather this is for the Verizon models?
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
It's an update specifically for the Verizon Pixels. It contains a number of bug fixes and improvements according to the release info. A simple Google search will locate more info including the specifics of the bug fixes and improvements.
So this OTA will update my Google store device to the Verizon build? Weird. I'll just flash the whole build later.
So, after applying this update - what build does it show?
Just flashed the OTA. It does indeed update Google Store devices to the Verizon build of 7.1.2, NHG47K. Looking in the OTA zip, the update may only affect the system and vendor partitions.
I had this happen after I flashed the January build I think it was. I have a play store pixel on vzw and it was trying to update my regular stock rom the vzw-specific version. It sounds like if you're on vzw service then you'd benefit from their improvements. I'm waiting for beans to update his rom before I update from 7.1.1. I just hope it includes these vzw changes.
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
alsip1023 said:
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
Click to expand...
Click to collapse
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
hub1 said:
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
Click to expand...
Click to collapse
I was referring to the difference between the 7.1.2 builds, not the phones.
alsip1023 said:
I was referring to the difference between the 7.1.2 builds, not the phones.
Click to expand...
Click to collapse
So was I.
TonikJDK said:
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
Click to expand...
Click to collapse
Thanks for playing the guinea pig. Good to know nothing obvious was added in terms of bloat.
With that being said, that Pixel update is handed to Verizon to "test and certify". Then it is sent to the Pixels. Verizon only promised to not delay updates. They may still add apps, bloat, etc... Should they so choose.
Added information:
Google Store Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the right (as in enabled) but is overall greyed out after "K" update.
Verizon Purchased Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the left (as in disabled) but is overall greyed out after "K" update.
Not sure what this means. If anything, I found it interesting. Once it's unlocked, unless I submit a relock, it can't be relocked by OTA right?
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
gordonlw said:
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
Click to expand...
Click to collapse
Hello,
You bought a Google version, you are fine. You can sideload Verizon's OTA if you are on Verizon's network. Otherwise, no benefits...
Even true Verizon's unlocked Pixel owners, as long as they don't lock bootloader, it will stay unlocked, no matter what they flash FYI.
You can install SU with fastboot boot twrp as well.
Cheers...
Worked great thanks!
So because I have systemless root installed (Magisk) I'm not able to do the OTA update. However, when I try to sideload the OTA I receive a lovely error stating that the compatibility matrix and framework's do not match (something about AVB 0.0 isn't equal to 1.0 or something like that). So unless there's a way to force disable verification checks, I guess I'm left with loading the latest factory image. Then there is the issue of this.
I'm running Project FI. The current image appears to be the T-Mobile image, but there is a "Fi Carriers" image also. Which image should I flash? I'm asking, because I don't want to lose the eSim and I do plan on modifying the flash-all.bat and remove the "-w".
Sorry if this is a duplicate thread, but I didn't see anything else related.
mrdquick said:
So because I have systemless root installed (Magisk) I'm not able to do the OTA update. However, when I try to sideload the OTA I receive a lovely error stating that the compatibility matrix and framework's do not match (something about AVB 0.0 isn't equal to 1.0 or something like that). So unless there's a way to force disable verification checks, I guess I'm left with loading the latest factory image. Then there is the issue of this.
I'm running Project FI. The current image appears to be the T-Mobile image, but there is a "Fi Carriers" image also. Which image should I flash? I'm asking, because I don't want to lose the eSim and I do plan on modifying the flash-all.bat and remove the "-w".
Sorry if this is a duplicate thread, but I didn't see anything else related.
Click to expand...
Click to collapse
I didn't see anybody else answering your question so I'll explain how I understand it. If you bought your phone from Google directly and are using it on Fi, you should always flash the Fi variant of the system image if it's available. Often you will see a system image on Google's site and a duplicate for only one of the carriers. I don't know the difference because I'm too lazy to research it but if you haven't taken the leap already, I would use the Fi version
mrdquick said:
So because I have systemless root installed (Magisk) I'm not able to do the OTA update. However, when I try to sideload the OTA I receive a lovely error stating that the compatibility matrix and framework's do not match (something about AVB 0.0 isn't equal to 1.0 or something like that). So unless there's a way to force disable verification checks, I guess I'm left with loading the latest factory image. Then there is the issue of this.
I'm running Project FI. The current image appears to be the T-Mobile image, but there is a "Fi Carriers" image also. Which image should I flash? I'm asking, because I don't want to lose the eSim and I do plan on modifying the flash-all.bat and remove the "-w".
Sorry if this is a duplicate thread, but I didn't see anything else related.
Click to expand...
Click to collapse
I am the same as you.
Google Store bought 2XL
Running on ProjectFI.
This OTA isnt a big deal from what I have read so far so am not bothering.
In the absence of a specific FI Carrier OTA I typically flash the TMob.
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
ptmuldoon said:
I purchased myself a used (good/mint condition) LE2125 phone from Swappa as an Xmas gift and have been using it for about the past week or so. Really liking the phone so far.
But it is still on Oxygen OS 11.2.10.10. And each time I check for updates, it still tells me I'm up to date. I am in the US using the phone with Spectrum mobile, although phone sees the Sim as Verizon.
To my knowledge, phone has never been rooted.
Shouldn't I have received the update by now? Although I am still a little afraid to take it based on the initial update fiasco.
Should I just download the Oxygen Update app and go that route?
Click to expand...
Click to collapse
I also haven't received on the same device and version. So, it's seems like a slow rollout
If you manually check for updates in settings does it tell you you're up to date? If so, I'd just get the update from Oxygen Updater and do a local install. Some people did have issues with the first release of OOS12 (C36) but those should have all been resolved in the next one (C39). I never had any issues with the update personally.
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
ptmuldoon said:
Thanks,
The Oxygen updater wants to go to C.36 first. And then after that, I think straight to C.40. I will likely wait till later tonight to update as do not want to mess up phone while here at work today.
Click to expand...
Click to collapse
Probably because C36 is the full update. If it won't let you download both C36 and C40 at the same time (before updating), I'd make sure you have access to wifi in case you're one of the lucky few affected by the mobile network issue in C36. But most likely you'll be fine, the other issues were very minor and you wouldn't even notice if you just install the second update right away.
Does Chrome auto fill work for you on 12? I heard that it was broken, but don't know whether it's been fixed with C40? Holding off on updating until someone can confirm. Thx
EDIT: Decided to bite the bullet and upgraded to C40 on my L2125. I actually like it quite a bit, but can confirm that for me, at least, Chrome auto-fill doesn't work. Other nit is you cannot put the battery percentage in the status bar AND remove the icon; either you have both, none, or just the icon. Also, Netflix is pre-loaded, but won't open or uninstall and update and when I go to the Play Store it shows as incompatible with my device?? (bootloader unlocked, but not re-rerooted yet). Also the power menu no longer gives you a recovery or bootloader option in rebooting. Good things include having more gestures (raise phone to answer) and a panel to control apps that auto-start or not. Also, somehow m yreboot sequence no longer includes the danger, your bootloader has been unlocked, screen (which I didn't think was possible to get rid of).
Rolling back to Android 11 for now. Also, many more root options still available there (like Gravity Box and JamesDSP)
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.