yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Phantasm4489:
You are fine to reboot.The only things that will cause you trouble is when the xposed framework gets disabled or the module itself gets disabled, so flashing a new Rom, upgrading the xposed framework or upgrading the module. If you don't freeze the good client during this process it will detect root as it constantly checks in the background. Simply rebooting won't cause a problem. The xposed stuff will all be running by the time the app starts scanning for root.
[Android Software/Hacking General [Developers Only]] dabrowsk:
If you have it installed and activated it is for sure safe.
[Android Software/Hacking General [Developers Only]] CannibalAngel:
Thank you both!
[Android Software/Hacking General [Developers Only]] JHoffmann:
DETECTED!

Detected this morning.

Good for Enterprise v.2.6.0.376

Good Access v.2.0.74.301

Xposed (installer?) v.2.6.1

This module v.3.1

LG G3

Android 4.4.2

Kernel 3.4.0

Build KVT49L.LS990ZV4
[Android Software/Hacking General [Developers Only]] vivelafrance:
taht's because you're using the Xposed module that's not working! Dev is working on a new one. A link is even a few pages back to download it. Not in the Xposed reporitory yet so it doesn't show.
[Android Software/Hacking General [Developers Only]] taxi333:
Any idea why this new update only works on stock ROM on N5 or other devices? Any way to workaround ? Maybe a build.prop modification on a custom ROM?
[Android Software/Hacking General [Developers Only]] techepet:
Looks like new Xposed Framework module apps make good crash, only option is to completely disable and unsinstall xposed framework.... stay away from 54 and 58, also when trying to install this patch on this latest version it hangs installing.
[Android Software/Hacking General [Developers Only]] scoobwrx:
Must have had corrupted download before. Was able to install fine but getting the force close on my custom 4.4.4 Dirty Unicorns ROM for HTC one. I'm currently using version 3.3alpha posted by Phantasm.
[Android Software/Hacking General [Developers Only]] javaguy110:
All is working well for me with everything current. Latest Verizon M8 update, latest GFE and latest .apk posted earlier in this thread. Had to reprovision, but that was because of my own boneheadedness.

Sent from my Gunmetal Grey M8
[Android Software/Hacking General [Developers Only]] Phantasm4489:
Can you all please post details of what phone and what Rom you are running and if it works or not so we can try to figure out why it works for some and not others
[Android Software/Hacking General [Developers Only]] techepet:
Did you update the latest xposed framework?

It was working fine for me using stock Moto X 4.4.4 rooted with previous Xposed Framework. But now with version 58 it crashes the good app. But this has nothing to do with the GFE module which was working perfect. Hope they update xposed framework to solve this crashes.

This is the thread I created reporting this error.

http://goo.gl/kALYT6
[Android Software/Hacking General [Developers Only]] javaguy110:
I'll update your other thread too, but my app process is 58 and bridge is 54.

Sent from my Gunmetal Grey M8
[Android Software/Hacking General [Developers Only]] techepet:
I just tried IT on my lg g2 running cyanogenmod 11 m10. As long as I don't install xposed framework good works fine, I am even using a policy that allows root and custom rom, but the moment I install framework and reboot good keeps crashing. With or without this gfe module . Sight...
[Android Software/Hacking General [Developers Only]] nutttr:
Annoying. On the latest Good and the v3.2 module it keeps telling me I'm not in compliance :( Tried twice too :)
[Android Software/Hacking General [Developers Only]] Phantasm4489:
in order to try and figure out whats going on with this ive added some more logging to the xposed module and attached it.

This one works in the same way as 3.2 so it should give the same results but it logs the following things to the xposed log

1) the compliance settings that came from the server

3) the stack trace when it returns to the desktop out to try and see what code is causing it to shut down

hopefully this should help to track down where the inconsistencies are with this.

Attachment REMOVED!!! See later post
[Android Software/Hacking General [Developers Only]] techepet:
[MENTION=2505474]Phantasm4489[/MENTION]

