I have the N920I on AT&T and desperately want WiFi Calling to work because it's an essential feature for me. I bought the S7 Edge and hate it, but before I sell it I'm trying to get WiFi calling ported over. Here is what I've accomplished so far.
Copied over apks of all apps known to be related to wifi calling
Changed CSC to ATT
vsimservice crashes repeatedly, rendering the phone unusable
adb logcat reveals
Code:
Didn't find class "com.sec.internal.vsim.VSimServiceApp" on path: DexPathList[[zip file "/system/framework/imsmanager.jar", zip file "/system/framework/secimshttpclient.jar", zip file "/system/framework/vsimmanager.jar", zip file "/system/app/vsimservice/vsimservice.apk"],nativeLibraryDirectories=[/system/app/vsimservice/lib/arm64, /system/app/vsimservice/vsimservice.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64, /system/lib64, /vendor/lib64
Does anyone have a clue how I can solve this? It seems to be the last remaining piece of the puzzle.
Related
Hi guys,
I've got a customer who is having a problem on my app which has to read wpa_supplicant.conf. Normally this file is located at /data/misc/wifi/wpa_supplicant.conf and requires root to read.
Anyways, according to the errors he's getting and based on his own exploration, his wpa_supplicant.conf file is not located there. I'm not sure which ROM he has (am waiting for a reply to that question now), but does anyone know if this file is normally located in /data/misc/wifi ?
Thanks,
James
Its not there on Darky 7.0 based on latest JPY firmware.
Search in progress ;]
/etc/wifi/wpa_supplicant.conf
and symlink
/system/etc/wifi/wpa_supplicant.conf
Thanks for the tip. On my customer's phone that file is just a template and not actually storing networks. I'll poke around in that ROM though. Thanks again.
Sent from my Nexus One using XDA App
Stock Froyo location is etc/wifi
jje
Looking at /system/etc/wifi/wifi.conf on Darky 7.0 I see the following
Code:
FIRMWARE_LOADER=wlan_loader
DRIVER_PROP_NAME=wlan.driver.status
SUPPLICANT_NAME=wpa_supplicant
SUPP_PROP_NAME=init.svc.wpa_supplicant
MODULE_FILE=/proc/modules
IFACE_DIR=/data/misc/wifi
DRIVER_MODULE_NAME=dhd
DRIVER_MODULE_TAG=dhd
FIRMWARE_LOADER=
[b]SUPP_CONFIG_TEMPLATE=/system/etc/wifi/wpa_supplicant.conf[/b]
SUPP_CONFIG_FILE=/data/wifi/bcm_supp.conf
DRIVER_MODULE_PATH=/lib/modules/dhd.ko
MFGDRV_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_mfg.bin nvram_path=/system/etc/wifi/nvram_mfg.txt
DRV_AP_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_aps.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=200 dhd_poll=1
DRIVER_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1
DRIVER_APS_FIRMWARE_NAME=bcm4329_aps.bin
DRIVER_STA_FIRMWARE_NAME=bcm4329_sta.bin
INTERFACENAME=eth0
WAPI_SUPPORT=false
[b]SUPP_CONF_FILEPATH=/data/misc/wifi/[/b]
SUPP_WAPI_AS_CERT_FILE_PATH=/data/misc/wifi/cert/as/
SUPP_WAPI_USER_CERT_FILE_PATH=/data/misc/wifi/cert/user/
SUPPLICANT_STATUS=wlan.supplicant.status
This tells me I would expect the conf file to be in /data/misc/wifi and the template to be in /system/etc/wifi.
Argh, this is very frustrating.
Code:
SUPP_CONFIG_TEMPLATE=/system/etc/wifi/wpa_supplicant.conf
is what you are after.
-(e)
Sweetlime, would you mind elaborating?
Do you see your networks in that file on your device?
On every device and ROM that I've been able to inspect that file is just the template and contains no specific network information.
Sorry I am an idiot I copied the wrong line, that should have read:
Code:
SUPP_CONFIG_FILE=/data/wifi/bcm_supp.conf
[null]
So I don't post much so bear with me.
I was looking for a solution to enable the hotspot on my rooted AT&T Galaxy S6. I ran across the following post that requires flash fire and a file that appears to modify the framework-res.apk.
http://forum.xda-developers.com/att-galaxy-s6/development/mod-tether-hack-oe2-build-t3115789
I am new to changing my android OS so I wanted a solution that instead modified the Tethering App itself.
I found the following post for enabling wifi tethering/hotspot on AT&T lollipop devices by changing the tetheringprovision.apk file.
http://forum.xda-developers.com/note-3-att/general/how-to-enable-wifi-hotspot-rooted-t3131646
I then found information on enabling tethering for an S6 on the T-mobile network that included additional steps. Like deleteing the arm64 folder (I just renamed mine) and refreshing the APN (I suspect this is done because they also change the customer.xml file that builds the default APN).
http://forum.xda-developers.com/tmobile-galaxy-s6/development/mod-enable-native-tether-t3078551
So I performed the following actions and was able to enable wifi hostspot on my AT&T Galaxy S6 with an unlimited data plan
Download the tetheringprovision.apk file on a rooted S6
Use a file explorer program like ES File Explorer rename the original tetheringprovision.apk to tetheringprovision.apk1
to copy the file from the download folder to the folder /system/app/TetheringProvision (in ES File Explorer you may need to enable root explorer to allow the copy)
Modify the permissions of the file (Used ES File Explorer under properties of the file)
Renamed the arm64 folder to arm64.old
Rebuilt the APN (Probably did not need to do this step)
Restarted the phone
If this works for you let me know.
PS: Does anyone know how to avoid detection?
Hello guys, I'm here to show you how to fix it without repeatedly turning it on and off. (I provided the stock bluetooth for you guys, that don't have it)
This is only for LTE jem, sorry for any convenience. (For bluetooth.)
1. Download this https://www.dropbox.com/s/29pw4nm27pgl8aj/Bluetooth fix.rar?dl=0
2. Extract it.
3. Replace /System/etc/Bluetooth/bcm2076_20mhz.hcd with BCM2076_26MHZ.HCD
4. Replace /System/vendor/firmware/bcm2076_20mhz.hcd with bcm2076_20mhz.hcd (The one I provided for you)
Then tada! Bluetooth works, you can only connect to compatible devices it seems but bluetooth finally works.
Now onto how to fix amazon jem not being recognized, on your pc/laptop.
I'm going to be honest here, this will be very short lol.
So anyways, go to this link https://windows10skill.com/kindle-fire-not-recognized-on-windows-10/#2 and follow the steps provided. Method 2 helped me, so try that first if you want. (This can work on windows 7 too, I forgot where I found it at but you can try following it still.)
That's all I have, for now. I hope all of you guys get everything fixed! Please let me know if this was helpful for you, I would appreciate it.
This RAR file won't open
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
bapi28 said:
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
Click to expand...
Click to collapse
Oh my god, I'm so sorry I forgot to mention this is only for lte devices. Sorry!
Understood step 4. But on step 3 when it states replace a file with a file having a different name, does that mean 1) delete original file and put new file in that folder, or 2) rename new file to existing files name and copy over top of existing file replacing it?
Ok, answered my own question and figured it out.
I did not have such a file in the /System/etc/Bluetooth folder.
I renamed the 26mhz file to 20mhz and replaced (overwrote) the file in the /System/vendor/firmware folder.
It is working great finally after issues for the past few years. Awesome. Thanks.
Hi there, I was wondering how to enable Native Call recorder in Android?
I have SIM CSC, this FW: https://www.sammobile.com/samsung/g...e/SM-G975F/SIM/download/G975FXXU4CTC9/329653/
and it doesn't allow native call recording
now I heard that if you install THL CSC rom (change CSC to THL), it will be enabled
but I don't want to change CSC, I have root and I don't want to reinstall diferent ROM, I would like to modify my SIM CSC to enable call recording?
Thanks for Anwsering and Best Regards
well I did it, I have native call recorder on my SIM CSC on my GalaxyS10+ Android 10 now I will tell you how its done
1. Find your cscfeature.xml file (this file hold many thing and also holds the option to enable call recorder
on my Galaxy S10+ Android 10 its in:
/system/product/omc/{COUNTRY_CODE}/conf/cscfeature.xml
Click to expand...
Click to collapse
where country code is your active CSC (mine is SIM) so my file would be in:
/system/product/omc/SIM/conf/cscfeature.xml
Click to expand...
Click to collapse
then if you have root copy this file to your computer, its encrypted so you will have to decrypt it for this you will need this program: https://github.com/fei-ke/OmcTextDecoder
you decrypt your file like this: java -jar omc-decoder.jar -i cscfeature.xml -d
it will generate a decrypted file out_cscfeature.xml
then you modify this file and add:
HTML:
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
your file should look something like mine (it depends what options you have enabled but for SIM CSC it should look like this)
HTML:
<?xml version="1.0" encoding="UTF-8"?>
<SamsungMobileFeature>
<Version>ED00003</Version>
<Country>SLOVENIA</Country>
<CountryISO>SI</CountryISO>
<SalesCode>SIM</SalesCode>
<FeatureSet>
<CscFeature_Audio_SupportSafeMediaVolumeDialog>TRUE</CscFeature_Audio_SupportSafeMediaVolumeDialog>
<CscFeature_Common_EulaVersion>2</CscFeature_Common_EulaVersion>
<CscFeature_Contact_ConfigImsOpStyle>SIM</CscFeature_Contact_ConfigImsOpStyle>
<CscFeature_GMS_SupportSTSTool>FALSE</CscFeature_GMS_SupportSTSTool>
<CscFeature_Graphics_DisableGameToolsPublicWIFI>TRUE</CscFeature_Graphics_DisableGameToolsPublicWIFI>
<CscFeature_Message_ConfigFreeMessage>off</CscFeature_Message_ConfigFreeMessage>
<CscFeature_Message_EnableReplyAll>TRUE</CscFeature_Message_EnableReplyAll>
<CscFeature_RIL_SupportEsim>FALSE</CscFeature_RIL_SupportEsim>
<CscFeature_Setting_EnableDataRoamingButtonInQuickPanel>TRUE</CscFeature_Setting_EnableDataRoamingButtonInQuickPanel>
<CscFeature_Setting_SupportDefaultScreenMode6500k>TRUE</CscFeature_Setting_SupportDefaultScreenMode6500k>
<CscFeature_SetupWizard_DisablePrivacyPolicyAgreement>TRUE</CscFeature_SetupWizard_DisablePrivacyPolicyAgreement>
<CscFeature_SmartSwitch_ConfigHeadUpNotification>never</CscFeature_SmartSwitch_ConfigHeadUpNotification>
<CscFeature_SyncML_DeleteCpAfterTryingToInstall>TRUE</CscFeature_SyncML_DeleteCpAfterTryingToInstall>
<CscFeature_SyncML_DiscardInvalidNetwpinCp>TRUE</CscFeature_SyncML_DiscardInvalidNetwpinCp>
<CscFeature_SyncML_EnableShowVersionNameAferSuccessfulUpdate>TRUE</CscFeature_SyncML_EnableShowVersionNameAferSuccessfulUpdate>
<CscFeature_SyncML_HideOmcAppDetailPage>TRUE</CscFeature_SyncML_HideOmcAppDetailPage>
<CscFeature_Vision_ConfigBeauty>NLLXX</CscFeature_Vision_ConfigBeauty>
<CscFeature_Vision_ConfigFood>NLLXX</CscFeature_Vision_ConfigFood>
<CscFeature_Vision_ConfigImageSearch>PTRXX</CscFeature_Vision_ConfigImageSearch>
<CscFeature_Vision_ConfigPlace>FSRXX</CscFeature_Vision_ConfigPlace>
<CscFeature_Vision_ConfigPlaceLandmark>SFSGO</CscFeature_Vision_ConfigPlaceLandmark>
<CscFeature_Vision_ConfigPlaceMap>GGLXX</CscFeature_Vision_ConfigPlaceMap>
<CscFeature_Vision_ConfigPlaceWeather>TWCXX</CscFeature_Vision_ConfigPlaceWeather>
<CscFeature_Vision_ConfigShopping>NLLXX</CscFeature_Vision_ConfigShopping>
<CscFeature_Vision_ConfigTextExchangerate>OANXX</CscFeature_Vision_ConfigTextExchangerate>
<CscFeature_Vision_ConfigTextTranslator>GGLXX</CscFeature_Vision_ConfigTextTranslator>
<CscFeature_Vision_ConfigWine>VVNXX</CscFeature_Vision_ConfigWine>
<CscFeature_VoiceCall_ConfigOpStyleForHdIcon>SIM_HD</CscFeature_VoiceCall_ConfigOpStyleForHdIcon>
<CscFeature_VoiceCall_DisableVTOutgoing>TRUE</CscFeature_VoiceCall_DisableVTOutgoing>
<CscFeature_VoiceCall_EnableCallButtonInFdnList>TRUE</CscFeature_VoiceCall_EnableCallButtonInFdnList>
<CscFeature_VoiceCall_SupportVolteCallBarringPassword>TRUE</CscFeature_VoiceCall_SupportVolteCallBarringPassword>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_Weather_ConfigCpType>TWC</CscFeature_Weather_ConfigCpType>
<CscFeature_Wifi_ConfigSnsStatus>DEFAULT_ON</CscFeature_Wifi_ConfigSnsStatus>
<CscFeature_Wifi_UseDefaultSecurityAs>WPA2/PSK</CscFeature_Wifi_UseDefaultSecurityAs>
<CscFeature_Wifi_UseRandom4digitCombinationAsSSID>TRUE</CscFeature_Wifi_UseRandom4digitCombinationAsSSID>
</FeatureSet>
</SamsungMobileFeature>
after that, reencrypt the file: java -jar omc-decoder.jar -i out_cscfeature.xml -e
it wil generate: out_out_cscfeature.xml then rename this file back to cscfeature.xml and copy it back to your phone, be sure to set the permisions the same as other files are in the same dir
then reboot and you are done
BTW: I could create HOME_CSC file for everyone to flash with odin, it wouldn't require root and you won't need to perform factory reset, the onlything I don't know is if you flash modified HOME_CSC file does that trip knox? I cannot try that as my knox is alredy tripped but if someone is wiling to root his/her phone and knows it will trip knox than tell me and we can try that, I will provide modified HOME_CSC file and he/she can flash it into his phone and if everything goes well, and knox is not tripped
and here are some more goodies you can put in your cscfeature.xml to get various efects
HTML:
<!-- Show LTE instead of 4G icon when using Mobile Data -->
<CscFeature_SystemUI_ConfigOverrideDataIcon>LTE</CscFeature_SystemUI_ConfigOverrideDataIcon>
<!-- Show 5G branding -->
<CscFeature_SystemUI_ConfigOpBranding5GIcon>5GAvailable,UseOneShapedIcon</CscFeature_SystemUI_ConfigOpBranding5GIcon>
bonus content (how to update to Android 10 and preserve root): https://www.youtube.com/watch?v=1iwL4i_e8TI&t=1452s
This is awesome I look forward to trying it out. I'm looking to buy 2 S10 US version for my father and I . I can only assume that it should perform the same work the NA north america firmware. Is this model easy to root bc I want to install exposed and remove some samsung stuff and get a good firewall? I'll can figure out how just asking causally.
hello,
i would like to try KNOX is 0 in my s10
I'm using csc - HOME_CSC_OMC_OXM_G973FOXM9DTI8_CL19530501_QB34490045_REV01_user_low_ship.tar
could you modify it and send link for download ?
Hi, I don´t know how to use the decryption program downloaded from github. There is not any executable file at all when I decompress the jar file. Is it necessary a java environment? No idea about this and any help is welcome.
Thanks
EDIT:
I´ve got to decrypt the file installing java after a lot of attempts. By the way I think that is possible to get the cscfeature.xml file without rooting, just using adb commands
Hi, anyway to use this method on a non root phone (S10+ SM-G975F)?
i get to the step of pushing the file back to the device and i get a Read-only error.
Thanks!
HTML:
adb: error: failed to copy 'cscfeature.xml' to '/system/product/omc/TPA/conf/cscfeature.xml': remote couldn't create file: Read-only file system
rashaunny said:
This is awesome I look forward to trying it out. I'm looking to buy 2 S10 US version for my father and I . I can only assume that it should perform the same work the NA north america firmware. Is this model easy to root bc I want to install exposed and remove some samsung stuff and get a good firewall? I'll can figure out how just asking causally.
Click to expand...
Click to collapse
The only way to root a US Galaxy S10 is to pay some guy in China to unlock the bootloader remotely, which has been discussed in the forums here although it's now sort of hush hush. Karma firewall on the play store is good I hear.
veso266 said:
well I did it, I have native call recorder on my SIM CSC on my GalaxyS10+ Android 10 now I will tell you how its done
1. Find your cscfeature.xml file (this file hold many thing and also holds the option to enable call recorder
on my Galaxy S10+ Android 10 its in:
where country code is your active CSC (mine is SIM) so my file would be in:
then if you have root copy this file to your computer, its encrypted so you will have to decrypt it for this you will need this program: https://github.com/fei-ke/OmcTextDecoder
you decrypt your file like this: java -jar omc-decoder.jar -i cscfeature.xml -d
it will generate a decrypted file out_cscfeature.xml
then you modify this file and add:
HTML:
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
your file should look something like mine (it depends what options you have enabled but for SIM CSC it should look like this)
HTML:
<?xml version="1.0" encoding="UTF-8"?>
<SamsungMobileFeature>
<Version>ED00003</Version>
<Country>SLOVENIA</Country>
<CountryISO>SI</CountryISO>
<SalesCode>SIM</SalesCode>
<FeatureSet>
<CscFeature_Audio_SupportSafeMediaVolumeDialog>TRUE</CscFeature_Audio_SupportSafeMediaVolumeDialog>
<CscFeature_Common_EulaVersion>2</CscFeature_Common_EulaVersion>
<CscFeature_Contact_ConfigImsOpStyle>SIM</CscFeature_Contact_ConfigImsOpStyle>
<CscFeature_GMS_SupportSTSTool>FALSE</CscFeature_GMS_SupportSTSTool>
<CscFeature_Graphics_DisableGameToolsPublicWIFI>TRUE</CscFeature_Graphics_DisableGameToolsPublicWIFI>
<CscFeature_Message_ConfigFreeMessage>off</CscFeature_Message_ConfigFreeMessage>
<CscFeature_Message_EnableReplyAll>TRUE</CscFeature_Message_EnableReplyAll>
<CscFeature_RIL_SupportEsim>FALSE</CscFeature_RIL_SupportEsim>
<CscFeature_Setting_EnableDataRoamingButtonInQuickPanel>TRUE</CscFeature_Setting_EnableDataRoamingButtonInQuickPanel>
<CscFeature_Setting_SupportDefaultScreenMode6500k>TRUE</CscFeature_Setting_SupportDefaultScreenMode6500k>
<CscFeature_SetupWizard_DisablePrivacyPolicyAgreement>TRUE</CscFeature_SetupWizard_DisablePrivacyPolicyAgreement>
<CscFeature_SmartSwitch_ConfigHeadUpNotification>never</CscFeature_SmartSwitch_ConfigHeadUpNotification>
<CscFeature_SyncML_DeleteCpAfterTryingToInstall>TRUE</CscFeature_SyncML_DeleteCpAfterTryingToInstall>
<CscFeature_SyncML_DiscardInvalidNetwpinCp>TRUE</CscFeature_SyncML_DiscardInvalidNetwpinCp>
<CscFeature_SyncML_EnableShowVersionNameAferSuccessfulUpdate>TRUE</CscFeature_SyncML_EnableShowVersionNameAferSuccessfulUpdate>
<CscFeature_SyncML_HideOmcAppDetailPage>TRUE</CscFeature_SyncML_HideOmcAppDetailPage>
<CscFeature_Vision_ConfigBeauty>NLLXX</CscFeature_Vision_ConfigBeauty>
<CscFeature_Vision_ConfigFood>NLLXX</CscFeature_Vision_ConfigFood>
<CscFeature_Vision_ConfigImageSearch>PTRXX</CscFeature_Vision_ConfigImageSearch>
<CscFeature_Vision_ConfigPlace>FSRXX</CscFeature_Vision_ConfigPlace>
<CscFeature_Vision_ConfigPlaceLandmark>SFSGO</CscFeature_Vision_ConfigPlaceLandmark>
<CscFeature_Vision_ConfigPlaceMap>GGLXX</CscFeature_Vision_ConfigPlaceMap>
<CscFeature_Vision_ConfigPlaceWeather>TWCXX</CscFeature_Vision_ConfigPlaceWeather>
<CscFeature_Vision_ConfigShopping>NLLXX</CscFeature_Vision_ConfigShopping>
<CscFeature_Vision_ConfigTextExchangerate>OANXX</CscFeature_Vision_ConfigTextExchangerate>
<CscFeature_Vision_ConfigTextTranslator>GGLXX</CscFeature_Vision_ConfigTextTranslator>
<CscFeature_Vision_ConfigWine>VVNXX</CscFeature_Vision_ConfigWine>
<CscFeature_VoiceCall_ConfigOpStyleForHdIcon>SIM_HD</CscFeature_VoiceCall_ConfigOpStyleForHdIcon>
<CscFeature_VoiceCall_DisableVTOutgoing>TRUE</CscFeature_VoiceCall_DisableVTOutgoing>
<CscFeature_VoiceCall_EnableCallButtonInFdnList>TRUE</CscFeature_VoiceCall_EnableCallButtonInFdnList>
<CscFeature_VoiceCall_SupportVolteCallBarringPassword>TRUE</CscFeature_VoiceCall_SupportVolteCallBarringPassword>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_Weather_ConfigCpType>TWC</CscFeature_Weather_ConfigCpType>
<CscFeature_Wifi_ConfigSnsStatus>DEFAULT_ON</CscFeature_Wifi_ConfigSnsStatus>
<CscFeature_Wifi_UseDefaultSecurityAs>WPA2/PSK</CscFeature_Wifi_UseDefaultSecurityAs>
<CscFeature_Wifi_UseRandom4digitCombinationAsSSID>TRUE</CscFeature_Wifi_UseRandom4digitCombinationAsSSID>
</FeatureSet>
</SamsungMobileFeature>
after that, reencrypt the file: java -jar omc-decoder.jar -i out_cscfeature.xml -e
it wil generate: out_out_cscfeature.xml then rename this file back to cscfeature.xml and copy it back to your phone, be sure to set the permisions the same as other files are in the same dir
then reboot and you are done
BTW: I could create HOME_CSC file for everyone to flash with odin, it wouldn't require root and you won't need to perform factory reset, the onlything I don't know is if you flash modified HOME_CSC file does that trip knox? I cannot try that as my knox is alredy tripped but if someone is wiling to root his/her phone and knows it will trip knox than tell me and we can try that, I will provide modified HOME_CSC file and he/she can flash it into his phone and if everything goes well, and knox is not tripped
and here are some more goodies you can put in your cscfeature.xml to get various efects
HTML:
<!-- Show LTE instead of 4G icon when using Mobile Data -->
<CscFeature_SystemUI_ConfigOverrideDataIcon>LTE</CscFeature_SystemUI_ConfigOverrideDataIcon>
<!-- Show 5G branding -->
<CscFeature_SystemUI_ConfigOpBranding5GIcon>5GAvailable,UseOneShapedIcon</CscFeature_SystemUI_ConfigOpBranding5GIcon>
bonus content (how to update to Android 10 and preserve root):
Click to expand...
Click to collapse
I have decompressed HOME_CSC, and I'm seeing its content. However, I can't find where to change this feature.
Can you please tell me what to change exactly?
I have a Pixel 5.
The stock rom does not have South Korean carrier mbn files.
I managed to source the files from the Internet.
I tried to copy paste it into
/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic/Pixel
but it doesn't work (I can't change folder properties to write).
I tried using the volte_switch.zip from this guide
Module to enable 5G/VoLTE/VoWIFI on Pixel4a 5G/Pixel5
Update (9 Oct 2022): Upload module here. Update (7 Apr 2021): If you are looking for the manual way to add 5G support besides the magisk module way or the module does not work for you. Please refer to #54 for the detailed steps. Thanks again to...
forum.xda-developers.com
and modified the files to add the mbn files of my choice but flashing the zip deletes all folders under generic/Pixel/ except my country's folder.
Removing the "module" from magisk manager and rebooting brings everything back.
Is it possible to make a flashable zip to add the mbn files?
Or does it require repacking the radio.img?
Or does the volte_switch.zip install the mbn files systemlessly?
If you post your Magisk module it might be easier to say why it doesn't work.
But if the Pixel directory is emptied out it sounds like you have a replace file in there causing issues. Just guessing though...
Didgeridoohan said:
If you post your Magisk module it might be easier to say why it doesn't work.
But if the Pixel directory is emptied out it sounds like you have a replace file in there causing issues. Just guessing though...
Click to expand...
Click to collapse
Thanks for the suggestion. I've uploaded the flash zip file as well. When I went through the install script, I did notice the "replace" code in there. How should I change it to?
Ok after much googling, I figured out.
I added in all my original mbn folders as well and then typed in:
REPLACE="
/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/
"
into customize.sh
This Replaced the folder with all the original and new mbn files.
Ok, I thought it worked but it's not actually working.
The new mbn files seems to be there but when I force a mbn reload by changing sim cards, it still loads the "original" files as if the new files aren't actually there.
For countries/carriers that's not listed in google's official supported list, the phone uses a 'generic' carrier mbn which is located in the generic/pixel/common/wildcard/pixel_wildcard/mcfg_sw.mbn.
This wildcard mbn is the generic carrier file that has 5G disabled by default. So in theory, all I need to do is replace the wildcard mbn with a different carrier's mbn which has 5G enabled by default. Then create magisk module and flash it to have it replaced.
My module appears to replace the files but the new files don't actually get loaded. When I change sim cards to force a reloading of mbn file, It still loads the old files.
What can I do to fix this? Any help is appreciated. Thanks.
Attached is my module.
Calling @Didgeridoohan good sir, if you could kindly provide me with knowledge about the post above, if possible. Thanks.
swangjang said:
Calling @Didgeridoohan good sir, if you could kindly provide me with knowledge about the post above, if possible. Thanks.
Click to expand...
Click to collapse
Busy life...
In theory you shouldn't at all need to do that replace function and add back all the stock files with the module. Magisk should take care of mounting or replacing only the files you need, so anything else is just redundant... But if it works, sure.
But it seems like it doesn't.
If you can verify with a file explorer that the files have been replaced with the ones from your module and the values still are taken from the original files that very likely means that there's more to it than just replacing those files.
You could provide the module install log and the Magisk log (Canary release so that it's actually useful) to see if there's anything wrong there.