yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] El Ha$on:
Hmm not entirely sure then what could be the issue.

I saw root cloak has lollipop support and that GFE was included as a default app for cloaking. But I haven't tried it. Getting pins on my end isn't that simple.

My only recommendation is just getting a different apk to install. A few post earlier I laid out my steps for another user and I think the link still works which included GFE 2.7 and Xposed 3.5, perhaps this helps. The only thing that's changed from that post is that I'm using official Xposed framework as opposed to romracers.

http://xdaforums.com/showthread.php?p=6251465
[Android Software/Hacking General [Developers Only]] ProFragger:
Thanks again for your prompt response! I heard RootCloak for LP is out, but it's for testers only? Not sure where to get the APK and try it out?

I am in the process of trying your guide again, with the included link for 2.7.1 something, let's see if magic happens. Which version are you running on your phone right now?

I tried an older version 2.2 or something really old... caught my Root right away with the patch installed! Got me in trouble, but also surprised me too! If you have older APKs that work, please do share, I appreciate it!
[Android Software/Hacking General [Developers Only]] El Ha$on:
I have GFE version 2.7.1.390 which is the link I had posted.

I got the rootcload apk from the Xposed installed app, just need to change the Versions to be shown as there isn't a stable build yet for root cloak. But I removed GFE from root cloak as I didn't want to interfere with the module from this thread.
[Android Software/Hacking General [Developers Only]] ProFragger:
Yeah, 2.7.1.390 is what I have always used. It keeps failing now, seems like it's probably not getting the Root permissions it needs? Do you have anything older than 2.7.1.390 lying around?

Wonder what version of Good I'd test RootCloak with, if I can get a hold of it...
[Android Software/Hacking General [Developers Only]] El Ha$on:
Unfortunately I do not. Sorry.

Here is root cloak. Not sure which GFE version to try with it. But I would say it would be amazing if it supported the newest version of GFE...right?

http://repo.xposed.info/module/com.devadvance.rootcloak2
[Android Software/Hacking General [Developers Only]] ProFragger:
Can confirm that Good for Enterprise (v2.7.1.390) on LG G4 H810l (AT&T) Android 5.1 failed with RootCloak 1.5.1 Beta, and crashes Good for Enterprise security patch v3.5 with a loop of "Good for Enterprise has stopped working..."

[MENTION=1201880]calisro[/MENTION], [MENTION=2505474]Phantasm4489[/MENTION], and [MENTION=2804938]devadvance[/MENTION] - Is there ANY chance you could please return to development of this AMAZING app to help unlucky users like me keep getting our corporate emails, while keeping our Root as well? Please guy :P!???
[Android Software/Hacking General [Developers Only]] munchee:
Workaround on arm v8?

I hope I'm in the right forum asking this. Recently changed my phone from an arm v7 to arm v8 architecture.

I've been using Lollipop 5.1 with Xposed and GFE root blocker module and Good V2.7.1.390 on the old phone and it's been working just fine.

After moving to a new phone, Good crashed every time launched when the XPosed module is enabled. It ran fine without the xposed module.

Looking a bit at the log, getting the following error:

09-22 13:44:45.366 E/art (28222): dlopen("/data/app/com.good.android.gfe-1/lib/arm/libsyncengineradio-lib2.so", RTLD_LAZY) failed: dlopen failed: "/data/app/com.good.android.gfe-1/lib/arm/libsyncengineradio-lib2.so" is too small to be an ELF executable: only found 0 bytes

Have anyone else seen this? Is this a compatibility issue between 32-bit to 64-bit during runtime of the module perhaps?
[Android Software/Hacking General [Developers Only]] xaueious:
Not sure why my phone acts differently than everyone else's

Can someone with the app installed help me check: if libsyncengineradio-lib.so libsyncengineradio-lib2.so have the same contents?

My phone for some reason has a 0 byte libsyncengineradio-lib2.so when I try to run it, so I can't get it to work