First thanks for the help!!! ok here is the log result,

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method call com.good.common.util.i intercepted

stack trace: java.lang.RuntimeException: xposed exception thrown

at com.phantasm.xposed.gfesecuritypatcher.GfeHook$2.beforeHookedMethod(GfeHook.java:323)

at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)

at com.good.common.util.i.a(Native Method)

at com.good.common.util.i.b(GFE:105)

at com.good.android.gfe.service.syncengine.jni.JNISyncEngine$ReceiverLoop.run(GFE:769)

at java.lang.Thread.run(Thread.java:841)

Loaded app: com.good.android.gfe

class found : g.ahp$aX

probable decryption method found : aK

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.cs found

method call to g.ahp->a intercepted - returning 0

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method call com.good.common.util.i intercepted

stack trace: java.lang.RuntimeException: xposed exception thrown

at com.phantasm.xposed.gfesecuritypatcher.GfeHook$2.beforeHookedMethod(GfeHook.java:323)

at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)

at com.good.common.util.i.a(Native Method)

at com.good.common.util.i.b(GFE:105)

at com.good.android.gfe.service.syncengine.jni.JNISyncEngine$ReceiverLoop.run(GFE:769)

at java.lang.Thread.run(Thread.java:841)
[Android Software/Hacking General [Developers Only]] Phantasm4489:
ok thats useful. i can see the stack trace - the server settings arent showing though :(

Ive attached an updated module to try - hopefully this one should log all the details.
[Android Software/Hacking General [Developers Only]] techepet:
Great no problem! Here you go new log using latest patch.

method call com.good.common.util.i intercepted

stack trace: java.lang.RuntimeException: xposed exception thrown

at com.phantasm.xposed.gfesecuritypatcher.GfeHook$2.beforeHookedMethod(GfeHook.java:323)

at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)

at com.good.common.util.i.a(Native Method)

at com.good.common.util.i.b(GFE:105)

at com.good.android.gfe.service.syncengine.jni.JNISyncEngine$ReceiverLoop.run(GFE:769)

at java.lang.Thread.run(Thread.java:841)

Loaded app: com.good.android.gfe

class found : g.ahp$aX

probable decryption method found : aK

class found : com.good.android.compliance.ComplianceManagerPolicy

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method hook - g.cs found

method call to g.ahp->a intercepted - returning 0

method hook - g.ahp found

security method located via method scan - return type int

method hook g.ahp->a hooked

method call com.good.common.util.i intercepted

stack trace: java.lang.RuntimeException: xposed exception thrown

at com.phantasm.xposed.gfesecuritypatcher.GfeHook$2.beforeHookedMethod(GfeHook.java:323)

at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:611)

at com.good.common.util.i.a(Native Method)

at com.good.common.util.i.b(GFE:105)

at com.good.android.gfe.service.syncengine.jni.JNISyncEngine$ReceiverLoop.run(GFE:769)

at java.lang.Thread.run(Thread.java:841)

Loaded app: com.good.android.gfe

class found : g.ahp$aX

probable decryption method found : aK

class found : com.good.android.compliance.ComplianceManagerPolicy
[Android Software/Hacking General [Developers Only]] hiyachi-32:
It doesn't work on xxu1ang3 freemwork on s5 xtrolite rom :/
[Android Software/Hacking General [Developers Only]] Phantasm4489:
in what way does it not work? does it detect root or does it simply crash out?

can you use the most recent module attached a few posts back and include the relevant bits from the xposed log.

---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------

this looks incomplete :(
[Android Software/Hacking General [Developers Only]] scoobwrx:
https://www.dropbox.com/s/uwzvtqfi6cqcfsh/xposed_error_20140923_122423.txt?dl=0

I'm getting the force close when trying to open GFE. Linked to my xposed log to hopefully help diagnose the issue. Not sure if good is detecting root or not since it FC.
[Android Software/Hacking General [Developers Only]] Surfinette:
I've tried to use Good v2.6.0.376 with your xposed module.

But I'm blocked because root is detected. However, I can see in the status bar that GFE is downloading my emails and syncing the contacts...But this is useless because I can't open GFE and can't have access to its ui

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Android Software/Hacking General [Developers Only]] esc247:
Firstly thanks for your work OP. [MENTION=2505474]Phantasm4489[/MENTION]

