yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] calisro:
Phantasm4489, i've linked this post in the OP so people can find it. Of all the solutions right now, this one is the best IMHO. Thanks a lot.
[Android Software/Hacking General [Developers Only]] control187:
I clearly have not had enough coffee today, how do I flash a zipped apk so that I cab install it in xposed? Do I extract it to the xposed folder in system?
[Android Software/Hacking General [Developers Only]] calisro:
Simply unzip it with any zip utility and install it like any other APK (side load). Then go into xposed and enable it.
[Android Software/Hacking General [Developers Only]] control187:
Unzipped, installed, activated. Also running rootcloak. Downloaded Good, fails to even start.
[Android Software/Hacking General [Developers Only]] calisro:
I just did what you did and its working. I even have rootcloak installed.
[Android Software/Hacking General [Developers Only]] control187:
Weird, still failing to start here. I have a Motorola xt912, so its a locked bootloader using Safestrap. CM11 installed on stock slot. Can anyone in a similar situation confirm it's working?

Thanks.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
I would upload it but there are issues with the module repository at the moment. They aren't accepting Amy new accounts at the moment and I don't already have an account so i can't upload

---------- Post added at 11:34 AM ---------- Previous post was at 11:27 AM ----------

It doesn't matter if you keep it running or not it still sits in the background watching for root even when the main app isn't running. If you install gfe and you have root it will detect it in seconds. You must install the xposed module first and leave it running at all times moo
[Android Software/Hacking General [Developers Only]] daichiasuka:
Started using this last night after I upgraded to KitKat and have has no issues with root detection. Thanks!

Looking at the code and the disassembled apk, I assume this is supposed to disable the password.

de.robv.android.xposed.XC_MethodHook.Unhook u2 = XposedHelpers.findAndHookMethod(classSecurityPolicy2, "s", XC_MethodReplacement.returnConstant(Boolean.valueOf(false)));

It doesn't seem to be working.
[Android Software/Hacking General [Developers Only]] control187:
I did get this to work finally, here is what I did on my VZ xt912 with SS to install ROMs.

Uninstall xposed, modules, and GFE

Wiped my Good PIN online, wiped the device from the Good record

Installed xposed, rebooted

Installed rootcloak and Phantasms apk, activated, rebooted

Installed GFE

Added GFE to rootcloak, rebooted

Added device to Good, requested PIN

Fired up Good

I also removed several root tools that I normally keep on the phone. These included TIB, FS file root, BBS root. I will add these back in one at a time and see if one of them is tripping me even with rootcloak and the APK running.

Thanks again.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
Yes well spotted. It was my attempt to disable the password. It didn't work and it needs to be removed. It will cause problems if you try and build from source with that included.
[Android Software/Hacking General [Developers Only]] daichiasuka:
I don't think you'll be able to disable it, but you can probably override the trigger to lock.
[Android Software/Hacking General [Developers Only]] dkoon1987:
Any luck bringing back titanium backup and/ or root explorer?
[Android Software/Hacking General [Developers Only]] control187:
I did manage to successfully load TI and FX root and maintain Good for at least 5 minutes to write this :) so I guess its OK. Weird that it wouldn't work before.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
you shouldnt need to uninstall any apps if using the xposed module. you also shouldnt need to install any additional apps (just xposed and xposed module - rootcloak is not needed). xposed module has everything required to prevent the current version of gfe from detecting root.

You need to install the xposed module and activate it before installing gfe or if you have already installed you need to wipe the data and get a new gfe activation pin.

Also at no point can you EVER deactivate xposed or the xposed gfe module while you have gfe installed (running or not)... if you do gfe will detect root within 5 seconds. so flashing a new rom or upgrading xposed will result in gfe detecting root unless you uninstall first (it may be possible to freeze/disable it but i'm not 100% sure on this as it didn't work for me - but maybe i made a mistake).
[Android Software/Hacking General [Developers Only]] clintonroche:
So While running GFE you can never use any of the xposed features or it will trip the root detect in the GFE?
[Android Software/Hacking General [Developers Only]] control187:
No. I think he is saying you cannot reinitiate exposed while GFE is running. So don't flash a ROM or turn exposed off.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
Yep exactly
[Android Software/Hacking General [Developers Only]] clintonroche:
Thanks both... Just wanted to make sure. I hate to bug IT for new codes.
[Android Software/Hacking General [Developers Only]] clintonroche:
Looks like it is working here... Thanks!!
[Android Software/Hacking General [Developers Only]] Phantasm4489:
Access to upload new xposed modules is now available again so i have added this into the Xposed module repository now:

http://repo.xposed.info/module/com.phantasm.xposed.gfesecuritypatcher
[Android Software/Hacking General [Developers Only]] CPA Poke:
Great work on this, I finally got up the guts to request another PIN from my IT folks (they're pretty hard to come by) and got GFE up and running flawlessly with your module!!

With that said, though, I'm an admitted flashaholic and will be hard-pressed to stay with this ROM for that long of a period. I remember back when all this started, people said that backing up app/data using TiBu allowed them to restore after clean-fa new ROMs. Have you (or anyone else) been able to do this? All I know is that the last time I installed GFE (using a hacked apk), it stopped syncing after I did a Nandroid backup and restored it after flashing a different ROM.
[Android Software/Hacking General [Developers Only]] calisro:
nandroid works if you disable the app prior to backing it up and if you do NOT re-enable it before restoring it.

1) disable gfe

2) back it up

3) flash new rom/wipe whatever.

4) re-add exposed and enable the module.

5) re-enable app (or restore it if you wiped data).
[Android Software/Hacking General [Developers Only]] control187:
Would that work with the Safestrap backup used for locked bootloaders too? Just curious.
[Android Software/Hacking General [Developers Only]] calisro:
I meant titanium. those directions are for titanium.

nandroid would work too. Thw key is that once gfe communicates with the server, all prior backups are invalid.
[Android Software/Hacking General [Developers Only]] calisro:
any type of backup. you just can't let gfe phone home between your backup and restore or that backup won't work.
[Android Software/Hacking General [Developers Only]] CPA Poke:
Perfect, that's great news. That's exactly where I went wrong - i tried to restore it via TiBu on the next ROM - that I flashed...then I restored my previous Nandroid and it stopped working.

Seriously thanks for your help. Usually I'm one to always try it all myself and figure it out, but this is a unique case.
[Android Software/Hacking General [Developers Only]] lionel7:
Hi guys

My company is now also checking if it is ios or android and unfortunately they now only accept ios.

do you know if it is possible to make my company think that i have an ios device when i run an android ?

Thx for your help

Lionel
[Android Software/Hacking General [Developers Only]] clintonroche:
That sucks.... But I would advise against this.

Sent from my Note 3
[Android Software/Hacking General [Developers Only]] yokuyuki:
Is it possible to disable GFE, reboot to recovery to apply root, install titanium backup to backup GFE, flash a new ROM, and then restore GFE?

Just want to avoid having to get a new PIN.
[Android Software/Hacking General [Developers Only]] calisro:
um. Didn't we just discuss that like 3 posts back? April fools already?
[Android Software/Hacking General [Developers Only]] control187:
In CM11 I couldn't get Good to disable, even with AppOps. I had to uninstall and flash. I have the advantage of getting my own self service Pin though.
[Android Software/Hacking General [Developers Only]] calisro:
I just did it today with cm11. You'll need to use titanium to freeze it. This is the process:

1) open Good and go to settings. Select "offline" and turn off persistent mode.

2) freeze the app with titanium.

3) back up Good with titanium or whatever.

4) do your rom work. wipe whatever. etc.

5) reinstall titanium after new rom if needed.

6) setup Good cloak xposed module.

7) restore Good.