/data/app-lib/com.good.android.gfe-1
[Android Software/Hacking General [Developers Only]] munchee:
[MENTION=2221071]xaueious[/MENTION], thank you for the suggestion. The lib file really is at 0 bytes, and I copied over the libsyncengineradio-lib.so to libsyncengineradio-lib2.so as you suggested, and that seemed to work.
[Android Software/Hacking General [Developers Only]] ProFragger:
Hi [MENTION=4931919]munchee[/MENTION] - there is some good news in your bad news. If you see my last few posts in this thread, I can confirm the same behavior as yours, on my LG G4, which, a you suspected, is a 64bit phone, and like you, my previous phones, Note 3, LG G3 and etc, this module used to work like a charm. I believe my friend [MENTION=3515213]Nowak4G[/MENTION], has confirmed the same behavior on his LG G4. Can I ask you which phone you are using.

I am not expert at reading logs, but looking at some Xposed logs, the patch is clearly not able to hook successfully to a few methods within Good. Not sure if this is a limitation of the new Xposed framework. Limitation is a bad word, but a change perhaps? Or if it's an issue with supersu not providing the correct provisioning to Good, but I suspect the former.

If you confirm your phone is not an LG G4, then I think it's safe to conclude that this module needs updating for the 64bit architectures and Xposed. Not sure who could help with that. I have reached to [MENTION=2505474]Phantasm4489[/MENTION] a bunch of times via thread mentions and a PM, but I don't believe he has the time to pick this back up again. One ray of hope could be the RootCloak development being picked up again, but again, no word from [MENTION=2804938]devadvance[/MENTION] either and not sure about [MENTION=1201880]calisro[/MENTION] either :'(!

One other thought I had was to use an alternative root provisioning app than super su, but if it's checking for Xposed as well, we may be screwed again :(...

Hoping someone smart can help us :'(!
[Android Software/Hacking General [Developers Only]] munchee:
My phone is OnePlus 2, so I agree this seemed to be a 64-bit issue.

There is a work around though, and it works. Thanks to [MENTION=2221071]xaueious[/MENTION] suggestions, if you open a file explorer, navigate to /data/app/com.good.android.gfe-1/lib/arm directory, then copy libsyncengineradio-lib.so to libsyncengineradio-lib2.so on that same directory (overwrite the existing file), then Good will work again.

BTW, that's all with Good version 2.7.1.390

Hope that helps.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

You're very welcome.
[Android Software/Hacking General [Developers Only]] calisro:
V11 update

New version up. It is a minor enhancement. This update:

- Adds logging to the /sdcard if that file system is found.

- Speeds up execution of the script by parallelizing some of the operations in the background.

It is a minor update so update if you wish to have those features but v10 will work just as well but a little slower and without logging. :good:
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise ( GFE ) root workaround

Updated to the latest CM nightly after disabling Good. It went fine except the update deleted the scripts. Re-flashing the .zip got things back on track. I didn't even need a new PIN, Good just half reinstalled itself & worked.

Will update to the v11 here soon.
[Android Software/Hacking General [Developers Only]] IT Rider:
I checked the OP and didn't see v11 available for download. Did I miss the link somewhere? I see the change log posted. Thanks! This scripting has been a phone saver for me at my job.

Thanks again for all the work.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

I must have not hit "save". weird. I reattached. thx for bringing to my attention.
[Android Software/Hacking General [Developers Only]] mb:
YMMV but using Root Explorer to execute the disable root script works really well for me. I don't need anything else. Simply rebooting restores root in my experience. i just have to remember to disable sync and exit Good fully before I restart my SGS2 to get root goodness back.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

yea some roms reroot on reboot. Make sure you use something like permissionsdenied to disable good auto start on reboot to prevent policy breaks.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

I've switched back to stock rom for now. I'm using stock unrooted rom after three years. It sucks but I'll have to live with it...
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

I could have gotten you all set up if you would have given me logs to work with. oh well.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

Ok I cannot be on the stock rom. I despise it.

I'll be switching to paranoid android and will be restarting the whole process. I may be seeking your assistance if needed. Thank you so much for being available.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

I am on the latest paranoid android rom. Gonna try this now. Fingers crossed.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

Tried everything over again... Didn't work.
[Android Software/Hacking General [Developers Only]] calisro:
It's hard for me to fix "it didn't work". :D

get me this data (run in connectbot or adb or similar and post gfe.txt from /sdcard after).

su
find /system/app /data/app /system/bin /system/xbin > /sdcard/gfe.txt

