Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,740,872 Members 52,958 Now Online
XDA Developers Android and Mobile Development Forum
View Poll Results: Are you using SUPERSU or SUPERUSER?
SUPERSU 82 83.67%
SUPERUSER 16 16.33%
Voters: 98. You may not vote on this poll

Good for Enterprise (GFE) [03-7-2014] root workaround

Tip us?
 
calisro
Old
(Last edited by calisro; 7th March 2014 at 03:47 PM.)
#1  
calisro's Avatar
Senior Member - OP
Thanks Meter 735
Posts: 1,852
Join Date: Sep 2008
Location: noneya

 
DONATE TO ME
Angry Good for Enterprise (GFE) [03-7-2014] root workaround

This IS working for 4.3+ using xposed module.

http://forum.xda-developers.com/show...&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:
Quote:
************************************************** ************************************************** **********
I AM NOT RESPONSIBLE FOR YOU BEING FIRED BY CIRCUMVENTING THE POLICY YOUR IT STAFF HAS PUT IN PLACE. I AM NOT RESPONSIBLE FOR BRICKING YOUR PHONE (ALTHOUGH SERIOUSLY DOUBT IT COULD POSSIBLY DO THAT). I AM NOT RESPONSIBLE FOR ANY DAMAGE WHAT SO EVER. THIS IS FOR EDUCATIONAL PURPOSES ONLY!!
************************************************** ************************************************** **********
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:
  1. 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
  2. Install Good Application
  3. 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.
  4. 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..
  5. 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 ):
Code:
Select Code
/system/xbin/dger;exit
<enter>
Code:
Select Code
/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:

Code:
Select Code
/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:
Code:
Select Code
/system/xbin/dger;sleep 5;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:
Code:
Select Code
/system/xbin/dger
Code:
Select Code
/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:
  1. Run dger to return root to your device and disable GOOD
  2. Reboot into cwm
  3. Flash rom and do any other rom specific instructions including any reboots or whatever the rom maintainer wants you to do.
  4. Reflash the gfe_workaround zip from the op since flashing the rom overwrites it.
  5. Boot into the rom and set it up as you like with root...
  6. Run disable good enable root.sh to make sure things are well after rom flash.
  7. reboot one last time
  8. 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
  1. Run dger to return root to your device and disable GOOD
  2. Use Titanium Backup (or similar like carbon) to backup the GOOD app and data.
  3. Reboot into cwm
  4. Flash rom and do any other rom specific instructions including any reboots, wiping data/system or whatever\ the rom maintener wants you to do.
  5. Reflash the gfe_workaround zip from the op since flashing the rom overwrites it.
  6. Boot into the rom and set it up as you like with root...
  7. 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.
  8. Immediately run dger BEFORE REBOOTING to make sure things are well after rom flash.
  9. Ensure you redisable any permissions denied things and autostarts.
  10. reboot one last time
  11. 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:

  1. flash newest scripts in OP and boot up and let it settle.
  2. run the disable good script.
  3. run enable good script.
  4. 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:
Code:
Select 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
Attached Files
File Type: zip gfe-v17.zip - [Click for QR Code] (298.9 KB, 882 views)
Samsung Galaxy S5 (Sprint) 900P
Asus Eee pad TF300T [ CM ]
The Following 36 Users Say Thank You to calisro For This Useful Post: [ Click to Expand ]
 
calisro
Old
(Last edited by calisro; 28th February 2013 at 06:06 PM.)
#2  
calisro's Avatar
Senior Member - OP
Thanks Meter 735
Posts: 1,852
Join Date: Sep 2008
Location: noneya

 
DONATE TO ME
The 'manual' process may not work anymore. I believe supersu apks are getting picked up for compliance. There are a few more manual ways listed in this thread that may or may not work for you but you are welcome to try them.


MANUAL PROCESS
 

If the script process is too complicated for you and you want to do things manually, you can do this as well. It is a pain though and more prone to getting the handheld disabled by good because of user error (forgetting to do something).

The key to this way is that gfe doesnt appear to detect supersu apk and does detect superuser apk. Not sure how long this will last! ymmv

You can install supersu, open it and let it authorize. Then rename /system/app/Superuser.apk to super_user.rob since its not needed anymore and let supersu do the authorizations.

Then install "app quarantine" from the market or titanium backup. These apps let you freeze and unfreeze the gfe app so you can bounce between a rooted and unrooted phone. (hint: there are widgets for this in titanium and app quarantine that are much more convenient)

If pre_JB, Install "permissions denied" (in app store) to remove the some of the permissions from the app. specifically you must remove
READ_LOGS

The process is as follows once the above is complete and gfe is installed and you want to use gfe:

FROST GFE(reroot)
  1. open gfe and go into preferences and select "disconnect" and then select shutdown good. VERY IMPORTANT TO DISCONNECT AND SHUTDOWN from within the GOOD app. Do NOT just hit the 'HOME' button and reroot. It WILL detect that it has been frosted and unfrosted if you do not follow this advice
  2. immediately open supersu app and go to settings and select "enable supersu" to reenable root.
  3. open app quarantine (or titanium) and freeze good so it won't autostart.