8) unfreeze and go online in settings.
[Android Software/Hacking General [Developers Only]] control187:
Thanks for the tip. Cloak doesn't work for me though, only Phantasm's script. I really wish TI made the freeze function a little more obvious.
[Android Software/Hacking General [Developers Only]] yokuyuki:
Different scenario. I don't have root at the moment so I can't freeze immediately. I'd have to boot into recovery, root, and then freeze, but I'm not sure if on startup, GFE will detect root.
[Android Software/Hacking General [Developers Only]] calisro:
you'll be fine if you do a nandroid. then you can point titanium to the nandroid as a source and restore after you install the new rom and setup phantoms xposed mudule. Should work I think.
[Android Software/Hacking General [Developers Only]] yokuyuki:
Good point. I hadn't thought of that. Don't even need titanium for that, can just use nandroid manager.
[Android Software/Hacking General [Developers Only]] mbastats:
Good Connect

Hope someone has had this situation before.

Good has another app called "Good Connect" used for Instant Messaging. Root Cloak doesn't work for it. I was thinking there might be a way to rewrite Phantasm's patch so that it would work with Good Connect. Since it's a product from Good, the security measure are most likely the same. At least it looked that way when I decompiled the apk...

Any advice is appreciated.
[Android Software/Hacking General [Developers Only]] daichiasuka:
With a little work this could likely be done. I would attempt it, but I don't have access to Good Connect. We don't use it (yet).
[Android Software/Hacking General [Developers Only]] mbastats:
Decompiling the files in the apk is the hardest thing for me. I can unzip it, but the .dex, .arsc, .xml files I'm not as skilled with. I found some info here. If anyone has information on how to EASILY break those files down for modification, please let me know.

Daichiasuka - I could send you the .apk or you can download and unzip it for Good Connect. Look at it and compare it to GFE apk and the patch Phantasm put together. There has to be a simple way to either replace files in Connect from GFE or rewrite a few lines of code within the files.
[Android Software/Hacking General [Developers Only]] daichiasuka:
I'm a little short on time right now, but maybe next week I could take a look. The issue for me is really testing. If you want to work with me to test an xposed patch for this, drop me a PM.
[Android Software/Hacking General [Developers Only]] mbastats:
I'm guessing no one has any ideas or wants to help out on this one. Good Connect is an app for Instant Messaging through Microsoft Lync/Communicator. I'm trying to duplicate or create the same scripts for it, as phantasm has for Good for Enterprise.
[Android Software/Hacking General [Developers Only]] rankitt:
will it work with Note 3 stock rooted

Hi Geeks,

Just had a question whether it will work with my At&t galaxy Note 3 stock rooted ?

Regards

Rankitt
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Yes. If you can run Xposed, then this should work. Running it on both my M8 and N7.
[Android Software/Hacking General [Developers Only]] dyonissos:
Tutorial?

Hey guys,

I'm trying to get GFE working on a rooted Moto G (CM11) but no luck so far.

Can someone put up a small how to?

What i've done so far:

- Installed GFE and got the rooted device message

- Installed the xposed apk

- Installed RootCloak Plus (Cydia) from the Play Store

- Cleared GFE data and cache

- Re-configured GFE and got the rooted device message again.

Do i need to completely uninstall GFE and reinstall? Didn't try this as i already requested 3 PINs today :(

Thanks for your hard work on this, it would mean a lot to me if i could use GFE on my rooted device.

Cheers!
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Did you also install the apk from the OP or the Xposed download section?

What you should do is:

1. Install Xposed framework

2. Install the Xposed apk (either from op or via Xposed framework

3. Reboot

4. Install Good

Done the above everytime, and works perfectly!
[Android Software/Hacking General [Developers Only]] dyonissos:
Finally got it working.

Thank you for making this possible! :good:
[Android Software/Hacking General [Developers Only]] AnteusFogg:
Adding for those who want to flash rom upgrades (dirty flash only of course) :

Freeze Good using ROM Toolbox or Titanium

Flash ROM

Enable Xposed with the GFE module

Reboot

Unfreeze Good

That works beautifully here
[Android Software/Hacking General [Developers Only]] aioen:
this worked for me! Thanks! (using Nexus 4, CM11)
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

I don't think so. Good is a piece of cr4p app. I have had it fail to detect root on cm9 on OG epic 4g but then start detecting root on the stock rom on that same phone. It also fails to detect it on my asus tf300 tablet (both stock and cm10). I also had it fail to detect it on my current phone with another custom rom (forget which one, I flash a lot)
[Android Software/Hacking General [Developers Only]] wc4482:
I'm having trouble on initial set up (flashed new ROM and backup wouldn't connect). I think its because I disabled all the services for Good in the autostarts app. I'm going to try installing one more time with only the startup service disabled.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