I got the 3.3Alpha patch working on my device. I am using an LG G2 D802 (on Pardus HD Sensation Black v3.2). I have RootCloak and AppSetting (with Get_tasks revoked) installed as well, so am not sure if the combination got it to work. Hope this info helps :)

Cheers!
[Android Software/Hacking General [Developers Only]] techepet:
Oh BTW I am using cyanogenmod 11 not stock os. Rgds
[Android Software/Hacking General [Developers Only]] ombheembush:
What's this AppSetting you are referring to? I didn't find that in the AppOps on PA Rom
[Android Software/Hacking General [Developers Only]] esc247:
You can find appsettings in xposed. It's a module available for download.
[Android Software/Hacking General [Developers Only]] ombheembush:
Thanks, I will try that.
[Android Software/Hacking General [Developers Only]] Ignite023:
Running LG G3 - tried with version 3, but root was still detected by the application. Moved to the alpha version on the previous page, and it works fine now.
[Android Software/Hacking General [Developers Only]] techepet:
Stock or custom rom?
[Android Software/Hacking General [Developers Only]] taxi333:
any way of running the same app session on different roms? Im using multirom in a N5. I have tried the following:

- Restore app+data using TB (stops syncing)

-Restore app + data + restored device ID using TB (stops syncing)

How would I accomplish this?
[Android Software/Hacking General [Developers Only]] anoraknophobia:
Install it again an get a new activation key. You can't backup Good.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

Try the v9 version. I added a mask to catch the apk I missed according to you files.
[Android Software/Hacking General [Developers Only]] wc4482:
Re: Good for Enterprise ( GFE ) root workaround

I happen to be in the process of wiping completely clean. I'll give v9 a shot, Thanks.

Question: is there a safe way to check for root after running your scripts? I think I got in trouble for opening titanium and root explorer when I was trying to reproduce an issue
[Android Software/Hacking General [Developers Only]] sabinn:
I tested v9 but had no joy. However, during Good's provisioning process it seemed to take a very long time. As if it was timing out. After several minutes the app closed, auto re-opened, and gave me a non compliance dialog.

I took the liberty of taking fresh ss's and running the output txt files your review. If you're willing of course. Pretty please? ;]
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

