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.
Related
Hi - I bought a Note 8.0 for my Daughter for Christmas. She's only 9 so I was planning to setup a restricted user - but I was surprised to find multiuser is not enabled on this device.
Just wanted to confirm before i return it - there's no way I can enable multi-user this without rooting the device, tripping KNOX switch and therefore invalidating the warranty (something I'm not really prepared to do on a device which is only a few weeks old) ?
PeaTines said:
Hi - I bought a Note 8.0 for my Daughter for Christmas. She's only 9 so I was planning to setup a restricted user - but I was surprised to find multiuser is not enabled on this device.
Just wanted to confirm before i return it - there's no way I can enable multi-user this without rooting the device, tripping KNOX switch and therefore invalidating the warranty (something I'm not really prepared to do on a device which is only a few weeks old) ?
Click to expand...
Click to collapse
I had the same problem when I purchased my unit and again after they release the OS upgrade to 4.4.2. After a great deal of searching I found the best method was to do a factory reset. Power the unit down then press and hold the Volume Up Button, Home Button and Power Button. Follow the menus to do a Factory Reset. I tried the Factory Reset from the Setting Menu, but it didn't fix the problem. Afterwards and for almost a year everything has worked perfectly.
Thanks for the reply - are you saying that a factory reset enabled the multi-user feature on your device ?
I just tried it, but unfortunately the result is the same : no 'users' option in the settings and no way to switch users on the lock screen. From what I've read, the multi-user option is disabled in the UK firmware. I guess you must be using firmware from another region ?
You must root, though you will void warranty on kk note 8.0.
Once rooted, add in the build.prop, ro.users=4
Reboot after saving. Have used it on 4.1.2 and 4.2.2, should work on kk.
gooberdude said:
You must root, though you will void warranty on kk note 8.0.
Once rooted, add in the build.prop, ro.users=4
Reboot after saving. Have used it on 4.1.2 and 4.2.2, should work on kk.
Click to expand...
Click to collapse
Hi everybody
I have the same problem. I've rooted and set the ro.users entry. I've also performed the factory reset. I cannot get the option to add another user to be displayed (I suppose it should be in the settings).
Could you please try to help me? Many thanx in advance.
ferroz said:
Hi everybody
I have the same problem. I've rooted and set the ro.users entry. I've also performed the factory reset. I cannot get the option to add another user to be displayed (I suppose it should be in the settings).
Could you please try to help me? Many thanx in advance.
Click to expand...
Click to collapse
OK, I tested with my testing kk note 8.0 and found Samsung disabled the feature. So, the only way to get it back is to use exposed multi users module to enable the feature.
Ok thank you very much I'll try that.
I've also tried the SwitchMe app but couldn't create new profiles, any experience with that?
The Canadian version (which was one of the earlier 4.4.2 builds to be released) also lacked multi-user, but was easily brought back by using something like Xposed. The US version of the ROM (which came out a few months later) did have it enabled (and it's the ROM I'm running now). Not all 4.4.2 builds were built at the same time and I believe that the later ones (say those built in July or later) have the feature. It could be something that's restricted by region, but I don't think that's necessarily the case here. It was probably an oversight because it runs perfectly fine on my Canadian model and other Samsung tablets they sell here have it enabled by default too. So if you still want the stock ROM but no root, you could try flashing a ROM using Odin from a different country with a build date newer than May 2014. I think that should work without triggering the Knox flag. Just be careful as EU standards for Wi-Fi are different than NA so there might be issues with certain channels in the N band if you're using an EU ROM in the US. Conversely, if you run the US ROM in the EU, you may be in violation of the region's laws governing radio frequencies since some of the bands that the US considers safe are restricted across the Atlantic. So instead, try flashing a ROM from a country that's nearby but was released after June or July. If you need to later on, you can always use Odin to re-flash the stock ROM that it came with before returning it.
Sent from my SGH-T859 using Tapatalk
I've asked portions of this before in this forum, but am asking again in more detail to make sure I comprehend what I'm contemplating...
1) I understand that I can REPLACE a stock ROM from one region (BRI) with a stock ROM from a DIFFERENT region (BTU) as long as the replacement (BTU) is at dated at least as recently as the one being replaced (BRI). And doing so via ODIN won't trip KNOX.
2) Is it necessarily the case that such a replacement will wipe all of my current settings?
3) Will a manual (non-OTA) update of the existing ROM w/o changing regions ALSO wipe my current settings? (I've used TR so can't use the OTA option anymore)
Reading in this forum seems to indicate "YES" to both 2 & 3, but I seem to have run across different thoughts elsewhere. I know when I've done OTA updates, there's usually a warning that I will or might lose all my settings, though that's never happened to me.
Thanks for the patience.
Hello,
I just got and Samsung galaxy S3 from a family member. And first thing I did, was reset it to factory settings. Which went ok.
Now I would like to update the phone. Current android version is 4.1.1. When I go into update section of the phone I get message that current phone version is up to date, but I read on the internet that latest version is 4.4.2. How should I best proceed in order to update the phone.
Also, I have several questions which I've been wanting to find out (Please note that I'm quite new to android):
1. This phone was rooted. It appears that after factory reset it is still rooted (According to Titanium Backup) is that how it should be? I thought that after factory reset phone would not have root access. Also what is strange, that after performing a factory reset I already had quite old version of Super Su pre-installed and CyanogenMod file manager, why is that?
2. I have an AT&T version of the phone. But I live in Europe where there is no sign of AT&T. Is it possible to remove AT&T branding? Also this phone has some kind of custom Adnroid software update "AT&T software update", which always tells me that v4.1.1 is the latest version of android available for my phone. Is it possible to revert back to native software update?
3. I did a factory reset on the phone about 30 minutes ago, how it already has 5.5 GB of free space used? - For some reason factory reset didn't remove music and photos.
4. I found the application named "System app remover". Can I trust its judgement on which apps are safe to remove?
5. How can I make sure if I have 2core processor or 4 core processor? - I downloaded this program "CPU / RAM / DEVICE Identifier", I have 2 core snapdragon processor
Hi Viltnieks!
You are correct: there have been newer Android updates released for the Samsung Galaxy SIII (SGH-i747/SGH-i747M variants). I know you tell you got an AT&T variant of the phone, but just to make sure, please double-ckeck under the Phone Settings --> About Phone that your device model is the SGH-i747 one. This info can also be found on a sticker under the battery. If you have another SGSIII device model, you are in the wrong forum.
I'm not exactly sure to pinpoint your phone's current state. At one point, you say that it has the AT&T Updater, but it also has been rooted, and contains CM file manager... As you want to update the phone's OS (ROM) to a newer version and would like to remove AT&T branding, I'll just straight skip to your second point:
viltnieks said:
2. I have an AT&T version of the phone. But I live in Europe where there is no sign of AT&T. Is it possible to remove AT&T branding?
Click to expand...
Click to collapse
There are basically three kinds of ROMs:
1. the official, carrier's ROM;
2. custom ROMs based on the carrier's official ROM. Those are ROMs created by the community, but are build on the carrier's one;
3. custom ROMs based on the Android Open Source Project, or one if its derived ROMs.
If you flash the first kind of ROM, you will have all the official stuff provided by AT&T, exactly as if the phone was brand new, out-of-the-box; this also imply that you will get all the AT&T stuff (AT&T Updater, AT&T-related softwares, AT&T branding...). If you flash the second kind of ROMs, you may get some of the AT&T stuff, though generally speaking ROM developers do a pretty good job at removing unneeded carrier junks and branding, or allow the user to choose which of the carrier-apps he wants to install or not. The third kind of ROMs are the cleanest kind looking at carrier-related stuff: it does not have those kind of things.
I have not given you a straight answer, as it is not my place to choose for you what you want. Still, I believe if you want to get rid of AT&T's branding, you would be more interested in custom ROMs, either carrier-based ones or AOSP/CM-based ones. For this reason, I would suggest you take a look around in the Android Development and Original Android Development sub-forums, where lots of custom ROMs are published by developers. Read the first posts of the threads, you will find what ROMs have to offer, what they look like, if they are based on stock or on AOSP/CM, if they are debloated, etc. The first posts also contain informations on how to install, so carefully read them.
You need to be running a completely stock ROM in order to receive OTA updates. This mean you cannot be rooted, stock apps should be present, and stock recovery.
Thank you for replying!
After double checking I can verify that model number indeed is SGH-i747. I also get AT&T logo before samsung logo when powering up, AT&T phone book and some other AT&T applications.
It has the AT&T updater, yes, but it isn't working. I always get "Software update interrupted. No update is available.." Or "Current software is up to date. You may check again in 24 hours"
And, indeed it has CM file manager and Super SU app installed, even If I do factory reset, these apps show up without installing. I guess it means that this is some kind of custom rom based carrier's ROM?
If I have a rooted phone, is it normal that it will stay rooted after factory setting reset?
I'm quite new to this, I wanted to clarify, ROM is like a version of android os?
I don't really need any of the carrier's stuff, so I guess 3rd kind of ROM would be best for me.
Is this the place where to look for roms - http://forum.xda-developers.com/galaxy-s3-att#romList?
Preferably I would like the phone to have global ROM, the one that comes with samsung galaxy S3, before carrier's add their stuff.
Factory reset will not remove the CM File Manager or SuperSu because they were probably installed via custom recovery or Odin. Only apps installed from the ROM itself will be removed.
I suggest installing the Samsung Phone Info app from the Play Store to determine the bootloader and modem installed on your phone and report back. The bootloader version is important to know before flashing anything.
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
metalik said:
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
Click to expand...
Click to collapse
There is a post in different thread that should answer all of your questions. I couldn't write it better myself, so here you go https://forum.xda-developers.com/xperia-xz1-compact/development/help-t3889845/post78673359
I hope it helps.
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
metalik said:
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
Click to expand...
Click to collapse
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Didgesteve said:
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Click to expand...
Click to collapse
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
the right question would be, how to get the latest security patches but staying with oreo?
vofferz said:
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
Click to expand...
Click to collapse
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
metalik said:
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
Click to expand...
Click to collapse
First take a screenshot of your current keystore status by typing this in the dialler *#*#7378423#*#*, then go to Service tests or Service info -> Security
I used newflasher since it's the last updated software for flashing.
Extract your ftf if required, put only the required files to downgrade in newflasher's folder. For me I only used kernel, system, userdata and cache.
Boot to flash mode, flash using newflasher, reboot and done! Make sure your keystore is intact by comparing the status of all keys with your screenshot.
I've used this method to downgrade temporarily, get temp root, backup my TA partition and then go back to current firmware. All keys intact.
metalik said:
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
Click to expand...
Click to collapse
I would flash everything else but the .ta and persist*.sin to ensure it works as intended with all files from the firmware you're using. Of course that resets all your userdata, but I guess a downgrade would require that anyway.
Warranty should be just fine - you're still just using official Sony firmware without any modifications to the device or system.
I don't think it will be possible to stay in official Oreo fw with locked bootloader and get recent security patches.
Sony will most probably implement the new patches only into the latest fw version - and that's Pie.
And if someone would make a custom rom with the latest patches on Oreo, you won't be able to install it with a locked bootloader.
Hello again,
what's the impact of flashing persist*.sin ... I believe that's connected with the attest keys, right?
Later edit: I downgraded from Customized DE Pie to Customized UK Oreo. I used newflasher, deleted all *.ta from the root & boot folder ... but by mistake I forgot about the one small persist*.sin file.
Long story short: yes, leaving persist*.sin file in the folder and flashing with newflasher destroyed the Attest keys (I get them as NOT provisioned).
The phone seems to work without problems nevertheless. I re-flashed to an older Customized DE Pie and got the last valid OTA update. Going back to Customized UK Oreo did remove everything from the Service Tests > Security (it showed "none"). But on that the Xperia Companion did the trick (software repair). So it's back on the initial Customized UK Oreo - just attest key shows NOT provisioned ... so
Lessons learned: /*.ta + /persist*.sin + /boot/*.ta must be removed before flashing with newflasher.
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
Hey,
sorry for the late reply ...
I kept everything that I (historically) downloaded with Xperifirm ...
I just checked and one folder is this "G8441_Customized UK_1310-6856_47.1.A.16.20_R18B" ... about 2.55 GB in size.
the content of fwinfo.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<fwinfo>
<project>Lilac</project>
<product>Xperia XZ1 Compact</product>
<model>G8441</model>
<market>United Kingdom</market>
<operator>Customized UK</operator>
<swId>1307-7511</swId>
<swVer>47.1.A.16.20</swVer>
<cda>1310-6856</cda>
<cdfVer>R18B</cdfVer>
<fsVar>GENERIC</fsVar>
</fwinfo>
and update.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<UPDATE>
<SYSTEMPARTITIONIMAGE>partition.zip</SYSTEMPARTITIONIMAGE>
<BOOT>boot.zip</BOOT>
<NOERASE>appslog_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>diag_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>ssd_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>Qnovo_X-FLASH-ALL-C93B.sin</NOERASE>
<FACTORY_ONLY>persist_X-FLASH-ALL-C93B.sin</FACTORY_ONLY>
<NOERASE>userdata_X-FLASH-CUST-C93B.sin</NOERASE>
<SIMLOCK>simlock.ta</SIMLOCK>
<NOERASE>cust-reset.ta</NOERASE>
<NOERASE>master-reset.ta</NOERASE>
<RESETNONSECUREADB>reset-non-secure-adb.ta</RESETNONSECUREADB>
<NOERASE>reset-wipe-reason.ta</NOERASE>
</UPDATE>
in a nutshell: I can zip the folder and find a way to send it to you.
Best regards,
Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Xperia XZ1 Compact 47.1.A.16.20 Firmware Search
metalik said:
in a nutshell: I can zip the folder and find a way to send it to you.
Click to expand...
Click to collapse
Shahnewaz said:
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Click to expand...
Click to collapse
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
@cynthi4 Customized NOBA (nordic/baltic) latest Oreo: http://aeitis.org/xz1c/
It's downloaded and decrypted via xperifirm and zipped.
I'll keep it there for a while, but might remove soon.
cynthi4 said:
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
Click to expand...
Click to collapse
Here you go:
https://bigboidrive.duckdns.org/nextcloud/s/ZW4FQmqBE8Dfcp2
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
moist_line said:
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
Click to expand...
Click to collapse
Unless you have any specific issues with Oreo or see some advantage with upgrading to Pie, I wouldn't. I am not a big fan of Pie and went through this downgrade to 47.1.A.16.20 to avoid it. If you're interested in custom ROMs, I am running LineageOS 15.1 on my xz1c and it's been great!
That's strange. Being still happy with my locked device, I've always regretted switching to pie so today I actually did the whole process to restore Oreo: downloaded the latest Costumized NOBA oreo the user few posts above linked, deleted *persist.sin and every *.ta files in the folder (even the one inside boot folder), run newflasher and then reboot. Too bad I found stock camera broken
I re-checked multiple times searching for those *.ta files to be sure to avoid this issue, but that's it: I got Oreo but now I have lost stock camera and who knows what else.
Does it mean I've lost those functionality forever? Is there any way to restore stock camera? Happy to see this thread still active
Hey guys! I have an LG G8 Thinq (LM-G820UM), stock OS, no root. I use Mint Mobile in the US.
I configured the APN settings according to Mint's website and I can call, send SMS/MMS, and get internet access just fine. But, I can't seem to use WiFi calling (though it's enabled on my Mint account) and I have not received a software update since March of 2021.
It says I am on the latest software version, but I have Android 10, and I've heard other Mint users are on 11 or even 12 with the same phone.
What can you recommend for me to make this work? I'd prefer not to root, but I am willing to. Can anyone ELI5 or link me a guide to fix this?
Thank you!
KillerTuxedo said:
Hey guys! I have an LG G8 Thinq (LM-G820UM), stock OS, no root. I use Mint Mobile in the US.
I configured the APN settings according to Mint's website and I can call, send SMS/MMS, and get internet access just fine. But, I can't seem to use WiFi calling (though it's enabled on my Mint account) and I have not received a software update since March of 2021.
It says I am on the latest software version, but I have Android 10, and I've heard other Mint users are on 11 or even 12 with the same phone.
What can you recommend for me to make this work? I'd prefer not to root, but I am willing to. Can anyone ELI5 or link me a guide to fix this?
Thank you!
Click to expand...
Click to collapse
Well first, Mint is not a carrier, they are an MVNO. They 'resell' T-Mobile network. So, it's not Mint that would update the OS, it would be whatever OS was originally (or rather currently) on the device.
So Mint doesn't care what OS variant you're using (Sprint, VZW, ATT, etc), but that' doesn't mean all the features will work (like vowifi).
I use Mint and have found that crossflashing my Sprint device to the latest US Open OS version (a11), everything will work; VoLTE, VoWifi, data, sms/mms, etc.
Mostly, the only way you would see an OTA update is if you are using the correct OS and that carriers network. That's not completely accurate though, some carriers will send an update over wifi without a (usually needed) carrier specific sim card, but that's hit or miss, no guarantees (I've had a Sprint phone that did it, but ATT is known to never do it).
You don't have to root to crossflash. But it's a real good idea to back up your entire rom before doing anything, or at the very least the essential partitions that are specific to your phone.
cheers
AsItLies said:
Well first, Mint is not a carrier, they are an MVNO. They 'resell' T-Mobile network. So, it's not Mint that would update the OS, it would be whatever OS was originally (or rather currently) on the device.
So Mint doesn't care what OS variant you're using (Sprint, VZW, ATT, etc), but that' doesn't mean all the features will work (like vowifi).
I use Mint and have found that crossflashing my Sprint device to the latest US Open OS version (a11), everything will work; VoLTE, VoWifi, data, sms/mms, etc.
Mostly, the only way you would see an OTA update is if you are using the correct OS and that carriers network. That's not completely accurate though, some carriers will send an update over wifi without a (usually needed) carrier specific sim card, but that's hit or miss, no guarantees (I've had a Sprint phone that did it, but ATT is known to never do it).
You don't have to root to crossflash. But it's a real good idea to back up your entire rom before doing anything, or at the very least the essential partitions that are specific to your phone.
cheers
Click to expand...
Click to collapse
Thanks so much for the explanation and the advice! I will begin researching crossflashing, pretty sure I've seen a couple of detailed posts here about it.
Is there a method to backup my ROM without root? I'm familiar with the process with TWRP installed, but not sure how to do it without. Would it be easier to just unlock the bootloader, flash TWRP + Magisk, backup, and then crossflash, rather than do it all without root?
Also, were you able to get an OTA update from Mint/T-Mobile once you crossflashed to the US Open OS version? Or would I have to flash an Android 12 ROM to upgrade?
Thanks again for the help, apologies for my newbieness. Just trying to get all my ducks in a row before I get hasty and brick my phone. lol
KillerTuxedo said:
Thanks so much for the explanation and the advice! I will begin researching crossflashing, pretty sure I've seen a couple of detailed posts here about it.
Is there a method to backup my ROM without root? I'm familiar with the process with TWRP installed, but not sure how to do it without. Would it be easier to just unlock the bootloader, flash TWRP + Magisk, backup, and then crossflash, rather than do it all without root?
Also, were you able to get an OTA update from Mint/T-Mobile once you crossflashed to the US Open OS version? Or would I have to flash an Android 12 ROM to upgrade?
Thanks again for the help, apologies for my newbieness. Just trying to get all my ducks in a row before I get hasty and brick my phone. lol
Click to expand...
Click to collapse
No worries, all good questions and not that easy to find the answers.
The best back-up method, imho, is to use the bkerler edl utilities (g search that, you'll find the github page).
Using twrp, what you can backup will be limited, but you can use dd commands to backup via twrp adb interface, but that's very time consuming.
I've never gotten an OTA update on LG phone if not running their specific OS, and not rooted or crossflashed to it. But, no big deal as pretty much now, there are no updates. Only the available KDZ and after flashing / xflashing to one of them, there won't be updates to it.
At this time, LG has not released any a12 roms, afaik. There are supposedly 'plans' to do so, but I'd bet it never happens.
cheers