also post a screen shot of sm manager or connectbot or however your running the scripts after running each script from the op.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

Thanks for being so cooperative...

As soon as I was using disable root enable good, supersu would update itself in background. So after using enable good disable root, I opened supersu and did complete un root. Rebooted and confirmed I did not have toot access. No root app will work.

Then I tried running enable good disable riot again.

I'll collect data for you and post back.
[Android Software/Hacking General [Developers Only]] calisro:
If you were able to open supersu after running that script, then it is likely the developer of the rom named the supersu apk that comes with it something that my script isn't catching. This is the hardest part about making these scripts work for everyone is that an APK located in /system/app can be called ANYTHING. I can call it BOB.apk and it will still work for whatever app is in that apk.

That being said. i'll bet you had one apk in /system/app and one in 'data/app for supersu. My scripts found your primary one that was updated from the market but couldn't find the one in /system/app so when /data/app supersu was 'hidden' the rom loaded /system/app supersu again.

Get me the output and I can see which it missed.

Also, you cant run the 'full unroot' from the supersu apk and expect my scripts to work.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

Makes sense.

Do you know if I use official cm10 then it will work?

Here are the files.

https://www.box.com/shared/6ta4nv5zl220jnvhdryt

https://www.box.com/shared/qxejt20s1b4n1z8k0q5b

https://www.box.com/shared/tbu6mv0z6afqt01rk7s5
[Android Software/Hacking General [Developers Only]] calisro:
Posting a debug zip. Flash this in CWM/TWRP and do the following:

After boot run in this order:

1) disable good enable root.

2) enable root disable good

3) then disable good enable root again.

After complete post these two files from your sdcard again:

disable good enable root.log

enable root disable good.log
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

Doing that right now. Thanks again.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

Her are the files...

https://www.box.com/shared/tre9prpdphlucn3ok3tq

https://www.box.com/shared/cp7hjo4zvbpvpqjnrvfh

Thanks for the efforts.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

Ok I've Done more analysis on this.

1. I've installed fresh copy of CM10.

2. Installed the script in OP.

3. Installed autostart

4. Installed good, disabled auto start of good.

5. Did not install anything else.

6. Ran enable good disable root script. In this setup good was working perfectly fine

Now I wanted to get my apps back so I continued.

7. Ran disable good enable root.

8. Installed titanium backup and safely restored only applications that do not need root (eg. Citibank, Chase, Aqua mail, etc.)

9. Ran enable good disable root.

10. And it failed the validation check on goods side... :(

11. Then I rebooted the system, cleared data from good and it still failed validation check.

12. Ran disable good enable root.

13. Uninstalled titanium backup. And cleared data for good.

14. Ran enable good disable root.

15. This time it worked perfectly.

I think the problem is caused by titanium backup on CM10.1 rom.

I will restore back to PA rom backup and then Uninstall titanium backup and see it it all works there or not...
[Android Software/Hacking General [Developers Only]] ProFragger:
Hey [MENTION=4931919]munchee[/MENTION] your instructions were a bit of a puzzle, but I figured them out and can confirm that Good is launching on my G4! Yayyyy!!! Thank you so so much bud :D!

Also my deepest gratitude to [MENTION=2221071]xaueious[/MENTION] to his incredible workaround! And to my friend [MENTION=3515213]Nowak4G[/MENTION] for helping test on the G4 and of course to [MENTION=1627069]El Ha$on[/MENTION] for his help!

Also thanks to [MENTION=2505474]Phantasm4489[/MENTION] for writing a patch that keeps on giving! Hopefully he reads this and comes back some day to update his patch to work with newer versions of Good :P! Thanks guys!
[Android Software/Hacking General [Developers Only]] zavjah:
Cannot open attachments since CM12.1

Hi all,

First of all yes, I have GFE 2.7.390 with latest official xposed up an running on my nexus 5.

But I do have another question:

Since I changed from CM11 to CM12.1 I cannot open any attachments within the GFE any more. On CM 11 I was using the same GFE version like now amd it worked fine. But now I only get the message that the IT administrator has disabled the possibility to view attachments outside of the good app.

Is anyone facing the same? Is there a way to get the view functionality back?

The to you all,

Zavjah
[Android Software/Hacking General [Developers Only]] thehobit:
In my experience, GFE 2.7 and lower has some compatibility issues with CM 12.1.
[Android Software/Hacking General [Developers Only]] CravingMender9:
Can someone confirm if this works?

Hi,

This is the longest I've been on a new phone without root. But I am almost out of patience and need to get some changes / debloat / sd card fix etc.

So, I had two questions for anyone who can help me test:

1) Those with Samsung, does GODO work with Knox Warranty void (0x1)?

