[Android Software/Hacking General [Developers Only]] calisro:
This IS working for 4.3+ using xposed module.

http://xdaforums.com/showpost.php?p=49878296&postcount=679

All credit goes to Phantasm4489. I am only adding the the OP so people can find it.

Below can be used for anything below 4.2 but I still think the xposed module above is better.

Standard Disclaimer:

First off:

THANKS to sparky for the 'su' binary I use in my newer scripts.

THANKS to chainfire for the 'su' binary I use in my older scripts.

THANKS to Fallon for helping fine tuning the directions.

This thread is dedicated to using GFE on rooted devices. My intent is to understand root detection schemes for my own personal education. If the information here is beneficial to others, then that is a plus.

I came up with a process that satisfies both GFE and its use on rooted (technically temp unrooted) devices. Basically unrooting and rerooting the phone so that the GFE app functions and I comply with not running GFE on a rooted phone. .

Tested on CM9 and CM10 for the Epic 4 Touch and the Galaxy S3. I've seen success on other ROMS as well. If you run into issues, i'd be happy to help and improve the process.

What GOOD(GFE) detects and what it doesn't care about

Some key notes about what GFE seems to detect:

Detects 'su' anyplace on the phone /system partition (usually located in /system/bin/su or /system/xbin/su).

Detects the superuser apk and supersu apk

Detects if you have su'd in adb or shell while it is running. Close adb and log out of and shells before launch!

If you use a root tool like titanium, reboot before launching good! Titanium will sometimes leave open rooted processes running.

In pre-JB, it could use the READ_LOGS android permission to comb the system logs and find 'root like 'activity'. In JB, that 'security hole' is closed and that permission is locked down by android.

It detects if /system is RW.

The software is setup to never be shutdown. Once its started, it runs no matter what. Preventing it from starting is a good thing IMHO.

Seems that for some unknown reason, if es explorer was run in root mode at any point before running good, it detects root. Even if I manually kill all the back ground processes before unfreezing/launching Good.

Sometimes I get a compliance failed when I was working in ADB prior to running good. Typically if I was in ADB doing root work, i'll reboot the ROM before enabling good.

Turn off 'automatic update' for super user app from market

What GFE does not seem to care about:

busybox

CWM

locked/unlocked bootloaders

Here is how to make root and GFE play as nice as possible. This isn't perfect but it works pretty good. I still get the 'compliance failed' once in a while when i do something dumb. I am lucky in that I can clear data on the GFE app and reuse the prior key or request a new key from our IT system on demand. If you cannot do this easily, then this may be cumbersome. As we further progress this, we should get less and less lockouts.

SCRIPTED PROCESS

Downloads:

Something to run the scripts One of these will do:

- Connectbot or any shell execution program from play store. connectbot has widgets

. I use connectbot....

​

- Script Manager found here: http://db.tt/Vonx78NI . Or playstore.​

(required for PRE-JB roms only). Install Permissions Denied from the Market

The latest cwm/twrp flashable zip attached to this OP.

An installation of busybox. Typically comes with CM and lots of other ROMs but just making the point here that it is required.

Setup app and dependencies:

Flash the gfe_workaround_setup zip attached to this OP in CWM. This will create four scripts and a "backdoor" su binary. They are as follows:

/system/xbin/dger

/system/xbin/egdr

/system/xbin/fu. (The sparkysu binary is insecure so be careful out there! Just a disclaimer)

/system/xbin/r_dger

/system/xbin/r_egdr

Install Good Application

If pre-JB (NOT REQUIRED ON JB+), open Permissions Denied and disable the READ_LOGS permission for the Good Application. Immediately after disabling that permission reboot the device from within the Permissions Denied app (in the menu). It must be done from within the application immediately after toggling the permissions to denied.

Optional but recommended: use "autostarts app" (or similar) from market to turn off all autostarting flags for Good app. This is incase you forget to disable root before you reboot and dont want it to start after again after flashing a rom which would restore root..

Use Connectbot or old script manager to execute the enable/disable scripts.

HOW TO Use the scripts and run the Good.

These scripts will basically temp unroot your phone and disable the superuser user whenever you want to run good. It will reverse the operation whenever you want to return root and lockup good.

I typically leave good disabled unless I am using it but that is up to you.

Whenever you want to 'run good'. You will run the script egdr.

Whenever you want to disable good and return root to your phone run dger (prior to reboot for example or flashing roms or whatever)

DO NOT FORGET TO run the DGER script before flashing a rom since that rom will repush superuser and su and if good was enabled when you shutdown to reflash the rom, good will detect root and deactivate the handheld. Also since I disable the superuser user entirely when you flash the new rom, you will lose root and will need to enable the superuser user and reflash the rom to fix things... You can always just fix it with adb but renabling superuser... But that is a pain.

(pre-JB only) Permissions Denied takes FOREVER to startup, several minutes at least & you repeatidly see it getting root permissions, at first I thought it was having issues but that is how it works.

No need to "Lock Permissions" within the Permissions Denied app from what I've seen but ymmv

Under the ROM Developer Options "Root access" is irrelevant, GFE is working just fine with it set to "Apps and ADB right now"

GFE will work fine by wiping app data & initilizing it with a new PIN if you get things cleaned up after a policy violation

No need to get an unlock code from your sysadmins after a policy violation, just wipe app data for GFE & get a new PIN (assuming you have access to a website to request a new PIN

A mini-how to for connectbot:

I prefer this because connectbot is a simple tool and I like to keep it simple. But you may prefer the script manager interface instead.

With connectbot, you can create 2 'local' connections. One for each of the enable/disable scripts appropriately named. You can edit each of the local connections and setup 'post-login automation'. In the post-login automation you add the following (Note that <enter> means to put a line feed... i.e. hit enter :) ):

