On rooted Oreo phones with the latest SuperSU v2.82R5 using both Samsung Phone Info and Shortcut Master, there's an java.lang error when trying run any RILServiceMode commands like com.sec.android.RILServiceModeApp/<android_secret_code:0011:0>
https://xdaforums.com/attachment.php?attachmentid=4514309&d=1527711585
I've read on an FDroid developer changelog that the java.lang error can be ignored by the catch exexption, and it should work fine. Supposedly it's a non-fatal error.
"Ignore dumb java.lang.IndexOutOfBoundsException"
The app is called SuperFreezZ, and maybe you can get in touch with him to see if you could figure this issue out.
https://f-droid.org/en/packages/superfreeze.tool.android/
The normal ADB "broadcast" command doesn't work either for secret_codes, nothing pops up on the phone.
adb shell am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://0011
Broadcasting: Intent { act=android.provider.Telephony.SECRET_CODE dat=android_secret_code://0011 flg=0x400000 }
Broadcast completed: result=0
While playing around with Logcat on a rooted G930U on Oreo, I've noticed that the android.provider.Telephony.SECRET_CODE requires permission to the com.sec.factory.permission.KEYSTRING, which might be the key enabling it on newer Androids. Interestingly if I insert a 520K test dongle into the phone and go to the dialer, it enables a lot of normally non-working secret codes directly on the keypad (including *#27663368378#, *#22745927#, *#33725327#, etc. maybe it enables the factory keystring??)
Filter #5: BroadcastFilter{ac06490}
Action: "android.provider.Telephony.SECRET_CODE"
Scheme: "android_secret_code"
AutoVerify=false
requiredPermission=com.sec.factory.permission.KEYSTRING
Not sure if it's just me, so if anyone has any solution sending the Secret_Code over ADB successfully on Oreo or higher, please let me know.
I miss those commands so bad.