2) Is this possible: Previously Installed GFE -> Uninstall (optional, or freeze after root) -> Root -> Make changes to phone that need root -> Unroot -> Reinstall GOOD?

With newer Samsung, I can't root without voiding Knox warranty. I really dont care about it as long as GOOD works. If there is someone using Samsung here, can you confirm that GOOD works with knox 0x1?

Thanks
[Android Software/Hacking General [Developers Only]] tdvargo:
1) I can confirm that GFE does NOT care about Knox. My GFE on my SGN2 has been running just fine with Knox 0x1 for over a year.

2) See this post for good step-by-step instructions:

<http://xdaforums.com/showthread.php?p=63385446>
[Android Software/Hacking General [Developers Only]] CravingMender9:
Thank you for the confirmation about Knox.

BTW, I may have missed it, but what post are you referring to? The link is for this points to my own post.

Thanks again.
[Android Software/Hacking General [Developers Only]] tdvargo:
[MENTION=4125131]CravingMender9[/MENTION],

Sorry, I missed the last part of the URL that specifies a particular post. Here is the correct URL:

<http://xdaforums.com/showpost.php?p=62514651&postcount=1361>
[Android Software/Hacking General [Developers Only]] the_mentor:
I'm not sure if this is the right place to ask this question but I'll give it a go.

Did anyone find a way around the root check in the "Good agent" app?

My company requires this app to setup our email.

Thank you
[Android Software/Hacking General [Developers Only]] El Ha$on:
Nothing yet on that app. Hopefully someone that has more technical knowledge might be able to pick it up.
[Android Software/Hacking General [Developers Only]] zavjah:
There is no other way to use GFE with cm 12.1 then the one with GFE 2.7.390 and this module, thus my question to all of you out there using this combination: what is your way in displaying attachments in GFE?
[Android Software/Hacking General [Developers Only]] El Ha$on:
I would imagine it depends on the type of attachment.

In my experience I've tried to open excel spreadsheets and I have had to download Google sheets to open it successfully. Interestingly enough Microsoft Excel did not work for me.

If its an email that's attached the GFE is able to handle it. I have tried anything else yet.
[Android Software/Hacking General [Developers Only]] zavjah:
Good to know that it does work for someone. I have just again tried XLS, DOC, PDF and regardles of an attachment type I always get the message:

Blocked: Your IT-Administrator has blocked opening of this attachment type outside of good app.

But I know that there was no change in the IT-Policy in regards to this in my company. This problem started when I switched from CM11 to CM12.
[Android Software/Hacking General [Developers Only]] mentalinc:
Hi

Has anyone had success running lollipop (5.0 or 5.1) on a Galaxy S 5?

I'd like to upgrade to lollipop but need to have root and GFE still running...

Which xposed framework did you have success with?

Thanks
[Android Software/Hacking General [Developers Only]] gorthon:
On my Galaxy S5 Duos I moved from Stock Android 4.4.2 to Cyanogenmod 12.1 (Android 5.1), including Good, so that answers your question. I can only recommend switching to CM, it is much better (and faster) than stock. You will lose fingerprint unlock though.

I had rooted Kitkat stock ROM, running XPosed and GFE, and here is what I did (some steps may not be necessary):

1) reboot, do not open Good thereafter

2) backup using Titanium Backup (backed up all apps anyway)

3) freeze Good

4) backup Good again with Titanium Backup

5) install CM12.1 (this involves installing TWRP recovery, wiping cache, system, data partitions (I wanted a clean install), flashing CM and Google Apps)

6) boot into system, phone was incredibly fast :) Set up everything the way I wanted.

7) Install XPosed for Lollipop. There are a few threads about this on xda, like here and here. I first booted into recovery and flashed the xposed-v75-sdk22-arm.zip . Then reboot and install	XposedInstaller_3.0_alpha4.apk