What do you mean "backup wouldn't connect". btw, I disable all for Good in autostarts. That should hurt.
[Android Software/Hacking General [Developers Only]] wc4482:
Sorry I mean after i restored all apps with titanium backup, the app would load.. but the email messages were dated 1/15 (i guess date of last backup). It wouldn't connect to the server and download so I decided to wipe cache/wipe data and uninstall/reinstall, hoping that if I do a fresh initial setup it will allow me to connect. Maybe it is the ROM or the new radio's I flashed (on Beans build7) but I hope not because the ROM is real smooth. I know that he used a lot of files from the new verizon OTA.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

you can have problems doing that. good keeps track of last syncs to the server. If you run my disable good script first then chances are you'll then be able to back it up with tibk and restore it to a new rom unless you run good between the backup and the restore.

I generally just don't restore data for good. you can just clear Good data and reauthorize it and it will work fine.
[Android Software/Hacking General [Developers Only]] wc4482:
I figured it was just User error. I'm not that good with titanium backup yet and it definitely is not as smooth for me as it should be. Thanks for the tips though - I'll remember that from now on!

Update: I cleared data and uninstalled/reinstalled and then disabled good/re-root through your script and verified that autostarts didn't have anything blocked. Then temp rooted through your script and went through the setup process from scratch. It says successful but not connected so hopefully in 30 minutes i'll be rocking and rolling. Thanks for your workaround and continued support!!!

Oh and correct me if I'm wrong but it seems like you have to be really careful what apps you have open in "recent apps" when going back and forth between root and temp un-root. I had titanium backup open yesterday when I tried to enable_good_disable_root and good caught my root. I wonder if this might be causing some people's problems (they aren't completely closing out of all apps before running the unroot script)
[Android Software/Hacking General [Developers Only]] wc4482:
So the initial download worked pretty good but it keeps going into "Not Connected" mode. Could it be cause my device ID changed or something? I don't know if its Verizon or my Rom or me or what.

I have to log off and quit Good and then open and log back in, in order to check my mail :confused:
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

weird. see if it happens connected only through wifi. Perhaps verizon wants you on a corporate plan. :/

edir: verizon stupidity. they should be sued. data is data...

https://community.verizonwireless.com/thread/767929

http://www.howardforums.com/showthread.php/1767952-Corporate-Email-Good-for-Enterprise
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

yes. some apps like tibk and es explorer leave things running or filesystems rw or whatever... if use those type of apps ill reboot b4 running good again.
[Android Software/Hacking General [Developers Only]] wc4482:
Well I am on a share everything plan and I started paying $15 a month back in December to be Good enabled. I just talked to Verizon and they show my phone as still being Good enabled and they told me they weren't blocking anything. At this point, I'm wondering if it is either

1) the fact that this morning I cleared Good data and tried reinstalling using the same license provided by my IT department (it says it expires Feb 3rd) or

2) the fact that my "Device ID" changed when I wiped and loaded the new beans b7 ROM. Titanium gave me a prompt saying that sometimes app's will look to the device ID. I think I hit revert to previous ID but It kept coming up so I just said screw it, ignore.

Does any of the above sound like something that might be causing problems??
[Android Software/Hacking General [Developers Only]] calisro:
no. My device ID changes all the time. The license is fine if it initiated which it did. It's something else...
[Android Software/Hacking General [Developers Only]] wc4482:
Ok thanks for saving me time. Also thanks for your time - I'm getting the feeling that this Good nonsense is almost not worth the hassle.

Do you think it could be the ROM? FYI build 3 and build 6 worked perfectly fine with your workaround. Build 7 has some big changes - such as the radio and some files from the new verizon OTA for the GNII. I might try going back to build 6 and seeing if I still have the problem.

Also, am I correct in saying that I can keep wiping data and reinstalling GOOD using that same license number as many times as I want until Feb 3rd (when it expires?)
[Android Software/Hacking General [Developers Only]] Bestbaldmanever:
Hallelujah!

