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
Related
Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
EDIT: Phones are brand new- they are STOCK. (Not rooted)
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well liked rom image for the S3 currently? (Stable)
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of what needs to be done, but rusty on the "particulars".
.
WeAreNotAlone said:
Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well likely rom image for the S3 currently?
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of want needs to be done, but rusty on the "particulars".
.
Click to expand...
Click to collapse
Are you already rooted? If you update you could lose root I'm not really sure since I'm not on stock but it is easy to re-root it if you have too. And no updating wont permanently block your device from being rooted.
check out this thread: http://forum.xda-developers.com/showthread.php?t=1949687
it has all the official firmwares & pre-rooted official firmwares that are odin flashable
WeAreNotAlone said:
Samsung Galxay S III, S3 64GB currently running:
Android v 4.0.4
Base T99UVLH2
Kernel 3.08-925100-user (~snip)
***************
Quick question or two.
Just received 2 T-Mo branded Samsung Galaxy SIII's 32GB.
This last week bought several BlackBerry PlayBooks 64GB, and found out "if "they are *allowed to "update" to the latest version it encrypts /blocks ability to ROOT the device PERMANENTLY.
(* PlayBooks are set to auto-update upon being first powered up, PRIOR to access to OS. Special procedures and apps need to be used so it does not apply "update" which blocks ability to ROOT the device.
*Latest PB OS v 2.1.0.1088 = Encryts bootloader IIRC.)
Q1: I'm concerned about OTA update, or enabling (clicking) "Software Update" manually applying a rom update /newer version of Android OS screwing up ability to ROOT the phone. Is this a issue of concern?
Q2: I noticed when I hit the button for checking "if" there is a update available a file was showing 335.65mb, so for sure a "update" is available.
Would it be best to backup current rom image , or is that image available online?
(I would assume it would be best- I guess my question is, "Is the Samsung SIII Android v 4.0.4" image available?
Is it a problem to roll back to a prior version?
(Sort of paranoid after the PlayBook auto updating so it can't be rooted... YES I know PlayBook isn''t running a Android OS)
What is the most well likely rom image for the S3 currently?
Any info, links would be appreciated.
NOTE: I realize I have alot of reading to do, I have flashed /modded phones in the past so I have a grasp of want needs to be done, but rusty on the "particulars".
.
Click to expand...
Click to collapse
These aren't like playbooks or ONE X's. We can flash firmwares and updates through Odin. You are safe bro
j_smith305 said:
Are you already rooted? If you update you could lose root I'm not really sure since I'm not on stock but it is easy to re-root it if you have too. And no updating wont permanently block your device from being rooted.
check out this thread: http://forum.xda-developers.com/showthread.php?t=1949687
it has all the official firmwares & pre-rooted official firmwares that are odin flashable
Click to expand...
Click to collapse
RE: Are you already rooted?
Nope, bone stock. Would like to run the units for about 30-days (Of course that may change, EG Sooner)
Appreciate the links, will check it out.
On a recommendation on a rom, Looking for rom with a high WAF. (Wife Approval Factor)
Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
Lakeshow423 said:
These aren't like playbooks or ONE X's. We can flash firmwares and updates through Odin. You are safe bro
Click to expand...
Click to collapse
Thank you,
After experiencing the "joy" of PlayBook #1 of #4 doing a forced update to a OS version which was not rootable, plus was non reversible wanted to get a feel on what was going on. In the end with the PlayBooks I have (1) unit left that I'm debating to root or not... REASON? There's like (1) person on the CrackBerry forums that has a in-depth knowledge of the QNX OS.... and the info on flashing a "rootable" version of the OS is not well documented. (Info is scattered amongst multiple threads- the (1) poster with a in-depth knowledge posts in a cryptic fashion.
Process seems pretty simple, but there is little "traffic" in the rooting section so that does not inspire confidence in getting answers to problems that may pop up after the "root".
From what I read BlackBerry /RIM closed the loophole that allowed the PB's to be rooted fairly quickly and numerically the numbers of persons who even have a "rooted" PlayBook is few and far between, VS those with Android powered devices. )
Getting back to the Samsung,
As noted above: Looking for rom with a high WAF. (Wife Approval Factor)
Stability is a factor, and "time" tweaking is at a premium.
What rom would you recommend?
PS: Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
(If tethering can be done without rooting, may leave the units stock for about 30-days or so until hardware is proven to be defect free. If you have any info on that, I'd be all ears.)
.
WeAreNotAlone said:
Thank you,
After experiencing the "joy" of PlayBook #1 of #4 doing a forced update to a OS version which was not rootable, plus was non reversible wanted to get a feel on what was going on. In the end with the PlayBooks I have (1) unit left that I'm debating to root or not... REASON? There's like (1) person on the CrackBerry forums that has a in-depth knowledge of the QNX OS.... and the info on flashing a "rootable" version of the OS is not well documented. (Info is scattered amongst multiple threads- the (1) poster with a in-depth knowledge posts in a cryptic fashion.
Process seems pretty simple, but there is little "traffic" in the rooting section so that does not inspire confidence in getting answers to problems that may pop up after the "root".
From what I read BlackBerry /RIM closed the loophole that allowed the PB's to be rooted fairly quickly and numerically the numbers of persons who even have a "rooted" PlayBook is few and far between, VS those with Android powered devices. )
Getting back to the Samsung,
As noted above: Looking for rom with a high WAF. (Wife Approval Factor)
Stability is a factor, and "time" tweaking is at a premium.
What rom would you recommend?
PS: Also on the hunt for a work-around to enabling tethering on Android 5GB plan.
(If tethering can be done without rooting, may leave the units stock for about 30-days or so until hardware is proven to be defect free. If you have any info on that, I'd be all ears.)
.
Click to expand...
Click to collapse
If it's for your wife then I would probably stick with stock so she doesn't complain about minor bugs lol or you could try a touchwiz based rom. Just check out the different roms in the android development & original android development thread and see if you find any that you like
As for tethering I can't help you much since I don't really use it. I did a quick search and found this thread that might be able to help: http://forum.xda-developers.com/showthread.php?t=1988735
If you are wanting to root I would use the root injected rom. The instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1771687
This gives root but fully stock otherwise. It is probably one of the safest ways to root.
Sent from my SGH-T999 using xda app-developers app
ioitall said:
If you are wanting to root I would use the root injected rom. The instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1771687
This gives root but fully stock otherwise. It is probably one of the safest ways to root.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
That sounds exactly like what I, and others than are concerned about "warranty" issues on new phones- baring a total hardware failure would benefit from until the hardware is proven itself to be DEFECT FREE.
Would like to "burn-in" the device, making sure nothing is amiss.
Thanks!
mrRobinson said:
This is a completely stock ODIN flashable ROM with root injected into the system image.
This is a fairly easy way to get root WITHOUT tripping the flash counter that will void the warranty. If you don't care about tripping the counter then you can get root other ways.
Click to expand...
Click to collapse
Hi,
I am sadly no mobile expert and need your kind support. Since over half a year I have 2 problems
very frequent phone call interruptions
much lower battery life time
My phone/sim provider in Germany are Vodafone and Congstar. But I do not think its related to them.
All the trouble started after a certain upgrade to newer versions of Android OS, but can't remember when this exactly started. Then the battery life went down significantly and I get those annoying interruptions in phone calls up to 3-4 times in a ~15 minute call. Its so bad .. What could you recommend to me ?
Is there a better image downloadable, maybe fallback to older version ?
Or is it possible to fallback to the version in ROM ? I fear side effects and unfixed system holes by this.
Thanks for any help !
BR
Moin,
I highly recommend you to switch to CyanogenMod. I took the switch to CM right after i bought my GT-I9195 and all I can say I've never expirenced such problems either on Vodafone nor O2. ATM I'm still at CM11 as this is rock stable and battery life is quite good, ~2-3 days depending on usage
Just follow this steps and you've got nothing to worry about.
1. install custom recovery
2. take a full backup of your current system + SD Card just for the case...
3. install CM11 for your phone + pico OpenGAPPS
4. flash the latest Modem EUR region for your phone right after
5. use it for a few days without any Custom kernel and a minimum of installed apps
6. if your not satisfied restore the backup from step 2.
Sounds simple...it is indeed.
Regards / Grüße
DonQ
DonQuichotte said:
Moin,
I highly recommend you to switch to CyanogenMod. I took the switch to CM right after i bought my GT-I9195 and all I can say I've never expirenced such problems either on Vodafone nor O2. ATM I'm still at CM11 as this is rock stable and battery life is quite good, ~2-3 days depending on usage
Just follow this steps and you've got nothing to worry about.
1. install custom recovery
2. take a full backup of your current system + SD Card just for the case...
3. install CM11 for your phone + pico OpenGAPPS
4. flash the latest Modem EUR region for your phone right after
5. use it for a few days without any Custom kernel and a minimum of installed apps
6. if your not satisfied restore the backup from step 2.
Sounds simple...it is indeed.
Regards / Grüße
DonQ
Click to expand...
Click to collapse
1st of all you talk about your GT-I9195 model which is a normal S4 mini, but I have the DUAL SIM version.
Thanks but I want to stay with the normal SW train, I installed CM on a S3 1y ago and I didn't like the look and feel. So CM is not an option for me.
Besides my preferences, if I look at this article its nice to see, that there is progress for the DUAL SIM version but there are still known issues like stuttering problems and of you look down further the auther doesn't intend to create a CM official version out of it, so it looks more like a "hack" than something which is further supported by CM. Looks like an ALPHA SW and a one way road to me. http://forum.xda-developers.com/showthread.php?t=2790789
So .. other ideas ?!
Hello,
One point before flashing: your knox is 0x0 ? 1st flash result 0x1 and warranty lost.
Choice is to flash and try to solve this problem by yourself but lost the warranty or see with samsung support what they can do, but after 1st flash there is no coming back.
Kralisec said:
Hello,
One point before flashing: your knox is 0x0 ? 1st flash result 0x1 and warranty lost.
Choice is to flash and try to solve this problem by yourself but lost the warranty or see with samsung support what they can do, but after 1st flash there is no coming back.
Click to expand...
Click to collapse
I have no clue about knox. I am using the smartphone with a private and a company SIM.
But there are is company deployed SW on the smartphone. Also e-mail is pure private.
I only use DUAL SIM for the purpose of being able to make company phone calls with the company SIM.
Is there no way to get rid of 4.4.2 ? I remember the phone has been sold with 4.2.x.
Is there no 4.2 stored somewhere on the phone which can be reactivated ? At least then I could check, wheter it runs more stable and whether battery life is then better. But in fact I have no Kies backup, as I hate this bloated software.
Knox information : https://en.wikipedia.org/wiki/Samsung_Knox
more important: at the end, e-fuse part: "This information may be used by Samsung to deny warranty service"
Kralisec said:
Knox information : https://en.wikipedia.org/wiki/Samsung_Knox
more important: at the end, e-fuse part: "This information may be used by Samsung to deny warranty service"
Click to expand...
Click to collapse
Is somebody able to explain to me in easy words, what this all now means to me ?
Does this mean, I can't do a downgrade without loosing any kind of warranty ?
Should this be the case, I assume I am stuck n the 4.4.2 path and can only hope for vendor support (Samsung).
So shall I open a case with Samsung and hope that they fix the issue should it be a SW related issue ?
In short: if you flash using odin or heimdall for the 1st time you will loose your warranty.
Samsung update is merged inside rom, it's not something you can just uninstall.
I don't know if usual samsung tool let you downgrade to a previous version
(this time without knox issue since it's pure samsung way to update)
Last year, I bought my first ever Android - a Galaxy S7 Snapdragon. Unfortunately, I soon learned that without root & Titanium, Android provides no way to do a proper/complete backup (i.e. SmartSync doesn't backup any app data, & Helium backs up some but misses many - WhatsApp, LINE, Viber, etc). Thus I returned the S7, took a brief hiatus, & am now eagerly awaiting the arrival of a brand new Exynos S9
I wanted to ask for any quick advice as to the "suggested" approach for rooting, so I can hit the ground running as soon as this thing arrives. As I understand it, there are 3 main approaches:
1) Install TWRP, stick with the stock Samsung ROM & flash SuperSU
2) Install TWRP, stick with the stock Samsung ROM & flash Magisk
3) Install TWRP, flash a custom ROM that's already rooted
Between 1 & 2, my understanding is that Magisk is preferable to SuperSU as it essentially accomplishes the same thing but without necessarily blocking OTA updates or some financial applications from working. True? So is there even any reason to consider #1? If not, any insight as to choosing between #2 vs (any specific custom ROMs)?
My long-term priorities are simply for the phone to run as well as possible, with as little maintenance as possible (i.e. as far as ease of getting security updates goes). I'm not really into lots of customization, experimenting, etc - I'd prefer to just get something up & running, stable, & stick with it. I will be using T-Mobile though, so I guess in either case I'll need to install this to get WiFi calling & VoLTE working. Also, I want to make sure that whichever root solution I choose, it can coexist with Secure Startup (the S7 Snapdragon's root couldn't, which was a dealbreaker for me).
Any insight would be greatly appreciated. The phone arrives Tuesday, I can't wait to get started!
As soon as you flash twrp your not going to get OTA updates nevermind root.
sent from my Pixel 2 XL or Note FE
Unfortunately i made a silly mistake, i wiped the EFS partition of my G960FD once rooting the device while not having any backup for it
i tried flashing official rom, combined roms, cutoms roms; but always, i have the same problem "unknown IMEI and Baseband"
even, i tried to use ODIN Nand Erase All and installing new fresh official rom and also, have the same problem
is there any recommendations, please?
hanymedic said:
Unfortunately i made a silly mistake, i wiped the EFS partition of my G960FD once rooting the device while not having any backup for it
i tried flashing official rom, combined roms, cutoms roms; but always, i have the same problem "unknown IMEI and Baseband"
even, i tried to use ODIN Nand Erase All and installing new fresh official rom and also, have the same problem
is there any recommendations, please?
Click to expand...
Click to collapse
Samsung repair centre
*Detection* said:
Samsung repair centre
Click to expand...
Click to collapse
They asked me to pay 400$ for replacing the mother board
that's why i asked for having any solution
hanymedic said:
They asked me to pay 400$ for replacing the mother board
that's why i asked for having any solution
Click to expand...
Click to collapse
when you say combined roms do you mean the factory binary firmwares? because if flashing the combination firmware/factory binary followed by the usual rigmarole factory reset, nd reflash official fw doesnt work you could try rebuilding the partition using adb shell (root access needed for this though)
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
this link isnt for the s9 smg960f but it did work for me when trying to solve the same issue on the sm-g950f,
anyway hope this helps in some way
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.
Hi everyone,
My Fold 3 started showing wierd sympotoms after Abdroid 12 update however I thought they might get fixed with the next upgrade. Last night I received Android 13 upgrade but to my surprise the issues with my phone stayed same.
My phone is official, no rooting or bootloader unlocking. Knox tripping is 0x0. The same result is shown by the Diagonostics in Members app.
My employer needs me to install work profile that this phone is not allowing and throwing an error saying I have a custom OS. I cannot boot into the bootloader from the recovery menu and getting a smart select error. Moreover I cannot login to Samsung Pay (stuck at fingerprint authrized) and Samsung Pass (Currently not available error: 162)
I have added all the possible screen shots for ready reference.
Can you please advise as what can I do to fix this annoyance! Many thanks in advance
try reflash latest official rom with full data erase
AndrOmega said:
try reflash latest official rom with full data erase
Click to expand...
Click to collapse
Thx for ur reply. I tried doing this already. Situation remains same.
It isn't Maas360 that you are trying to install by chance?
imapfsr said:
It isn't Maas360 that you are trying to install by chance?
Click to expand...
Click to collapse
I am not aware of Maas360!
Can anyone with knowledge help as I need to setup my office profile urgently. My second phone is acting up...
If your phone is not modified in any way, then I would go straight to Samsung. Someone here might be able to help, but in cases like this, Sammy might be your best bet.
Its not modified however Samsung wants to change the mother board and charge big as its out if warranty.
Thats the reason I turned to the community as I have got many issues fixed from the wonderful people that Sammy wanted to charge otherwise.
Update your Google services. Says July, last is October!