8) Now you can just start the XPosed install and install modules as you were used to in Kitkat. Don't forget to activate them and reboot.

9) Restore the Good backup in Titanium Backup (the last of the two backups). When you start Good, pay attention to two things: Good will ask once for root access, click Grant. Good will then ask for device administrator priviliges, as you are not installing it from the play store. Click activate.

Good runs fine now. It is version 2.7, so not the most recent one. I can open image attachments within Good, but no office documents. Not sure if this worked in Kitkat, some people say it has to do with Good 2.7 not supporting Lollipop well. But it is the most recent version we have.
[Android Software/Hacking General [Developers Only]] El Ha$on:
Anyone out there interested in testing some Marshmallow?

http://xdaforums.com/showthread.php?p=63826736
[Android Software/Hacking General [Developers Only]] dabrowsk:
I've tried but good even didn't start.
[Android Software/Hacking General [Developers Only]] El Ha$on:
Which version of GFE did you try?

GFE 2.7 with module 3.5?
[Android Software/Hacking General [Developers Only]] dabrowsk:
Exactly :(
[Android Software/Hacking General [Developers Only]] Gjohnson7771:
Can someone she'd some lite on this for me. I have a Note 4 running Pop rocks Rom. Is there a simple working setup for Good mobile without exposed? Exposed has been given us stability issues with the Rom.

Thanks
[Android Software/Hacking General [Developers Only]] El Ha$on:
Since [MENTION=692317]dabrowsk[/MENTION] has confirmed for us that this module does not currently work with Marshmallow is there anyone out there is the technical know-how, to possibly update the module to get it working on 6.0? Seems like CM13 might be dropping soon, and it would be great being able to upgrade and keeping GFE even if it is one of the older versions.

Perhaps [MENTION=2221071]xaueious[/MENTION] because of your workaround with 64bit? Or maybe [MENTION=2505474]Phantasm4489[/MENTION] can shed some light? Any help is greatly appreciated.

Again thank you for writing the patch to begin with!

---------- Post added at 03:19 PM ---------- Previous post was at 02:22 PM ----------

Currently no other method known if you are rooted.

Sent from my Nexus 7
[Android Software/Hacking General [Developers Only]] Gjohnson7771:
Ok, thanks for the reply.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
unfortunately no i'm not sure where the issue could be. Some of the issues people have seen relating to 64 bit chips seem to be related to the way it patches the native library files but i wouldn't expect problems with that to manifest themselves in this way.

i wonder does gfe v2.7 even work on marshmallow correctly when used without root and the xposed module.
[Android Software/Hacking General [Developers Only]] dabrowsk:
With xposed installed and without this module activated gfe at least started to work. I tested it as well.
[Android Software/Hacking General [Developers Only]] ddimple4:
GFE 2.7 works on MM without root and xposed.
[Android Software/Hacking General [Developers Only]] mentalinc:
Great to hear v2.7 works on MM.

Now to find what's the cause of the bug to prevents Good from running (based on the above reports)
[Android Software/Hacking General [Developers Only]] El Ha$on:
All,

I just installed an unofficial cm13 build on my LG G2 to test GFE 2.7.1.

First I tested GFE without Xposed and it started up and was brought to the setup page.

Next I installed Xposed, installed the module, enabled rebooted, uninstalled GFE and went into titanium to restore my backup.

GFE started up and no problems, however it could not establish a connection to the server, so my guess is that currently to get it working it might to be on a clean install of GFE 2.7.1 which is a bummer.

Wish I had more to comment on, but as official cm13 is not yet available for my device (vs980) I am going to wait until then to fully test my hypothesis as getting a pin from my employer is not something I have easy access to and request often.

Hope this helps someone or guidance for someone willing to test further.
[Android Software/Hacking General [Developers Only]] payne_307:
I'm on rooted Sultan Unoffcial CM13 on OnePlus One device based on Android 6.0. GFE v2.7.1 works just fine with Xposed and GFE patcher module. I'm getting emails and notifications. I have tried Xposed and GFE after a very long time since I was using the official Cyanogen OS 12.1 on my OnePlus One. But even after using it after so many months, had no hiccups.