You can now use the rooted phone like normal.

when you want to use gfe, temp unroot as follows:
UNFROST GFE(temp unroot)
  1. using titanium or app quarantine defrost gfe.
  2. immediately open supersu and go to settings and uncheck "enable supersu". the will hide the su binary and temp unroot.
  3. open gfe and use it like normal.
once done using gfe, refrost it like above

this works very well but ymmv. The scripted method works much better.
Samsung Galaxy S5 (Sprint) 900P
Asus Eee pad TF300T [ CM ]
The Following 5 Users Say Thank You to calisro For This Useful Post: [ Click to Expand ]
 
Fallon
Old
(Last edited by Fallon; 10th December 2012 at 04:35 PM.) Reason: Added link to old stuff
#3  
Senior Member
Thanks Meter 41
Posts: 278
Join Date: Jan 2007
Location: Parker
Finally had success getting GFE running a recent CM10 nightly on my AT&T SGS3 thanks to calisro. Thanks for figuring out a good work around to enable GFE! It looks like my issues this go around were with Permissions Denied & me doing some uninstall-re-install of GFE.

My process (tweaks to calisro's stuff mostly):
  1. Uninstalled ES explorer (just to make sure it is not causing issues for now)
  2. Installed GFE
  3. Installed Script Manager (I've since upgraded to Script Manager-SManager(NoAds), always a good idea to support the devs)
  4. Installed Permissions Denied
  5. Installed su as /sdcard/rob_su
  6. Opened Permissions Denied and disabled the following permission for the Good Application: READ_LOGS and RECEIVE_BOOT_COMPLETED
  7. Rebooted from within Permissions Denied, checked & verified Good had the 2 permissions in question denied
  8. Created the 3 scripts using the updated versions recently posted
    • setup_rootdoor.sh
    • enable_good_disable_root.sh (complete with the missing final line noted above)
    • disable_good_enable_root.sh
  9. With Script Manager, ran setup_rootdoor.sh
  10. Deleted all data for GFE through app manager
  11. With Script Manager, ran enable_good_disable_root.sh
  12. Activated GFE
  13. Working GFE

Notes:
  • Permissions Denied takes FOREVER to startup, several minutes at least & you repeatedly see it getting root permissions, at first I thought it was having issues, but I guess that's normal behavior
  • No need to "Lock Permissions" within the Permissions Denied app from what I've seen
  • Under Developer Options "Root access" is irrelevant, GFE is working just fine with it set to "Apps and ADB right now"
  • GFE seems to be sucessfully cleaned up by deleting app data from within app manager
  • GFE will work fine by wiping app data & initializing 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
  • Logs & thoughts from of my previous failures & troubleshooting steps http://forum.xda-developers.com/show...95&postcount=5
__________________
Samsung Galaxy S 3 (AT&T)
Some CyanogenMod recent 11 nightly probably
__________________
Asus Transformer 16GB
CyanogenMod 10 derivative

Now retired:
Samsung Captivate - CyanogenMod 9
The Following 2 Users Say Thank You to Fallon For This Useful Post: [ Click to Expand ]
 
calisro
Old
#4  
calisro's Avatar
Senior Member - OP
Thanks Meter 735
Posts: 1,852
Join Date: Sep 2008
Location: noneya

 
DONATE TO ME
Quote:
Originally Posted by Fallon View Post
Finally had success getting GFE running a recent CM10 nightly on my AT&T SGS3 thanks to calisro. Thanks for figuring out a good work around to enable GFE! It looks like my issues this go around were with Permissions Denied & me doing some uninstall-re-install of GFE.

My process (tweaks to calisro's stuff mostly):
  1. Uninstalled ES explorer (just to make sure it is not causing issues for now)
  2. Installed GFE
  3. Installed Script Manager (I've since upgraded to Script Manager-SManager(NoAds), always a good idea to support the devs)
  4. Installed Permissions Denied
  5. Installed su as /sdcard/rob_su
  6. Opened Permissions Denied and disabled the following permission for the Good Application: READ_LOGS and RECEIVE_BOOT_COMPLETED
  7. Rebooted from within Permissions Denied, checked & verified Good had the 2 permissions in question denied
  8. Created the 3 scripts using the updated versions recently posted
    • setup_rootdoor.sh
    • enable_good_disable_root.sh (complete with the missing final line noted above)
    • disable_good_enable_root.sh
  9. With Script Manager, ran setup_rootdoor.sh
  10. Deleted all data for GFE through app manager
  11. With Script Manager, ran enable_good_disable_root.sh
  12. Activated GFE
  13. Working GFE

Notes:
  • Permissions Denied takes FOREVER to startup, several minutes at least & you repeatedly see it getting root permissions, at first I thought it was having issues, but I guess that's normal behavior
  • No need to "Lock Permissions" within the Permissions Denied app from what I've seen
  • Under Developer Options "Root access" is irrelevant, GFE is working just fine with it set to "Apps and ADB right now"
  • GFE seems to be sucessfully cleaned up by deleting app data from within app manager
  • GFE will work fine by wiping app data & initializing 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
  • Logs & thoughts from of my previous failures & troubleshooting steps http://forum.xda-developers.com/show...95&postcount=5
FYI, I simplified the install with a flashable zip and some modifications to the scripts so that the work they do is dynamic rather than hard coded.
Samsung Galaxy S5 (Sprint) 900P
Asus Eee pad TF300T [ CM ]
 
calisro
Old
(Last edited by calisro; 8th February 2013 at 12:54 AM.)
#5  
calisro's Avatar
Senior Member - OP
Thanks Meter 735
Posts: 1,852
Join Date: Sep 2008
Location: noneya

 
DONATE TO ME
Discovered that the new Script Manager is potentially causing policy compliance issues. See the op for alternative or older version of script manager.
Samsung Galaxy S5 (Sprint) 900P
Asus Eee pad TF300T [ CM ]
 
Fallon
Old
#6  
Senior Member
Thanks Meter 41
Posts: 278
Join Date: Jan 2007
Location: Parker
Quote:
Originally Posted by calisro View Post
Discovered that the new Script Manager is causing policy compliance issues. See the op for alternative or older version of script manager.
Does it only trip when you use it? I think I saw Script Manager update a couple days ago, but haven't had any problems yet. Then again I haven't needed to mess with SM at all since then or even engage root for anything since I got GFE working on CM10 a week or so ago.
__________________
Samsung Galaxy S 3 (AT&T)
Some CyanogenMod recent 11 nightly probably
__________________
Asus Transformer 16GB
CyanogenMod 10 derivative

Now retired:
Samsung Captivate - CyanogenMod 9
 
calisro
Old
(Last edited by calisro; 13th December 2012 at 04:52 PM.)
#7  
calisro's Avatar
Senior Member - OP
Thanks Meter 735
Posts: 1,852
Join Date: Sep 2008
Location: noneya

 
DONATE TO ME
I'm having it fail compliance by simply having it installed. I've gone through and upgraded, tested, downgraded, tested, etc for a number of times to be sure and it keeps tripping as soon as it is used once. I've even installed it,denied superuser for the app, then used connectbot to actually run the script and it still failed. As soon as I go back to older version it works flawlessly again.

I'll be interested if yours' trips when toggle root and good once again.
Samsung Galaxy S5 (Sprint) 900P
Asus Eee pad TF300T [ CM ]
 
blackspp
Old
#8  
blackspp's Avatar
Senior Member
Thanks Meter 60
Posts: 548
Join Date: Dec 2010
Location: Amsterdam
De easiest way to perform tasks that require root is to use chainfire's exynos exploit apk to acquire root and when you're done use supersu to unroot.

Make sure you stop de GFE service before rooting! I just did this and GFE really stops working as I rooted, cleaned up my new polish Note 2 4.1.2. rom, unrooted, booted and used GFE like before, no policy violations.

Whatever you do, do not boot before you unrooted.
Linux forever!

b l a c k S P e c i a l s
 
calisro
Old
(Last edited by calisro; 20th December 2012 at 08:20 PM.)
#9  
calisro's Avatar
Senior Member - OP
Thanks Meter 735
Posts: 1,852
Join Date: Sep 2008
Location: noneya

 
DONATE TO ME
Quote:
Originally Posted by blackspp View Post
De easiest way to perform tasks that require root is to use chainfire's exynos exploit apk to acquire root and when you're done use supersu to unroot.

Make sure you stop de GFE service before rooting! I just did this and GFE really stops working as I rooted, cleaned up my new polish Note 2 4.1.2. rom, unrooted, booted and used GFE like before, no policy violations.

Whatever you do, do not boot before you unrooted.
I wouldn't call that the easiest but to each their own.

While that may work for some people for a short time, it doesn't address a lot of things:
1) Doesn't work with superuser since Good detects the superuser apk and doesn't detect supersu yet. Detection of supersu will be added to Good at some point since its use is being coming more prevalent.
2) That exploit will be addressed soon since it affects millions of hand sets. Samsung will close the exploit and AOSP/AOKP will also address the exploit. So it will be useful for a short time only.
3) It only works for Samsung exynos based handsets only. My method is generic.
4) Requires reboots to bounce back and forth between root and unroot. Would be tiresome to do this many times a day.
5) if you reboot while your rooted, you'll get policy breaks.
Samsung Galaxy S5 (Sprint) 900P
Asus Eee pad TF300T [ CM ]
 
IT Rider
Old
#10  
Senior Member
Thanks Meter 42
Posts: 154
Join Date: Nov 2006
Location: Chicago Area
v6 works great. the new method of CWM installation of scripts makes it very easy. i used the free autorun app "autorun manager" to disable the receiver flags of GFE.

the only annoyance that really is not bad is that when GFE is disabled, the shortcuts/widgets i have are removed since the app is hidden. a very acceptable price to pay considering my company has the "root" compliance turned on. this at least gives me access to email w/o rebooting when needed.

Thanks for all the work!

The Following User Says Thank You to IT Rider For This Useful Post: [ Click to Expand ]
Tags
gfe, good for enterprise, root check, unroot
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes