[Connected Car] donaldta:
Have you thought about making this process into an actual APK for an Android Phone or Tablet? That way people would have the option of rooting the SCT through their handheld Android devices. Similarly to how getiem was using Craze - ADB Toolkit to carry out the ADB commands without a PC.

Yes, the "/system/whitelist.xml" file allows the respective application to run as long as its assigned manifest package name is in the list. If you need help finding out the package name, you can use "adb shell pm list packages" to get a list of all the installed packages and if there are more than one package names that seem similar, then you can use "adb shell dumpsys package {package.name}" to get more detailed information about the pacakge from the other list.

Don't forget about checking with the method you created the original "evil--ppktemp.tmp", if there is a way we can sneak this process into SCT as a package then it would be much simpler method for everyone.

:) No problem but even though we have root, don't forget that we still need a little bit of feedback left.

For example, try these commands to see if you can see any of the hidden settings from the Settings package pop-up on your SCT which weren't available to you normally.

adb shell am start -n com.android.settings/.WirelessSettings

adb shell am start -n com.android.settings/.SoundSettings

adb shell am start -n com.android.settings/.DisplaySettings

adb shell am start -n com.android.settings/.SecuritySettings

adb shell am start -n com.android.providers.subscribedfeeds/com.android.settings.ManageAccountsSettings

adb shell am start -n com.android.settings/.PrivacySettings

adb shell am start -n com.android.settings/.deviceinfo.Memory

adb shell am start -n com.android.settings/.LanguageSettings

adb shell am start -n com.android.settings/.VoiceInputOutputSettings

adb shell am start -n com.android.settings/.AccessibilitySettings

adb shell am start -n com.android.settings/.DateTimeSettings

adb shell am start -n com.android.settings/.DeviceInfoSettings

adb shell am start -n com.android.settings/.quicklaunch.QuickLaunchSettings

adb shell am start -n com.android.settings/.fuelgauge.PowerUsageSummary

adb shell am start -n com.android.settings/.ApplicationSettings

adb shell am start -n com.android.settings/.RunningServices

adb shell am start -n com.android.settings/.DevelopmentSettings

adb shell am start -n com.android.settings/.applications.StorageUse

And the output files of these commands, which you'd claimed to do this past Monday:

adb shell "ls -l /system/bin" > bin.txt

adb shell "ls -l /system/sbin" > sbin.txt

adb shell "ls -l /system/xbin" > xbin.txt

It would be helpful. Especially, if we can find out whether or not the sed command is on the SCT. Then we could use "adb shell sed -i 's/ro.parrot.install.allow-all=false/ro.parrot.install.allow-all=true/' /system/build.prop" To change the file in place instead of needing to pull, edit, push, and chmod it.

---------- Post added at 07:38 AM ---------- Previous post was at 07:35 AM ----------

I don't believe so but it would be a good experiment. Though, I believe the list is pattern matched "as is" without using regular expressions. Otherwise, you can use just a single "*". There wouldn't be a need for the extra ".*.*" since that would only further limit pattern matching.