/system/xbin/dger;exit
<enter>

/system/xbin/egdr;exit
<enter>

You can either open connectbot each time and run the enable or disable scripts or you can add connectbot shortcuts to each local connection on your launcher's desktop. Its under 'add shortcut' you will see connectbot. :)

If you, like me, get annoyed by the notification icon from connectbot, you can optionally do these steps to execute it.

In the connectbot options, disable persistence. Also you can replace the ';exit' in the post automation commands with ';kill $PPID' and that will get you very close a self closing command. That will terminate the shell session you are in. When disabling GFE you'll still have to hit the back button but when enabling GFE it wont stay in your notification bar.

Example:

/system/xbin/dger;kill $PPID
<enter>

The negative is that if there was an issue, you wont see the log. I may add logging support in the scripts so that we can go back and look easier anyway at what failed if we get a lock out. If you ever needed to debug though just remove that temporarily and you'll see the log again.

If you wanted a few seconds to review the log, you could do something like this also:

/system/xbin/dger;[COLOR="Red"]sleep 5[/COLOR];kill $PPID
<enter>

A mini-how to for script manager:

In script manager you will add the scripts into script manager and execute them via the app or it's widgets. The scripts should NOT be setup to run as superuser but they still will prompt for super user when the disable one is actually executed and you should respond GRANT to that request. You will use the app to find the scripts in /system/xbin chosing the following:

/system/xbin/dger

/system/xbin/egdr

FAQ

Q: If I am going to dirty flash a new rom (no data wipe), What do I need to do to keep GOOD in compliance?

A: IT'S LIKE DANCING AROUND A LAND MINE! You will want to follow this process before and after flashing dirty:

Run dger to return root to your device and disable GOOD

Reboot into cwm

Flash rom and do any other rom specific instructions including any reboots or whatever the rom maintainer wants you to do.

Reflash the gfe_workaround zip from the op since flashing the rom overwrites it.

Boot into the rom and set it up as you like with root...

Run disable good enable root.sh to make sure things are well after rom flash.

reboot one last time

use scripts as normal

Q: If I am going to clean flash a new rom (wipe data), What do I need to do to keep GOOD in compliance?

A: Clean Flashing will require you to restore the good app or jsut reactivate it. You can likely avoid reactivation by following this. YMMV

Run dger to return root to your device and disable GOOD

Use Titanium Backup (or similar like carbon) to backup the GOOD app and data.

Reboot into cwm

Flash rom and do any other rom specific instructions including any reboots, wiping data/system or whatever\ the rom maintener wants you to do.

Reflash the gfe_workaround zip from the op since flashing the rom overwrites it.

Boot into the rom and set it up as you like with root...

Restore GOOD with Titanium. You may need to also restore your android ID with titanium as I am not sure if it hashes that ID with activation credentials.

Immediately run dger BEFORE REBOOTING to make sure things are well after rom flash.

Ensure you redisable any permissions denied things and autostarts.

reboot one last time

use scripts as normal

DEBUGGING PROCESS

So you've experienced a policy break/lockout? Now what?? :) This is how you can debug and give me what I need to help you if required:

flash newest scripts in OP and boot up and let it settle.

run the disable good script.

run enable good script.

run disable good script again.

That will create log files in /sdcard/ with the same names as the scripts. You can review those or submit them to me in this thread and I can look. I will also need the following. I review these files to see if there are any 'other' superuser or supersu apks that my scripts have missed. I will need the /sdcard/gfe.txt after you run the below to assist posted in the thread.

Run the following commands in a connectbot shell after above:

Code:

su
find /system/app /data/app /system/bin /system/xbin|sort > /sdcard/gfe.txt
pm list packages >> /sdcard/gfe.txt

Then give me these following logs:

/sdcard/gfe.txt

/sdcard/egdr.......log

/sdcard/dger.......log

Some of the most common reasons for lockouts are because of the running of certain root apps prior to enabling good. Certain root apps still retain root access after you close them. Notably es explorer and titanium. I'm sure there are others but this is two that I know of. If you use those tools either disable root access in them if applicable or reboot before running good after using them.

Change log

04-20-2013 (v16):

Renamed scripts and binary

04-03-2013 (v16):

Added "script complete" messages to output.

04-02-2013 (v15):

Added command line option to turn off auto-launch of GFE. The default will remain to auto-launch it.

04-01-2013 (v14):

Went back to sparky su as other su is causing too many anomolies.

FAQ added to OP.

02-26-2013 (v13):

Removed execution speed enhancement introduced in v11 as it caused some issues.

02-22-2013 (v12):

Further improved Logging to sdcards

Added some enhancements and termination of some root apps(titanium)

02-14-2013 (v11):

Improved script execution speed by parallelizing some operations

Added logging to /sdcard if available

02-04-2013 (v10):

Changed the way I handled superuser apps (or multiples) stored in data and system.

Added ability to handle chainfire's nonag apk in addition to regular supersu.

Started using supersu's su for a more secure setup.

Revamped directions and cleared up some errors in the OP.

01-29-2013 (v9):

added new mask for apk

added error handling for mounts incase.

01-25-2013 (v8):

reversed order of hiding apks between system/data to resolve

issue of supersu/superuser "forgetting" settings when rerooting.

12-18-2012 (v6):

added supersu support

fixed left over apks from super app upgrades

12-14-2012 (v3):

Added clean exit commands.

12-13-2012 (v2):

- Discovery that new script manager may cause compliance issues and doesn't work after temp unrooting!

12-12-2012 (v1):

- Fixed bugs

- Automated variables

- Created flashable setup script

- Simplified the install process

12-10-2012 ():

- Initial design