Start at boot disabled for Google Play Store and Service-> Stuck in a boot loop...

[ao.tao]

Ahoy Together

In Short:

1. Is there a way to enable/disable "start at boot" for apps from adb shell? If yes, how?
2. How are the app names of Google Play Store and its Service?

Thanks in advance!

Long Version:
A few days ago I disabled ("Where is my Mind"/Pixies) "Start at boot" for Google Play Store and for the Service. I am not pretty sure, but I guess I also changed some permissions to "Always ask". This resulted in an immediate freeze of my Note 3 (Purify) and a reboot. Whenever it reaches the locked Screen (Displaying Time etc.) it freezes again and reboots after a short while. After I recognized that all this was not a "great" idea, I really did research but actually I couldn't find a solution for how to revert it.

What I did until now:
First I tried to install opengapps again, but nothing changed. As I am using TWRP, I went into recovery boot and started a shell.

adb root
adb shell pm reset-permissions

As some of you may know: This is not working The complete environment for adb in recovery is not working properly, because all the settings and configs (env, etc.) are not set/loaded. Tried to hack it anyway:

mount system
export _=/system/bin/env 
export ANDROID_DATA=/data 
export HOME=/data 
export ANDROID_STORAGE=/storage 
export TERMINFO=/system/etc/terminfo 
export SYSTEMSERVERCLASSPATH=/system/framework/org.cyanogenmod.platform.jar:/system/framework/org.cyanogenmod.hardware.jar:/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar 
export SHELL=/system/bin/sh 
export TERM=linux 
export ANDROID_SOCKET_adbd=12 
export ANDROID_CACHE=/cache 
export EXTERNAL_STORAGE=/sdcard 
export MKSH=/system/bin/sh 
export ANDROID_ASSETS=/system/app 
export ASEC_MOUNTPOINT=/mnt/asec 
export BOOTCLASSPATH=/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/apache-xml.jar:/system/framework/org.apache.http.legacy.boot.jar 
export VIBE_PIPE_PATH=/dev/pipes 
export ANDROID_BOOTLOGO=1 
export HOSTNAME=hltexx
export USER=shell 
export TMPDIR=/data/local/tmp 
export PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin:system/lib
export ANDROID_PROPERTY_WORKSPACE=10,0 
export ANDROID_ROOT=/system

As you can image, this didn't do it either. The pm command (Package Manager) didn't worked properly (-> null object reference).

Then I found a thread with mentioning safe mode:

adb shell echo "1" > /data/property/persist.sys.safemode
adb shell chmod 600 /data/property/persist.sys.safemode

But no chance again. Couldn't pass the locked Screen.

After a while I realized, that after clearing my cache (dalvik/cache) my Note3 is busy while start up. I could actually execute this both commands:

adb root
adb shell pm reset-permissions

But again, nothing changed. I guess the permissions aren't the problem, but the "start at boot" options are.

I have a short time slot (while rebooting after wipe cache/dalvik) where I can reach a working adb shell with root permissions. But I couldn't find a way in the internet how to enable "start at boot" option for an app I guess I am using the wrong keywords or... whatever. Can anyone give me an hint? Or tell me what I can do?

And NO, factory reset is no option, as there is data on that phone, which is important for me.

My Phone:
Note 3, Purify (Latest), TWRP, OpenGAPPS

Thanks in advance!

Best regards,
AO Toprak