Well, I don't know how, but I finally got it working!

I was running SuperNexus 2 and had unrooted it to try and get it working but no joy. Then things started crashing and my PC wouldn't recognise the S3 when I plugged it in.

So I deleted all data and re-flashed the ROM. Then reflashed CWM Recovery, downloaded ROM Manager and flashed the latest nightly of CM 10.1.

At this point I figured I'd give the scripts approach one final go before giving up completely and flashing the stock ROM back, as I really do need mobile email from work.

So, I flashed the scripts zip in the OP, installed Good, then the version of SManager in the OP, then ran the enable_good_disable_root script, fired up Good, entered the PIN, and held my breath. And sure enough it worked. And has been working fine now for about seven hours! Fingers crossed it continues.

Unfortunately the PC still doesn't recognise the phone when I plug it in; looking at other forums that appears like it might be a terminal fault. At some point I may have to re-flash the stock ROM and send it back to Samsung for replacement, but for now I'm just happy I got it working!

Thanks to everyone for their help and patience!
[Android Software/Hacking General [Developers Only]] wc4482:
Good has a tendency to start up on reboot, so make sure you only reboot if you are temp unrooted OR the better option is to buy "Autostarts" in the play store and disable Good on startup. Then you don't have to worry about Good starting up when you don't want it to
[Android Software/Hacking General [Developers Only]] wc4482:
Re: Good for Enterprise ( GFE ) root workaround

Does good not work on wifi connection? I re flashed and it seems to be working but not if I'm connected to my firms secure wifi
[Android Software/Hacking General [Developers Only]] calisro:
Works on either.
[Android Software/Hacking General [Developers Only]] wc4482:
Blah, ok thanks. I guess sync on 3g/4g only is better than no connection at all.
[Android Software/Hacking General [Developers Only]] Zirillian:
My firm is the same way. If I connect to their secure WiFi while I'm in the office, Good won't connect. I contacted the IT helpdesk and was informed that that's just the way it is. Won't work. So we're stuck not using Wifi at the office just to keep Good working.
[Android Software/Hacking General [Developers Only]] wc4482:
How do I send logs

Something happened to my scripts - both of them.

I tested some things and 1) when temp unroot, Good policy compliance failed and root apps may or may not have still been able to obtain root access. From what I saw SuperSU was hidden in all cases. 2) When re-rooting, SuperSU wouldn't show back up and root apps may or may not have been able to obtain root access. I had to restart at this point to bring back SuperSU and root.

I decided to reflash the scripts (made sure that root was indeed working before restarting to recovery!). I wiped delvik cache out of habit. Not really sure what that does.

Ran script to temp un-root and check to see if SuperSU was properly hidden. Success.

Ran script to re-root and check if SuperSU was properly restored. Fail. At this point opened up TiBU and it did properly acquire root access. Restarted Device (which restored SuperSU app)

Ran script to temp un-root and see if TiBU improperly acquired root access. It improperly acquired root access.

Edit: Decided to completely wipe and reflash my ROM. Probably something I did. I'm sure I can get it working again
[Android Software/Hacking General [Developers Only]] sabinn:
Files attached. Thanks so much for looking into this. I really want to get this working so let me know if there is anything else I can supply that would help debug the process :)
[Android Software/Hacking General [Developers Only]] aydc:
Has anyone else been able to replicate this? Thanks to the tips here I can use GFE with my phone, but I also want to get rid of the damn app asking for a password every time I want to use it. I tried what's described, but still the app asks for a password once 15 minutes run out. Maybe it can be possible to turn 15 minutes into 999999 minutes with an Xposed script.
[Android Software/Hacking General [Developers Only]] calisro:
The key to having it not prompt all the time is to remove the permission GET_TASKS permission. Give that a try. You can do that via exposed (apps like App Settings can do it) or there is apps like 'permissions denied' from the market (follow directions in the OP for permissions denied).
[Android Software/Hacking General [Developers Only]] AnteusFogg:
THAT is awesome. Thanks so much for the tip!

If I helped you, please thank me :)