Hi,
I have some problem about build.prop and magisk
i install module enable camera2api in my phone (mi note3 stock rom eu)
after i reboot and check command in build.prop
it show #persist.camera.HAL3.enabled=1 not persist.camera.HAL3.enabled=1
How to fix this issue ?
Thank you
Magisk doesn't directly edit the build.prop file, only the values. Use the the getprop command in a terminal emulator to check the new value.
Update: This Method works on Oreo and Pie as well
Good day
First thread here so please go easy on me
This is a small guide on how to increase the headphone volume for Nokia 5 (TA-1053). Might work on other models too...
Things you need:
0. Nokia 5 TA-1053
1. Unlocked bootloader
2. Root
3. Third party file manager (Root explorer, ES, etc.)
Phase 1:
> Unlock and root your phone. This helpful thread will guide you:
https://forum.xda-developers.com/nokia-5/how-to/root-twrp-nokia-5-t3703423
**You need to downgrade to Nougat to unlock and root the phone
Phase 2: access root filesystem and Mixer_paths
> Open your file manager app
> On ES file explorer, grant root acces on app then go to Home > Local > Device > etc
> FOR ANDROID OREO/PIE: Mixer_path_nd1 is located at root/etc/vendor
> Usually on custom roms like Lineage OS for Qualcomm devices, you can find a single file named Mixer_paths.xml. however on Nokia devies it consists of 20 mixer_paths due to HMD distributing similar software across different models like the Nokia 6 (not sure why but i saw a D1C mixer_path, and D1C is a Nokia 6)
> Now look for a file named "Mixer_paths_nd1.xml" then open it via a text editor
> Scoll down until you see "these are inital mixer settings". Locate these tags:
Rx1 digital volume
Rx2 digital volume
Rx3 digital volume
Default value is 84, so change it so something higher. I set mine to 92
> After changing the mixer path value, save the file (with root access) and exit the app. And restart the phone
> Enjoy the loudness
Phase 3 (optional):
For better audio experience, try installing Viper4Audio 2.7, which can be found here:
https://www.xda-developers.com/viper4android-v2-7-new-ui-profile-management
DONE!
Thanks to:
@wolfyapl for the bootloader unlock/TWRP guide
Team DeWitt for the Viper4Audio material design app
Viper4Audio Team
HMD Nokia
XDA community
Hey,
I finally got Call and Message Continuity on S5E LTE working.
First you have to root your S5E ( Instructions here: https://forum.xda-developers.com/gal...t3926742/page2 )
Then download the APK for call and message continuity from internet, copy it to device.
Boot your tablet in "Rooted mode"(vol up and power)
Install the APK via "FX Explorer" with root addon enabled (click on open with and then select FX Root installer, will fail ). Then in FX Explorer copy the app to /system/app/ ( create a new folder, mine is called . CMC). Reboot phone into magisk mode again - it should be visible in settings now. However if you click to enable it you cant as you currently cant add your samsung account.
Reboot your tablet once more, this time in "normal" unrooted mode - add samsung account - done.
How to change files in the directory /system with Magisk
Note:
I tested the instructions below with Magisk 24. 25.0, and 25.2 on an ASUS Zenfone 8 running OmniROM (Android 12 ) .
The filesystem for /system is normally mounted read-only In Android 12 and it's difficult to change files in that filesystem.
One possible solution to change files in /system is to create a Magisk module for this task.
For testing if a Magisk Module would work like expected you can create a Dummy Magisk module . The steps to implement the Dummy Magisk Module are:
Install Magisk, enable root access for the shell in Magisk and enable access via adb (this can be done in the "Developer Options" in the system settings)
Next connect to the phone using the command
Code:
adb shell
and become root user
Code:
su -
Now create a sub directory in the directory
/data/adb/modules
e.g.
Code:
ASUS_I006D:/ # ls -ld /data/adb/modules/*
drwxrws--- 3 u0_a118 media_rw 3452 2022-05-30 12:12 /data/adb/modules/playstore
ASUS_I006D:/ #
Then copy the new files for the directory in /system to that directory (/data/adb/modules/<modulename>/ is equal here to the root dir, /, on the phone)
Example:
Code:
ASUS_I006D:/ # find /data/adb/modules/playstore
/data/adb/modules/playstore
/data/adb/modules/playstore/system
/data/adb/modules/playstore/system/etc
/data/adb/modules/playstore/system/etc/permissions
/data/adb/modules/playstore/system/etc/permissions/com.android.vending.xml
/data/adb/modules/playstore/system/priv-app
/data/adb/modules/playstore/system/priv-app/Phonesky
/data/adb/modules/playstore/system/priv-app/Phonesky/lib
/data/adb/modules/playstore/system/priv-app/Phonesky/lib/arm
/data/adb/modules/playstore/system/priv-app/Phonesky/lib/arm/libbrotli.so
/data/adb/modules/playstore/system/priv-app/Phonesky/lib/arm/libconscrypt_jni.so
/data/adb/modules/playstore/system/priv-app/Phonesky/lib/arm/libcronet.85.0.4181.5.so
/data/adb/modules/playstore/system/priv-app/Phonesky/lib/arm/libgame_sdk_device_info_jni.so
/data/adb/modules/playstore/system/priv-app/Phonesky/lib/arm/libphonesky_data_loader.so
/data/adb/modules/playstore/system/priv-app/Phonesky/lib/arm/libtensorflowlite_jni.so
/data/adb/modules/playstore/system/priv-app/Phonesky/Phonesky.apk
/data/adb/modules/playstore/system/priv-app/FakeStore
/data/adb/modules/playstore/system/priv-app/FakeStore/oat
/data/adb/modules/playstore/system/priv-app/FakeStore/oat/arm64
/data/adb/modules/playstore/system/priv-app/FakeStore/oat/arm64/FakeStore.odex
/data/adb/modules/playstore/system/priv-app/FakeStore/oat/arm64/FakeStore.vdex
/data/adb/modules/playstore/system/priv-app/FakeStore/FakeStore.apk
ASUS_I006D:/ #
Now reboot the phone.
After the reboot all files in /data/adb/modules/<modulename> will be mapped to /system by Magisk, e.g:
Code:
ASUS_I006D:/ # find /system/priv-app/Phonesky/
/system/priv-app/Phonesky/
/system/priv-app/Phonesky/lib
/system/priv-app/Phonesky/lib/arm
/system/priv-app/Phonesky/lib/arm/libbrotli.so
/system/priv-app/Phonesky/lib/arm/libconscrypt_jni.so
/system/priv-app/Phonesky/lib/arm/libcronet.85.0.4181.5.so
/system/priv-app/Phonesky/lib/arm/libgame_sdk_device_info_jni.so
/system/priv-app/Phonesky/lib/arm/libphonesky_data_loader.so
/system/priv-app/Phonesky/lib/arm/libtensorflowlite_jni.so
/system/priv-app/Phonesky/Phonesky.apk
ASUS_I006D:/ #
ASUS_I006D:/ # find /system/priv-app/FakeStore/
/system/priv-app/FakeStore/
/system/priv-app/FakeStore/oat
/system/priv-app/FakeStore/oat/arm64
/system/priv-app/FakeStore/oat/arm64/FakeStore.vdex
/system/priv-app/FakeStore/oat/arm64/FakeStore.odex
/system/priv-app/FakeStore/FakeStore.apk
ASUS_I006D:/ #
Because the mapping will be done while booting the phone it will also survive updating the OS on the phone to a new version as long as the user data is not deleted and Magisk is installed in the boot partition.
Notes:
Magisk "replaces" existing directories and files in /system with the files in that directory by using bind mounts.
You can not add additional files or directories to /system using this method -- it's only possible to add additional files and directories to the existing sub directories in /system.
This Magisk feature can also be used to make files in sub directories in /system writable -- see How to make files in system writable for detailed instructions.
This method can also be used to replace files in the directories /vendor, /product, or /system_ext:
from https://topjohnwu.github.io/Magisk/guides.html:
The system folder
All files you want to replace/inject should be placed in this folder. This folder will be recursively merged into the real /system; that is: existing files in the real /system will be replaced by the one in the module’s system, and new files in the module’s system will be added to the real /system.
If you place a file named .replace in any of the folders, instead of merging its contents, that folder will directly replace the one in the real system. This can be very handy for swapping out an entire folder.
If you want to replace files in /vendor, /product, or /system_ext, please place them under system/vendor, system/product, and system/system_ext respectively. Magisk will transparently handle whether these partitions are in a separate partition or not.
Click to expand...
Click to collapse
But this seems to work only to replace existing files in these directories.
This method to replace files in /system simulates a module in Magisk so if everything is okay I strongly recommend to create a "real" Magisk Module with the new files for /system.
Trouble Shooting
If something does not work check the Magisk log file in /cache :
/cache/magisk.log
History
Update 10.06.2022
added the infos about how to update files /vendor, /product, /system-ext
Update 12.06.2022
The Magisk Module to install the patched Playstore used in this example can be downloaded here
http://bnsmb.de/files/public/Android/PlayStore_for_MicroG.zip
see also this Message
https://forum.xda-developers.com/t/...h-a-patched-playstore-from-nanodroid.4456421/
Update 03.10.2022
The sentence about how to update files in /vendor, /product, /system-ext was missing here --fixed
Added a note about what can not be done using this method
Update 04.11.2022
Added the hint for the post to make files in /system writable
Doing some cleanup to make the instructions more clear
Update 18.01.2023
See How to change any file or directory using Magisk for another approach to change files on read-only mounted filesystems.
Can this way be used with the Product and other folders?, framework?
To remove apps?, make fake apk's?
NisseGurra said:
Can this way be used with the Product and other folders?, framework?
Click to expand...
Click to collapse
I just did a quick test and it seems that replacing files in other folders seems not to work
(but this was only a quick test without checking the documentation for Magisk ...)
To remove apps?, make fake apk's?
Click to expand...
Click to collapse
I don't think that you can remove files because Magisk uses bind mounts for replacing the files. But you can disable apps by creating empty files.
E.g. in my example in the previous post
/data/adb/modules/playstore/system/priv-app/FakeStore/FakeStore.apk
is an empty file to overwrite (and therfor disable) the file
/system/priv-app/FakeStore/FakeStore.apk.
That's neccessary because FakeStore.apk and Phonesky.apk use the same signature and that is not allowed in Android.
regards
Bernd
Tested to change a app: SamsungCalendar
Copied the files to /data/adb/modules/
Want to exchange the samsung calendar to an other calendar app that cant be installed due to name conflict.
Replace app?, seems no go
NisseGurra said:
Tested to change a app: SamsungCalendar
Copied the files to /data/adb/modules/
Want to exchange the samsung calendar to an other calendar app that cant be installed due to name conflict.
Replace app?, seems no go
Click to expand...
Click to collapse
Post an "ls -l" for the directory with the app you want to replace and the output of
ls -lr /data/adb/
The file structure in /data/adb/module must match the file structure in / , e.g. to replace the file
/system/priv-app/<appname>/<app.apk>
the file to replace that app must be
/data/adb/modules/<modulename>/system/priv-app/<appname>/<app.apk>
Module Name can be any name .
regards
Bernd
I have try this again, seems magisk creates an file connected to the replaced file.
How do i make these files?
I have some 200 apps in system that i like to disable. Would an "fake" apk disable these apps?
Tested calendar app again, it replaces apk but as its in system/app it can not start the "calendar"
Hi,
Do you think that in this module I can switch mbm system file from
vendor/rfs/msm/mpss/readonly/vendor/mbm/mcfg_sw/mbn_sw.txt
kubans2301 said:
Hi,
Do you think that in this module I can switch mbm system file from
vendor/rfs/msm/mpss/readonly/vendor/mbm/mcfg_sw/mbn_sw.txt
Click to expand...
Click to collapse
Hi
The file does not exist on my phone:
Code:
ASUS_I006D:/ # ls /vendor/rfs/msm/mpss/readonly/vendor/
firmware
ASUS_I006D:/ #
So I will create it now:
Code:
ASUS_I006D:/data/adb/modules/fmradio # mkdir -p system/vendor/rfs/msm/mpss/readonly/vendor/mbm/mcfg_sw
ASUS_I006D:/data/adb/modules/fmradio #
ASUS_I006D:/data/adb/modules/fmradio # echo "# Test file" > system/vendor/rfs/msm/mpss/readonly/vendor/mbm/mcfg_sw/mbn_sw.txt
ASUS_I006D:/data/adb/modules/fmradio #
ASUS_I006D:/data/adb/modules/fmradio # cat system/vendor/rfs/msm/mpss/readonly/vendor/mbm/mcfg_sw/mbn_sw.txt
# Test file
ASUS_I006D:/data/adb/modules/fmradio #
and reboot
Code:
ASUS_I006D:/data/adb/modules/fmradio # reboot
after the reboot the file is thre:
Code:
ASUS_I006D:/data/adb/modules/fmradio # cat /vendor/rfs/msm/mpss/readonly/vendor/mbm/mcfg_sw/mbn_sw.txt
# Test file
ASUS_I006D:/data/adb/modules/fmradio #
ASUS_I006D:/data/adb/modules/fmradio # echo "Test 1234" >>./system/vendor/rfs/msm/mpss/readonly/vendor/mbm/mcfg_sw/mbn_sw.txt
ASUS_I006D:/data/adb/modules/fmradio #
ASUS_I006D:/data/adb/modules/fmradio #
ASUS_I006D:/data/adb/modules/fmradio # cat /vendor/rfs/msm/mpss/readonly/vendor/mbm/mcfg_sw/mbn_sw.txt
# Test file
Test 1234
ASUS_I006D:/data/adb/modules/fmradio #
So it should also work to "overwrite" an existing file in that directory.
regards
Bernd
regards
Bernd
NisseGurra said:
I have try this again, seems magisk creates an file connected to the replaced file.
How do i make these files?
I have some 200 apps in system that i like to disable. Would an "fake" apk disable these apps?
Tested calendar app again, it replaces apk but as its in system/app it can not start the "calendar"
Click to expand...
Click to collapse
HI
I missed that post -- what did you do exactly and what did not work?
regards
Bernd
just make a Replace list in customize.sh in magisk zip is fine
Thank you so much. It works perfectly on my Xiaomi mi 11 on miui 14 (android 13). It is easy and very fast way to change files in subfolders in system when it mounted read-only.
This is great and the best thing is that if something doesnt work and I get a bootloop I can always just boot into safe mode and remove the module
So this replaces files or just creates some links?
For instance if I make a module to replace Samsung My Files with a custom app, will this be reversible, meaning that if I delete my module I get original My Files app back?
veso266 said:
This is great and the best thing is that if something doesnt work and I get a bootloop I can always just boot into safe mode and remove the module
So this replaces files or just creates some links?
For instance if I make a module to replace Samsung My Files with a custom app, will this be reversible, meaning that if I delete my module I get original My Files app back?
Click to expand...
Click to collapse
This is great and the best thing is that if something doesnt work and I get a bootloop I can always just boot into safe mode and remove the module
Click to expand...
Click to collapse
correct (and if booting to save mode does not work anymore you can boot from the recovery image and fix the problem)
So this replaces files or just creates some links
Click to expand...
Click to collapse
/system is mounted read-only and neither you nor Magisk can replace files on a read-only mounted filesystem . Magisk creates bind mounts for the files and directories to replace.
Bind mounts only exist in memory and will be removed by a reboot.
For instance if I make a module to replace Samsung My Files with a custom app, will this be reversible, meaning that if I delete my module I get original My Files app back?
Click to expand...
Click to collapse
yes, just deactivate or deinstall the Magisk Module. This can be done either in the Magisk App, in an adb shell, or, if the phone does not boot anymore, from within a booted recovery image
regards
Bernd
bnsmb said:
correct (and if booting to save mode does not work anymore you can boot from the recovery image and fix the problem)
/system is mounted read-only and neither you nor Magisk can replace files on a read-only mounted filesystem . Magisk creates bind mounts for the files and directories to replace.
Bind mounts only exist in memory and will be removed by a reboot.
yes, just deactivate or deinstall the Magisk Module. This can be done either in the Magisk App, in an adb shell, or, if the phone does not boot anymore, from within a booted recovery image
regards
Bernd
Click to expand...
Click to collapse
Thanks, let me first tell you I am using Android 10 (no need to upgrade, and I don't want some obscure api to be removed, which I found out about when I need it)
I was able to make a small module that adds a priv-app, a permissions and a library, and it works great
No the onlything I need to add is a system service
So I need to replace framework.jar (I also have EdXposed installed through Riru and I dont want to break it)
Now I have Samsung Galaxy S10+ (SM-G975F) which doesnt have this service, but korean version of it (SM-G975N) has
So for the first test, I just wanted to transplant framework.jar (using the same android version of course) from SM-G975N to my SM-G975F
this seams easier to do then patch my framework.jar, because I read that system service also needs to be signed, and I don't know how to do that yet
I hope replacing framework.jar file will be enought (since I also read system services are located elsewhere)
The service I need to add is called: FMRadioService.java (and is located under com\android\server\ (if you decompile framework.jar)
Now I need to figure out how to recover, if something goes wrong (because something alawys goes wrong, I would like to be prepared)
So how to enter safe mode and disable my module?
And you said that if this doesnt work I can boot from recovery image (what image? is stock recovery allright? (I don't have TWRP yet (I will install it, once I figure out how), and I explained the reasons in this thread: https://forum.xda-developers.com/t/...-app-after-you-have-root-with-magisk.4564363/ )
Thanks
veso266 said:
Thanks, let me first tell you I am using Android 10 (no need to upgrade, and I don't want some obscure api to be removed, which I found out about when I need it)
I was able to make a small module that adds a priv-app, a permissions and a library, and it works great
No the onlything I need to add is a system service
So I need to replace framework.jar
Now I have Samsung Galaxy S10+ (SM-G975F) which doesnt have this service, but korean version of it (SM-G975N) has
So for the first test, I just wanted to transplant framework.jar (using the same android version of course) from SM-G975N to my SM-G975F
this seams easier to do then patch my framework.jar, because I read that system service also needs to be signed, and I don't know how to do that yet
I hope replacing framework.jar file will be enought (since I also read system services are located elsewhere)
The service I need to add is called: FMRadioService.java (and is located under com\android\server\ (if you decompile framework.jar)
Now I need to figure out how to recover, if something goes wrong (because something alawys goes wrong, I would like to be prepared)
So how to enter safe mode and disable my module?
And you said that if this doesnt work I can boot from recovery image (what image? is stock recovery allright? (I don't have TWRP yet (I will install it, once I figure out how), and I explained the reasons in this thread: https://forum.xda-developers.com/t/...-app-after-you-have-root-with-magisk.4564363/ )
Thanks
Click to expand...
Click to collapse
Hi
I don't have a Samsung phone and as far as I know Samsung uses other tools then other vendors for accessing the phone ...
Anyway, these are the instructions to do this on an ASUS Zenfone 8 (using fastboot and adb):
To enter the safe mode just press the power button; wait until the dialog with restart, power-off, etc occurs. Klick on the restart button in that dialog without releasing the power button of the phone. A new dialog to confirm the Save mode should appear.
To boot the ASUS Zenfone 8 from the recovery image boot the phone into the bootloader
adb reboot bootloader
and then issue on the PC
sudo fastboot boot <recovery_image>
<recovery_image> can either be the TWRP image for the phone or the recovery image for the LineageOS (or any other recovery with enabled access via adb).
adb is enabled by default in the TWRP image; in the LineageOS access via adb must be enabled via a menu entry after booting from the image.
AFAIK the stock recovery from Android does not support access via adb.
The phone can also be booted from the recovery installed on the phone via
adb reboot recovery
if the installed recovery supports access via adb.
And, for the records:
In most cases where the OS is loaded after booting the phone but seems to hang, access via adb will already work.
The Magisk Modules are stored in sub directories the directory /data/adb/modules/ , e.g.:
Bash:
ASUS_I006D:/ # ls -l /data/adb/modules/
total 21
drwxr-xr-x 3 root root 3452 1970-01-29 22:32 MiXplorer
drwxr-xr-x 4 root root 3452 1970-01-29 22:32 PlayStore_for_MicroG
drwxr-xr-x 5 root root 3452 1970-01-29 22:32 addbin
drwxr-xr-x 3 root root 3452 1970-01-29 22:32 bootctl-binary
drwxr-xr-x 5 root root 3452 1970-02-01 14:10 btop++
drwxrwxrwx 3 root root 3452 1970-01-29 22:32 nano-ndk
drwxr-xr-x 3 root root 3452 1970-01-29 22:32 ssh
ASUS_I006D:/ #
To disable a Magisk module after the next reboot create the file
/data/adb/modules/<modulename>/disable
To force Magisk to remove a Magisk module after the next reboot create the file
/data/adb/modules/<modulename>/remove
(see also here: https://forum.xda-developers.com/t/some-hints-for-using-magisk-on-android-phones.4471857/)
Note that Magisk will disable all Magisk modules automatically if the phone is booted into Safe mode.
regards
Bernd
I have a SM-G781U1 (Cricket CSC: AIO) rooted and unlocked bootloader. Currently running the following ROM (Android 12 One UI 4.1)
G781USQU7FVC2_BIT1_SAFE.7z (https://drive.google.com/file/d/1BNF6CNhT2JkY5rAdsMIFeGIUaxfoRKff/view?usp=sharing)
I am trying to enable native Call Recording and so far have been unable to get it working on android 12. I did have it working on Android 10.
I have pulled the following file /optics/configs/carriers/single/AIO/conf/system/cscfeature.xml and decoded it using https://github.com/fei-ke/OmcTextDecoder
I then added the following code to the file
Code:
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowedByMenu</CscFeature_VoiceCall_ConfigRecording>
After modding the CSC I then re encoded the file and pushed back to the phone /optics/configs/carriers/single/AIO/conf/system/cscfeature.xml
I tried adding just RecordingAllowed but after a reboot have been unable to get it working. I verifed the phone is using AIO csc and
When I had both tags and rebooted I got a notice there was a new setting but after opening settings there was no call recording option but Settings still showed there was a new option available (settings has a red N icon)
I looked around the filesystem and the optics folder seems to be the location for my CSC. but after replacing the CSC with my modded CSC and rebooting calls are not being recorded.
I also noticed /optics/configs/carriers/single/AIO/conf/omc.info shows
Code:
<customerEdition>ED0003</customerEdition>
while the CSC shows ED0009, not sure if that makes a difference but changing it to ED0009 did not make a difference.
Below is my current cscfeatures.xml file decoded
Spoiler: cscfeature.xml
Code:
<?xml version='1.0' encoding='utf-8'?>
<SamsungMobileFeature>
<Version>ED00009</Version>
<Country>USA</Country>
<CountryISO>US</CountryISO>
<SalesCode>AIO</SalesCode>
<FeatureSet>
<CscFeature_Audio_ConfigBootSoundDelay>2800000</CscFeature_Audio_ConfigBootSoundDelay>
<CscFeature_Audio_SupportSafeMediaVolumeDialog>TRUE</CscFeature_Audio_SupportSafeMediaVolumeDialog>
<CscFeature_Audio_SupportSyncBootSound>TRUE</CscFeature_Audio_SupportSyncBootSound>
<CscFeature_BT_ConfigNetAccessTypeForPANNAP>GSM</CscFeature_BT_ConfigNetAccessTypeForPANNAP>
<CscFeature_BT_DisableNAP>TRUE</CscFeature_BT_DisableNAP>
<CscFeature_BT_DisableSAP>TRUE</CscFeature_BT_DisableSAP>
<CscFeature_Calendar_ConfigDefRingtoneName>Cricket Bottle</CscFeature_Calendar_ConfigDefRingtoneName>
<CscFeature_Calendar_EnableShiftedWeekNumber>TRUE</CscFeature_Calendar_EnableShiftedWeekNumber>
<CscFeature_Calendar_SetColorOfDays>XXXXXXX</CscFeature_Calendar_SetColorOfDays>
<CscFeature_Camera_CameraFlicker>60hz</CscFeature_Camera_CameraFlicker>
<CscFeature_Camera_ShutterSoundMenu>TRUE</CscFeature_Camera_ShutterSoundMenu>
<CscFeature_Common_Config5GevoMobileType>2</CscFeature_Common_Config5GevoMobileType>
<CscFeature_Common_ConfigAllowedPackagesDuringDataSaving>com.samsung.android.smartcallprovider,com.sec.android.app.cmas,com.dti.cricket</CscFeature_Common_ConfigAllowedPackagesDuringDataSaving>
<CscFeature_Common_ConfigEmergencyModePackages>com.sec.android.app.cmas,com.sec.vowifispg,com.sec.vsimservice,com.sec.vsimmanager,com.sec.vsim.ericssonnsds.webapp,com.samsung.android.nsdsvowifi,com.sec.unifiedwfc</CscFeature_Common_ConfigEmergencyModePackages>
<CscFeature_Common_ConfigPco>COMMON</CscFeature_Common_ConfigPco>
<CscFeature_Common_ConfigSvcProviderForUnknownNumber>off,off,off</CscFeature_Common_ConfigSvcProviderForUnknownNumber>
<CscFeature_Common_SupportCiq>TRUE</CscFeature_Common_SupportCiq>
<CscFeature_Common_SupportMinimizedSip>TRUE</CscFeature_Common_SupportMinimizedSip>
<CscFeature_Contact_ANRConfig>0</CscFeature_Contact_ANRConfig>
<CscFeature_Contact_ConfigDisplaySimIcon>disable</CscFeature_Contact_ConfigDisplaySimIcon>
<CscFeature_Contact_ConfigDtmfPause>3</CscFeature_Contact_ConfigDtmfPause>
<CscFeature_Contact_ConfigDuoVideoCall>ViLTE, nopopup,</CscFeature_Contact_ConfigDuoVideoCall>
<CscFeature_Contact_ConfigImsOpStyle>AIO</CscFeature_Contact_ConfigImsOpStyle>
<CscFeature_Contact_ConfigOpStyleVariation>ATT</CscFeature_Contact_ConfigOpStyleVariation>
<CscFeature_Contact_SupportDuoVideoCall>TRUE</CscFeature_Contact_SupportDuoVideoCall>
<CscFeature_DeviceSearch_AlwaysShowSipWhenSwipeLaunched>FALSE</CscFeature_DeviceSearch_AlwaysShowSipWhenSwipeLaunched>
<CscFeature_DeviceSearch_SupportEnterpriseSearchProviderList>branch;</CscFeature_DeviceSearch_SupportEnterpriseSearchProviderList>
<CscFeature_FMRadio_DisableMenuInternetRadio>TRUE</CscFeature_FMRadio_DisableMenuInternetRadio>
<CscFeature_Framework_2ndScreenConfig>ruler_default_unit,inch;</CscFeature_Framework_2ndScreenConfig>
<CscFeature_Framework_DisableDoubleTapTextSelection>TRUE</CscFeature_Framework_DisableDoubleTapTextSelection>
<CscFeature_Framework_DisableEdgeHandlerHaptic>TRUE</CscFeature_Framework_DisableEdgeHandlerHaptic>
<CscFeature_GMS_DisableSetupWizard>TRUE</CscFeature_GMS_DisableSetupWizard>
<CscFeature_GMS_SetClientIDBaseAm>android-cricket</CscFeature_GMS_SetClientIDBaseAm>
<CscFeature_GMS_SetClientIDBaseMs>android-cricket-us-revc</CscFeature_GMS_SetClientIDBaseMs>
<CscFeature_GMS_SetFrpPersistent>TRUE</CscFeature_GMS_SetFrpPersistent>
<CscFeature_IMS_ConfigMdmnType></CscFeature_IMS_ConfigMdmnType>
<CscFeature_LockScreen_ConfigCarrierSecurityPolicy>FactoryResetWithoutUI;DisplayUnlockToast</CscFeature_LockScreen_ConfigCarrierSecurityPolicy>
<CscFeature_LockScreen_ConfigClockDisplayPolicy>HideTextOfRoamingClock</CscFeature_LockScreen_ConfigClockDisplayPolicy>
<CscFeature_LockScreen_SupportToastSimUnlockSuccess>TRUE</CscFeature_LockScreen_SupportToastSimUnlockSuccess>
<CscFeature_Message_DisableMenuWapPushServiceLoading>TRUE</CscFeature_Message_DisableMenuWapPushServiceLoading>
<CscFeature_Message_DisableMmsSubject>TRUE</CscFeature_Message_DisableMmsSubject>
<CscFeature_Message_DisableSaveClassZeroMessage>TRUE</CscFeature_Message_DisableSaveClassZeroMessage>
<CscFeature_Message_EnableCpm>TRUE</CscFeature_Message_EnableCpm>
<CscFeature_Message_EnableReplyAll>TRUE</CscFeature_Message_EnableReplyAll>
<CscFeature_Message_ImageResizeQualityFactorWhenAttach>high</CscFeature_Message_ImageResizeQualityFactorWhenAttach>
<CscFeature_Message_MmsModeCaptureVideoBitRate>0</CscFeature_Message_MmsModeCaptureVideoBitRate>
<CscFeature_Message_MmsModeCaptureVideoMaxDuration>0</CscFeature_Message_MmsModeCaptureVideoMaxDuration>
<CscFeature_Message_MmsModeCaptureVideoMaxSize>1018880</CscFeature_Message_MmsModeCaptureVideoMaxSize>
<CscFeature_Message_ReplaceLabel4RetreivedMsg>TRUE</CscFeature_Message_ReplaceLabel4RetreivedMsg>
<CscFeature_Message_SupportSuggestedCategory>TRUE</CscFeature_Message_SupportSuggestedCategory>
<CscFeature_NFC_ConfigAdvancedSettings>Disable</CscFeature_NFC_ConfigAdvancedSettings>
<CscFeature_NFC_ConfigOpSigningAccessKey>USA_COMM</CscFeature_NFC_ConfigOpSigningAccessKey>
<CscFeature_NFC_DefStatus>ON</CscFeature_NFC_DefStatus>
<CscFeature_RIL_ConfigNetworkTypeCapability>ATT-AIO-GSM-USA</CscFeature_RIL_ConfigNetworkTypeCapability>
<CscFeature_RIL_DisableMobileDataOnly>TRUE</CscFeature_RIL_DisableMobileDataOnly>
<CscFeature_RIL_EmergencyOnlyWithNoSim>TRUE</CscFeature_RIL_EmergencyOnlyWithNoSim>
<CscFeature_RIL_NotifyInvalidSIM>TRUE</CscFeature_RIL_NotifyInvalidSIM>
<CscFeature_RIL_RemoveToastDuringBipOperation>TRUE</CscFeature_RIL_RemoveToastDuringBipOperation>
<CscFeature_RIL_RemoveToastDuringStkRefresh>TRUE</CscFeature_RIL_RemoveToastDuringStkRefresh>
<CscFeature_RIL_SIMPlmnAction>TRUE</CscFeature_RIL_SIMPlmnAction>
<CscFeature_RIL_SupportEsim>FALSE</CscFeature_RIL_SupportEsim>
<CscFeature_Setting_ConfigForbidAppDisableButton>com.android.contacts</CscFeature_Setting_ConfigForbidAppDisableButton>
<CscFeature_Setting_ConfigMobileHotspotProvisionApp>com.samsung.unifiedtp,com.samsung.unifiedtp.ui.TetheringProvisionActivity</CscFeature_Setting_ConfigMobileHotspotProvisionApp>
<CscFeature_Setting_ConfigTouchSensetivity>ON</CscFeature_Setting_ConfigTouchSensetivity>
<CscFeature_Setting_ConfigTypeHelp>1</CscFeature_Setting_ConfigTypeHelp>
<CscFeature_Setting_DefDialingKeypadTone>OFF</CscFeature_Setting_DefDialingKeypadTone>
<CscFeature_Setting_EnableFactoryResetPasswordWhenNoSIM>TRUE</CscFeature_Setting_EnableFactoryResetPasswordWhenNoSIM>
<CscFeature_Setting_SupportHAC>TRUE</CscFeature_Setting_SupportHAC>
<CscFeature_Setting_SupportIccId>TRUE</CscFeature_Setting_SupportIccId>
<CscFeature_Setting_SupportMenuSmartTutor>FALSE</CscFeature_Setting_SupportMenuSmartTutor>
<CscFeature_Settings_ConfigDefinedApnProtocol>IPV4V6,IPV4V6</CscFeature_Settings_ConfigDefinedApnProtocol>
<CscFeature_Sip_ConfigOpBranding>ATT</CscFeature_Sip_ConfigOpBranding>
<CscFeature_Sip_DisableToolbarAppList>youtube,spotify</CscFeature_Sip_DisableToolbarAppList>
<CscFeature_Sip_SupportAddExtraWarningMsgForRts>TRUE</CscFeature_Sip_SupportAddExtraWarningMsgForRts>
<CscFeature_SmartSwitch_ConfigHeadUpNotification>never</CscFeature_SmartSwitch_ConfigHeadUpNotification>
<CscFeature_SyncML_ConfigOmcDomainRegion>us</CscFeature_SyncML_ConfigOmcDomainRegion>
<CscFeature_SystemUI_BlockDoubleTapNotiOnLockScreen>TRUE</CscFeature_SystemUI_BlockDoubleTapNotiOnLockScreen>
<CscFeature_SystemUI_ConfigDefQuickSettingItem>Wifi,WifiCalling,SoundMode,Bluetooth,RotationLock,AirplaneMode,Flashlight,Hotspot,BatteryMode,Location,WindowsLink,ScreenRecorder,DesktopMode,AllShareCast,NearbyShare,BlueLightFilter,NightMode,Dnd</CscFeature_SystemUI_ConfigDefQuickSettingItem>
<CscFeature_SystemUI_ConfigDefStatusShowBatteryPercent>ON</CscFeature_SystemUI_ConfigDefStatusShowBatteryPercent>
<CscFeature_SystemUI_ConfigMaxRssiLevel>5</CscFeature_SystemUI_ConfigMaxRssiLevel>
<CscFeature_SystemUI_ConfigOpBrandingForIndicatorIcon>AIO</CscFeature_SystemUI_ConfigOpBrandingForIndicatorIcon>
<CscFeature_SystemUI_ConfigOpBrandingLTEWideBandIcon>NONE</CscFeature_SystemUI_ConfigOpBrandingLTEWideBandIcon>
<CscFeature_SystemUI_ConfigQuickSettingPopup>AIO</CscFeature_SystemUI_ConfigQuickSettingPopup>
<CscFeature_SystemUI_ConfigRemoveQuickSettingItem>Sync</CscFeature_SystemUI_ConfigRemoveQuickSettingItem>
<CscFeature_SystemUI_ConfigRuleForShowPlmn>LcdOn_3sec</CscFeature_SystemUI_ConfigRuleForShowPlmn>
<CscFeature_VT_ConfigBearer>-CSVT</CscFeature_VT_ConfigBearer>
<CscFeature_VT_ConfigCapability>three_widget</CscFeature_VT_ConfigCapability>
<CscFeature_VT_ConfigOpStyleForDependency>AIO_PSVT</CscFeature_VT_ConfigOpStyleForDependency>
<CscFeature_VT_ConfigOpStyleForSetting>removevtsetting</CscFeature_VT_ConfigOpStyleForSetting>
<CscFeature_VT_SupportAddCall>TRUE</CscFeature_VT_SupportAddCall>
<CscFeature_Video_ConfigOpStyleForSubTitle>USA</CscFeature_Video_ConfigOpStyleForSubTitle>
<CscFeature_VoiceCall_ConfigOpStyleForCallerId>ECID</CscFeature_VoiceCall_ConfigOpStyleForCallerId>
<CscFeature_VoiceCall_ConfigOpStyleForHdIcon>ATT_WIFI,NOHD</CscFeature_VoiceCall_ConfigOpStyleForHdIcon>
<CscFeature_VoiceCall_ConfigOpStyleForImsFunction>wfc_capa_noti_mgr</CscFeature_VoiceCall_ConfigOpStyleForImsFunction>
<CscFeature_VoiceCall_ConfigOpStyleForMvno>AIO_ATT_MVNO</CscFeature_VoiceCall_ConfigOpStyleForMvno>
<CscFeature_VoiceCall_ConfigOpStyleForVolte>AIO_VOLTE,USA_VOLTE,support_merge_option_waitingcall_dialog</CscFeature_VoiceCall_ConfigOpStyleForVolte>
<CscFeature_VoiceCall_ConfigOptStyleForCallBarring>RemoveAll</CscFeature_VoiceCall_ConfigOptStyleForCallBarring>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_VoiceCall_DisableCallTransfer>FALSE</CscFeature_VoiceCall_DisableCallTransfer>
<CscFeature_VoiceCall_DisablePopupMsgWhenDeactivatingCallForwarding>TRUE</CscFeature_VoiceCall_DisablePopupMsgWhenDeactivatingCallForwarding>
<CscFeature_VoiceCall_EnableBeepVibration4UssdAlert>TRUE</CscFeature_VoiceCall_EnableBeepVibration4UssdAlert>
<CscFeature_VoiceCall_SupportHoldUiForVolte>TRUE</CscFeature_VoiceCall_SupportHoldUiForVolte>
<CscFeature_VoiceCall_SupportMenuForVoicePrivacy>TRUE</CscFeature_VoiceCall_SupportMenuForVoicePrivacy>
<CscFeature_VoiceCall_SupportNotiForUssd>TRUE</CscFeature_VoiceCall_SupportNotiForUssd>
<CscFeature_VoiceCall_SupportPopupForDataOff>TRUE</CscFeature_VoiceCall_SupportPopupForDataOff>
<CscFeature_VoiceCall_SupportRTT>TRUE</CscFeature_VoiceCall_SupportRTT>
<CscFeature_VoiceCall_SupportRTTConferenceMerge>TRUE</CscFeature_VoiceCall_SupportRTTConferenceMerge>
<CscFeature_VoiceCall_SupportTTY>TRUE</CscFeature_VoiceCall_SupportTTY>
<CscFeature_VoiceCall_SupportVolteHoldTone>NOT</CscFeature_VoiceCall_SupportVolteHoldTone>
<CscFeature_Weather_ConfigCpType>TWC</CscFeature_Weather_ConfigCpType>
<CscFeature_Weather_ConfigDefRefreshInterval>1</CscFeature_Weather_ConfigDefRefreshInterval>
<CscFeature_Weather_ConfigDefTempUnit>0</CscFeature_Weather_ConfigDefTempUnit>
<CscFeature_Weather_SupportPromptForDataUsage>TRUE</CscFeature_Weather_SupportPromptForDataUsage>
<CscFeature_Weather_SupportPromptForLocationAccess>TRUE</CscFeature_Weather_SupportPromptForLocationAccess>
<CscFeature_Web_ConfigDefaultBrowser>chrome</CscFeature_Web_ConfigDefaultBrowser>
<CscFeature_Web_CustomizeErrorPage>ATT</CscFeature_Web_CustomizeErrorPage>
<CscFeature_Web_SetHomepageURL>https://home.cricketwireless.com</CscFeature_Web_SetHomepageURL>
<CscFeature_Web_SetUserAgent>AIO</CscFeature_Web_SetUserAgent>
<CscFeature_Wifi_CaptivePortalException>AIO</CscFeature_Wifi_CaptivePortalException>
<CscFeature_Wifi_ConfigOpBranding>AIO</CscFeature_Wifi_ConfigOpBranding>
<CscFeature_Wifi_DisableMWIPS>TRUE</CscFeature_Wifi_DisableMWIPS>
<CscFeature_Wifi_Support5GAntShare>TRUE</CscFeature_Wifi_Support5GAntShare>
<CscFeature_Wifi_SupportNotificationMenu>TRUE</CscFeature_Wifi_SupportNotificationMenu>
</FeatureSet>
</SamsungMobileFeature>
Hello,
were you able to make progress on this?
I can't do it either, I have a galaxy s10+ with Android 12 (I had no problem with android10)
Thanks