Guide for overriding IMS settings to force enable VoLTE/VoWiFi using Carrier Privileges
Martin Paljak for GlobalPlatformPro (gp.jar) - A tool to load and manage applets on compatible JavaCards from command line
Bertrand Martel for ARA-M applet (applet.cap) - ARA-M implementation for JavaCards. ARA-M is an application (typically present on a SIM card) which manage access rules that are enforced by an Access Control Enforcer (typically present on Android device). The enforcer makes sure the rules from the ARAM are enforced. An access rule is composed of an AID, a certificate hash (SHA1/SHA256 of client application cert) and a set of rules. The Access Control enforcer will allow/deny a client application (for example an Android app) to send APDU to a Secure Element (SE) applet based on these rules
In order to install and/or manage Java Card applets on your SIM card, make sure to have KIC1, KID1 and KIK1 keys. KIC1, KID1 and KIK1 could differ from one SIM card to another so make sure to have the correct keys. If you have a non-programmable USIM/ISIM with ARA-M application and have option to push certficates to ARA-M via OTA, jump to Step 4
$ git clone https://github.com/herlesupreeth/CoIMS_Wiki
$ cd CoIMS_Wiki
$ alias gp="java -jar $PWD/gp.jar"
Example: In sysmoUSIM-SJS1-4ff USIM cards, the key mappings for GlobalPlatformPro are as follows
sysmoUSIM key | GlobalPlatformPro argument |
---|---|
KIC1 | --key-enc |
KID1 | --key-mac |
KIK1 | --key-dek |
Fetch details of the SIM by replacing KIC1, KID1 and KIK1 with correct keys respective to your SIM card. Execution of below command should not result in any error. If there is an error, please check the error and double check everything before proceeding
$ gp --key-enc <KIC1> --key-mac <KID1> --key-dek <KIK1> -lvi
Proceed with caution when unlocking SIM card as it could brick your USIM/ISIM if incorrect KIC1, KID1 and KIK1 keys are used
$ gp --key-enc <KIC1> --key-mac <KID1> --key-dek <KIK1> --unlock
Example: A sysmoUSIM-SJS1-4ff USIM card with following keys is unlocked as follows
KIC1 = --key-enc = 975B496CED1F2FB984145A55AB31A585
KID1 = --key-mac = E7207B567F9D08726A6EFBD90C50DA9A
KIK1 = --key-dek = DEAA4E9A9B3BC6FC5EFF77A8E9925632
$ gp --key-enc 975B496CED1F2FB984145A55AB31A585 --key-mac E7207B567F9D08726A6EFBD90C50DA9A --key-dek DEAA4E9A9B3BC6FC5EFF77A8E9925632 --unlock
Default type=DES3 bytes=404142434445464748494A4B4C4D4E4F kcv=8BAF47 set as master key for A000000003000000
Proceed with caution when installing applets on SIM card as it could brick your USIM/ISIM if incorrect KIC1, KID1 and KIK1 keys are used
Install the ARA-M applet (applet.cap). The following command must execute without any errors.
# If SIM is not unlocked in Step 2
$ gp --key-enc <KIC1> --key-mac <KID1> --key-dek <KIK1> --install applet.cap
# If SIM is unlocked in Step 2
$ gp --install applet.cap
The Carrier Config Android app which will be installed in Step 5 is signed with following SHA1 key
SHA1: E4:68:72:F2:8B:35:0B:7E:1F:14:0D:E5:35:C2:A8:D5:80:4F:0B:E3
In order to provide Carrier Privileges to Carrier Config app, push the above SHA1 certifcate as follows
# If SIM is not unlocked in Step 2
$ gp --key-enc <KIC1> --key-mac <KID1> --key-dek <KIK1> -a 00A4040009A00000015141434C0000 -a 80E2900033F031E22FE11E4F06FFFFFFFFFFFFC114E46872F28B350B7E1F140DE535C2A8D5804F0BE3E30DD00101DB080000000000000001
# If SIM is unlocked in Step 2
$ gp -a 00A4040009A00000015141434C0000 -a 80E2900033F031E22FE11E4F06FFFFFFFFFFFFC114E46872F28B350B7E1F140DE535C2A8D5804F0BE3E30DD00101DB080000000000000001
The split-up of above APDU sent to SIM card is as follows
#### REF-AR-DO for UICC Carrier Privileges |REF-AR-DO|T|E2 | | | | | | |L|2F | | | | | | |V|REF-DO|T|E1 | | | | | | |L|1E | | | | | | |V|AID-REF-DO |T|4F | | | | | | |L|06 | | | | | | |V|FFFFFFFFFFFF | | | | | |DeviceAppID-REF-DO|T|C1 | | | | | | |L|14 | | | | | | |V|E46872F28B350B7E1F140DE535C2A8D5804F0BE3| | | |AR-DO |T|E3 | | | | | | |L|0D | | | | | | |V|APDU-AR-DO |T|D0 | | | | | | |L|01 | | | | | | |V|01 (Always) | | | | | |PERM-AR-DO |T|DB | | | | | | |L|08 | | | | | | |V|0000000000000001 |
To check the list of installed certificates use the following command
# If SIM is not unlocked in Step 2
$ gp --key-enc <KIC1> --key-mac <KID1> --key-dek <KIK1> --acr-list-aram
RULE #0 :
AID : FFFFFFFFFFFF
HASH : E46872F28B350B7E1F140DE535C2A8D5804F0BE3
APDU rule : ALWAYS(0x01)
# If SIM is unlocked in Step 2
$ gp --acr-list-aram
RULE #0 :
AID : FFFFFFFFFFFF
HASH : E46872F28B350B7E1F140DE535C2A8D5804F0BE3
APDU rule : ALWAYS(0x01)
If you have a non-programmable USIM/ISIM with ARA-M application and have option to push certficates to ARA-M via OTA, push the above SHA1 certificate on to the SIM
Make sure the SIM card is placed in the default/first SIM slot of the device (only for multi-sim capable devices)
Download the CoIMS Carrier Config app from play store. Then, run the app
Important points/values to note after running the app for this app to enable VoLTE
After installation of the app, access the options menu on the right hand top corner and select Samsung/Mediatek IMS Settings option based on your device chipset and edit the IMS settings accordingly to enable desired IMS features
This is an alternate method if the above method using GlobalPlatformPro tool does not work for you
$ git clone https://github.com/herlesupreeth/sim-tools
# Use shadysim.py if your SIM has ONLY USIM (not ISIM) application e.g. sysmoUSIM-SJS1-4ff
# Use shadysim_isim.py if your SIM has USIM + ISIM application e.g. sysmoISIM-SJA2
# If SIM has ONLY USIM application
$ python shadysim.py --pcsc -t --kic <KIC1> --kid <KID1>
# If SIM has USIM + ISIM application
$ python shadysim_isim.py --pcsc -t --kic <KIC1> --kid <KID1>
# If SIM has ONLY USIM application
$ python shadysim.py --pcsc -l applet.cap -i applet.cap --kic <KIC1> --kid <KID1> --module-aid A00000015141434C00 --instance-aid A00000015141434C00
# If SIM has USIM + ISIM application
$ python shadysim_isim.py --pcsc -l applet.cap -i applet.cap --kic <KIC1> --kid <KID1> --module-aid A00000015141434C00 --instance-aid A00000015141434C00
The Carrier Config Android app is signed with following SHA1 key
SHA1: E4:68:72:F2:8B:35:0B:7E:1F:14:0D:E5:35:C2:A8:D5:80:4F:0B:E3
In order to provide Carrier Privileges to Carrier Config app, push the above SHA1 certifcate as follows
# If SIM has ONLY USIM application
$ python shadysim.py --pcsc --kic <KIC1> --kid <KID1> --aram-apdu 80E2900033F031E22FE11E4F06FFFFFFFFFFFFC114E46872F28B350B7E1F140DE535C2A8D5804F0BE3E30DD00101DB080000000000000001
# If SIM has USIM + ISIM application
$ python shadysim_isim.py --pcsc --kic <KIC1> --kid <KID1> --aram-apdu 80E2900033F031E22FE11E4F06FFFFFFFFFFFFC114E46872F28B350B7E1F140DE535C2A8D5804F0BE3E30DD00101DB080000000000000001
# If SIM has ONLY USIM application
$ python shadysim.py --pcsc --kic <KIC1> --kid <KID1> --aram-apdu 80CAFF4000
# If SIM has USIM + ISIM application
$ python shadysim_isim.py --pcsc --kic <KIC1> --kid <KID1> --aram-apdu 80CAFF4000
Use adb debugging with filter for "ims" keyword
OR
If the value of CarrierIdentifier indicated in the app is -1 (i.e Unknown Carrier) - Not shown in Android 8.0 and 8.1 devices
If PLMN is on the following lists with respect to Android version the phone is running on
Resolution: Wait for vendor to release an update and hopefully it contains the updated carrier list
If PLMN is not on the above lists
Resolution: Refer the following link
https://source.android.com/devices/tech/config/carrierid#integrating_carrier_ids_with_carrierconfig
If the SIM is placed in non-default SIM slot in a multi-SIM phones i.e. SIM in slot 1 (SIM slot 0 (default), SIM slot 1) of device
VoWiFi may not work on most devices because the ePDG address is still hard-coded in configuration files on the device and is not fetched from USIM