Installing eGate on LG Classic

  1. You will need a computer with the adb tool installed, and a usb cable to connect your phone to your computer. This tutorial should get you started with adb.
  2. Your phone will need to be able to connect over the internet to our licensing server. Either you need a SIM with a data plan or the phone needs to be connected to wifi.
  3. After purchasing, you will receive a message containing file download links for several apk files, along with a license key. Make sure to save the license key for the next step. Download the file named egate for lg classic.apk.
  4. Open the terminal app, and and run this command:

adb install -g "Downloads/egate for lg classic.apk"

  1. In the same terminal, run:

adb shell pm uninstall -k --user 0 com.qualcomm.simcontacts

  1. In the same terminal run this:

adb shell dpm set-device-owner com.android.cts.egate/com.oss.egate.a

  1. Open the launcher and select the eGate icon to open it.
  2. Enter the license code in the license field and tap save. Ignore the dealer code field. If you see the app password screen appear, congratulations. Your license has been activated. If you see the Log In button again, that means that our licensing server could not be reached.
  3. Enter the password that will be used to password protect eGate. This password cannot be recovered, so make sure to store it in a safe place.
  4. You should now have arrived at the main screen, so configure eGate as you wish and exit the app.
  5. That’s it!

I’m having this issue on the lg classic

C:\Users\PCPLUS>adb shell dpm set-device-owner com.android.cts.egate/com.oss.egate.a
java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device
        at android.os.Parcel.readException(Parcel.java:2021)
        at android.os.Parcel.readException(Parcel.java:1959)
        at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:5184)
        at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:148)
        at com.android.commands.dpm.Dpm.onRun(Dpm.java:96)
        at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
        at com.android.commands.dpm.Dpm.main(Dpm.java:41)
        at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
        at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:285)


i can confirm that a hard factory reset did not resolve the issue

i skipped that step and proceeded with the installation as usual, it allowed me to set a pin but when i try to log in the app crashes
attachment_21

What is the output of adb shell dumpsys account?

My bad. I didn’t test the upload properly. I know what the problem is, and I will upload a fixed version tomorrow. This is a separate problem from the Not allowed to set the device owner error.

C:\Users\PCPLUS>adb shell dumpsys account
User UserInfo{0::13}:
  Accounts: 1
    Account {name=SIM, type=com.android.sim}

  AccountId, Action_Type, timestamp, UID, TableName, Key
  Accounts History
  1,action_account_add,2023-09-05 23:50:53,1001,accounts,0

  Active Sessions: 0

  RegisteredServicesCache: 5 services
    ServiceInfo: AuthenticatorDescription {type=com.android.sim}, ComponentInfo{com.qualcomm.simcontacts/com.qualcomm.simcontacts.SimAuthenticateService}, uid 1001
    ServiceInfo: AuthenticatorDescription {type=com.android.exchange}, ComponentInfo{com.lge.email/com.lge.email.service.EasAuthenticatorService}, uid 10130
    ServiceInfo: AuthenticatorDescription {type=com.lge.email.account}, ComponentInfo{com.lge.email/com.lge.email.service.ImapPopAuthenticatorService}, uid 10130
    ServiceInfo: AuthenticatorDescription {type=com.android.localphone}, ComponentInfo{com.qualcomm.simcontacts/com.qualcomm.simcontacts.PhoneAuthenticateService}, uid 1001
    ServiceInfo: AuthenticatorDescription {type=com.lge.sync}, ComponentInfo{com.android.providers.contacts/com.lge.providers.contacts.AuthenticatorService}, uid 10116

  Account visibility:

this is with egate installed but not set as device owner

i haven’t had that problem with the new command adb shell dpm set-device-owner com.android.cts.egate/com.oss.egate.a
though i’ve had it previously eGate--Android MDM - #18 by Lamden613 - Filters and MDMs - Jtech forums

this is with egate installed but not set as device owner

run adb shell pm uninstall -k --user 0 com.qualcomm.simcontacts and try setting device own again.

An update has been uploaded to the store.

resetting device again ??

success
here are the steps i took

  1. I did a hard factory reset by going to the hidden menu (*#546368#*125#)
  2. I ran adb shell pm uninstall -k --user 0 com.qualcomm.simcontacts
  3. I then closed that terminal and proceeded as per you directions in another terminal
1 Like

here it is

C:\Users\PCPLUS>adb install -g "Downloads/egate for lg classic.apk
Performing Streamed Install
Success

C:\Users\PCPLUS>adb shell dpm set-device-owner com.android.cts.egate/com.oss.egate.a
Success: Device owner set to package ComponentInfo{com.android.cts.egate/com.oss.egate.a}
Active admin set to component {com.android.cts.egate/com.oss.egate.a}

ill post a full review and rundown in a day or two
Screenshot 2023-09-06 181938

Thanks for your help. I’ve updated the instructions at the top of this thread.

I believe this needs to be ran in a separate terminal (at least in my experience)

I’ve always run it in the same terminal. Maybe we are using different terminals. :grinning:

I dont know y this thread is named “instilling egate on a lg vn220”. This app couldn’t be installed on a lg vn220 because its android 6. If you can change the sdk i can test it on the vn220

My bad. I thought that’s what we were talking about. I’ll change the title.

Not going to happen. I tried but ran into problems where some of the app dependencies did not have suitable versions for such a range of Android versions.

I just got my LG Classic to test it myself. Can’t figure out how to enable adb. Tried all the secret codes I could find. Any ideas?