Few Qs. Are you using script manager from market or the op? Did you run any root like apps before trying activation again? (trying to narrow what's getting flagged) Did you have adb or connectbot running before trying? I know it can search running processes for open su shells.

Try one more after a fresh boot. So run the reroot script. reboot. Then let it boot and settle. Then run the unroot/launch good script.

I know htcs have boot loaders that need to be unlocked. I wonder if it is able to tell its been unlocked. I need to research a bit on that.
[Android Software/Hacking General [Developers Only]] wc4482:
I reflashed my rom from scratch. I mean complete clean install (even formatted sdcard and internal memory. And the Policy compliance still found root.

I noticed that SuperSU had an update in the playstore. I'm going to freeze Good and wipe data and try to uninstall updates on superSU.

EDIT: Update! Great Success!

Got v9 working on my phone, I think I found my problem. When I rooted and unlocked my VZW Note 2, it came with TWRP and SuperSU v0.99. Everytime I flash it puts that same version (v0.99) of SuperSU Back on, and when I open the play store, it wants me to upgrade SuperSU V1.01. I usually do but I think this caused two .apk's to download. I noticed the script was hiding and unhiding SuperSU-1.apk (instead of just SuperSU.apk) and the temp un-root was not actually taking. I assume the old v0.99 apk was still sitting out there and Good was detecting the old version.

Long story short I have to make sure I never update the SuperSU or i'll likely get flagged again. Means I can't ever hit update all in the play store :/
[Android Software/Hacking General [Developers Only]] sabinn:
I got it working!

installed/reinstall script manager from OP

removed Titan Backup and Pro license (force close/disable/clear data/uninstall)

removed GFE (force close/disable/clear data/uninstall)

REBOOT

provisioned a fresh GFE key using my corporate portal

reinstalled GFE from Google Play

ran enable_good_disable_root.sh

TADA!

My man! Thank you so much :)
[Android Software/Hacking General [Developers Only]] calisro:
I had that happen with the new supersu oddly enough. But then when I tried to debug it it now works. Not sure why. I did notice that after installing the new supersu that the remounting of my /system file system read only failed and Good will detect a RW /system file system. Not sure if that was the issue or not. I added some error checking before unfreezing good incase the mount as RO fails. The new version (v9) in the op.

If you do get a policy break using the new v9, post the output of the above commands to see if I am missing a mask for the new supersu. As I said its now working again for me.....
[Android Software/Hacking General [Developers Only]] calisro:
Awesome. This tells me that Good can't check unlocked boot loaders on HTC devices. :)

It is probably the case that you had titanium still running when you tried last time. If I work with some root tools like titanium or es explorer in root mode, I'll usually do a quick reboot before unrooting/running good. I have them installed and just having them installed doesn't matter. Maybe i'll put some logic in the script to terminate titanium if its running just to be safe. (in v10)
[Android Software/Hacking General [Developers Only]] wc4482:
See my edited message above. I'm gonna stick with the old SuperSU app. Any reason to upgrade? I wonder if my problem is identical to yours?

I was using v9 when it failed but my company makes it hard to get a new license so I don't really want to test with 1.01 and find out.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

I'll try testing it. My key for gfe can be reused as many times as I need. I'm surprised yours expires?...
[Android Software/Hacking General [Developers Only]] wc4482:
Yes it expires after one or two weeks and they make you call IT to get a new one. I found out today that if your app fails the policy check more than once or twice in short duration they void you server side and make you get a account via another IT phone call. Seems expensive - don't they have to pay for each license?
[Android Software/Hacking General [Developers Only]] calisro:
They pay per license but only active licenses. Once they invalidate yours it goes back to the pool of licenses.

EDITED: I didnt have the new supersu installed like I thought I did. I just upgraded and I couldnt get good to activate with both the new and old supersu (it will keep the older one on the rom).
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

okay. So the version of supersu isn't the issue at all. I am running 1.0.2 now. The issue seems to be having one original apk in system that came with the rom and the newer updated apk in /data.

If you copy the newer version from data to system and then delete the others it works fine. It must have something to do with how I remove both. I'll research it.
[Android Software/Hacking General [Developers Only]] storm_chaser:
thanks for this useful information. Especially regarding licenses.
[Android Software/Hacking General [Developers Only]] Zirillian:
Does anyone have any experience running GFE on a tablet? I have GFE running on my Nexus 7 just fine, rooted with CM10.1 nightlies and a custom kernel. It hasn't flagged me once for noncompliance and I haven't done anything in this thread. I'm wondering if GFE is not checking for compliance on the tablet for some reason, although that doesn't make much sense since I'm sure the Nexus 7 is set up the same way as my Nexus 4 as far as internal folder structure.

I've been really wanting to root my N4, but am terrified it'll break compliance and I wouldn't be able to get it back to normal without doing the scripts mentioned in this thread, which seem like they can be a hassle at times. I'm not the type of person that would forcefully shut down Good after I check my work email. Similar to Gmail, I want to know when I get mail at all times (by the notification light or phone vibration), and not have to manually log in and check it.
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise ( GFE ) root workaround

GFE can check for root, but is an optional setting set server side. Your company might not bother checking for root.

I'd highly doubt a tablet would be any different than a phone in root detection.
[Android Software/Hacking General [Developers Only]] calisro:
RE: tablet: I don't think they differentiate. that being said it doesn't detect root on my tablet either... But it also didn't detect root on some of the other phones I have owned. GFE is just a piece of garbage and its detection mechanisms are terrible. I believe that it is simply failing to detect root on some devices. On my epic 4G, for example, I had it detect root on some ROMs and not others for no reason what so ever on the same device. I also had it not detect root on one rom on my E4GT (both phones are samsung devices btw as if that matters).

You should be able to root your N4 and if you run into compliance issues you have a very high probability of reverting it to a state where it doesn't detect root (back to stock or just by removing root (so and apk).

The method in this script is only for people that want to toggle between root and non-root. It, at times, can be a hassle but it is a price to pay for keeping root when I need it.

THere are other ways to handle this. You can use supersu app to run a complete unroot operation where it will remove itself from your device. THen you'd have to reinject root when you need it in recovery by whatever method is appropriate for your phone when you want it. PITA IMHO. :)
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

The new 1.0.4 version of supersu is out. I've successfully upgrade to it with no policy breaks by doing the following:

1) run the disable good enable root script.

2) install from play store.

3) within the settings of supersu, select to install as system app. This option will replace the apk in system with the one from data. i.e. you will only have one and not two apks.

4) done.
[Android Software/Hacking General [Developers Only]] Zirillian:
Advice much appreciated. Welp, I did try rooting my N4 tonight to see what happened...and sure enough, I got flagged immediately. I tried clearing GFE data, uninstalling it, temp unrooting with superuser, reboot, install GFE, input NEW PIN code generated by IT, and now it is saying "This handheld (IMSI:3102605......) has already been set up for another user. Contact your IT administrator.

Kind of at a loss what to do now. Thinking about uninstalling good again, releasing the PIN code/license, and letting it sit overnight...then trying again in the morning. With this going on...I'm not even at a point where I could try your scripts to see if I could deal with having to do that every time to check my mail. Hoping I can figure out this IMSI thing.

Any ideas?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

Never seen that but likely your company may not allow you to reuse pins which sucks. Hopefully your company has a self service website to get another pin otherwise calling you IT will be a pain.

EDIT:If you have trouble getting pins all the time and your one of those people who rarely use root, you can consider what other people do which is to use supersu's option to do a complete unroot then reboot.... Whenever you need root, you can reflash supersu's cwm flashable reroot script again.

That method is slower but will avoid policy breaks more.

In addition I can create a cwm flashable insecure su script that you can always keep on your phone even with good. It doesn't detect it.... that way you can at least get root from connectbot by typing 'spark' instead of su.
[Android Software/Hacking General [Developers Only]] javaguy110:
You know...I saw something in another thread. I can't remember where, but talked about putting Good in offline mode and then backing it up with TiBu. Maybe worth a shot. It said something about how it would stop syncing without putting it offline first.

I found that after trying to back it up before a Verizon update. No guarantee, but maybe. I'm curious of the result of you do try...for future reference.

Sent from my Gunmetal Grey M8
[Android Software/Hacking General [Developers Only]] thehobit:
Xposed compatibity issue with GFE 2.5 and 2.6

It seems that the issue with GFE 2.5 and 2.6 crashing is not a security patch issue but Xposed compatibility issue on custom ROM’s:

I have two configuration:

• N4

• 4.4.4 Stock

• Xposed 2.7

• Security patcher 3.3 alpha

• GFE 2.6

Works perfectly

On another phone:

• Coolpad F1

• 4.4.2 Custom

• Xposed 2.7

• Security patcher 3.3 alpha

Only GFE 2.4 in working, GFE 2.5 and 2.6 are crashing

Here is the important part: my admin was kind enough to disable the security profile o which is detecting root on the Coolpad.

Then, I discovered that the problem is actually the Xposed module and not the patcher.

GFE 2.5 and 2.6 would not work at all if Xposed is installed regardless of any security module (security module uninstalled).

There is a thread about the incompatibility of Xposed and GFE, is but I do not get workable conclusion.

http://xdaforums.com/xposed/enterprise-crashes-xposed-enabled-t2810897/page2

Any hint?