yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] aydc:
The first time I tried it, it didn't work, that's why I wrote the post here, but after you confirmed it, I uninstalled App Settings and reinstalled it and tried again, and this time it worked. Thanks.
[Android Software/Hacking General [Developers Only]] dyonissos:
It's working!

Yesterday I set the lock-out policy to 1 minute and it didn't ask me for password since.

Thanks for sharing!
[Android Software/Hacking General [Developers Only]] slinkys4evrh:
My company's GFE policy makes us add a password to the lock screen. I tried the remove"GET_TASKS" permission but that didn't work. Does anyone know of a way to disable the lock screen password?

Getting tired of entering in a password all the time.

-Slink
[Android Software/Hacking General [Developers Only]] AnteusFogg:
Removing the get_tasks permission did it for me, and just like you my company is enforcing the use of a password

If I helped you, please thank me :)
[Android Software/Hacking General [Developers Only]] calisro:
Give the exposed module 'Lockscreen Disabler' a try. I haven't confirmed that it would work but its supposed to.
[Android Software/Hacking General [Developers Only]] slinkys4evrh:
Calisro,

Thanks for your quick reply but unfortunately when I tried the "Lockscreen Disabler" I received a compliance check failure.

-Slink
[Android Software/Hacking General [Developers Only]] jonsharky:
Having the same "issue" at work.

Will give this a go. Thank you.
[Android Software/Hacking General [Developers Only]] dyonissos:
Removing the permission GET_TASKS permission worked for me.

It still asks for password sometimes, but i can live with that.
[Android Software/Hacking General [Developers Only]] psg190:
Looks like today's update kills root protection. :(
[Android Software/Hacking General [Developers Only]] AnteusFogg:
damn it, I forgot to disable the auto update :-$
[Android Software/Hacking General [Developers Only]] nutttr:
Dammit, I was just about to download it today!! Hopefully it's an easy fix....

Anyone got the apk for the old version?
[Android Software/Hacking General [Developers Only]] psg190:
+1 I'd like an apk for the previous version as well.
[Android Software/Hacking General [Developers Only]] AnteusFogg:
I restored a backup that has the old version. If you tell me how to extract the apk I'll make it available. If there is any way to do that, that is.
[Android Software/Hacking General [Developers Only]] psg190:
You can use Titanium Backup to extract the apk. Or this app: https://play.google.com/store/apps/details?id=com.extract.apk.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
I've updated the xposed module which should allow it to work with the latest version (and also put in an additional patch that should hopefully handle updates better than the previous one).

I can't test it at the moment but if anyone wants to give this a try for me and report back before i upload it to the official xposed repository that would be great.

Edit: updated version - first attempt did not work
[Android Software/Hacking General [Developers Only]] EvertonB:
I just tested and it didn't work for me (Nexus 5)- thanks for trying to fix.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
can you be more specific about what did not work? had root already been detected by the new version? if so did you get your account reactivated and it then detected root again and locked you out? or something different happened?
[Android Software/Hacking General [Developers Only]] AnteusFogg:
Thanks, I'll give this a spin when I've reactivated my account!
[Android Software/Hacking General [Developers Only]] EvertonB:
Sorry, I'll be more helpful.

1. Old xposed module was working fine with Good v2.4.0.315

2. Updated Good to v.2.4.0.250 and got the 'account deactivated message' within Good

3. Rolled back to v 2.4.0.315 using my TB backup

4. Installed new version of xposed module, rebooted and then updated good

5. I didn't actually get the account deactivated message when I tried to setup Good with new pin - it started working through the 'starting services' etc steps and then it just through me out and wouldn't complete setup
[Android Software/Hacking General [Developers Only]] segelfreund:
Can you give me the old Version oft good? So i can tried.

Gesendet von meinem Nexus 5 mit Tapatalk
[Android Software/Hacking General [Developers Only]] Phantasm4489:
i think i found the problem with it and i've updated the attachment in the previous post.
[Android Software/Hacking General [Developers Only]] EvertonB:
when I get to 'retrieving services' it throws me out of good. I can go back to good and resume the setup i.e. I'm not locked out, but it never gets past 'retrieving services'
[Android Software/Hacking General [Developers Only]] Phantasm4489:
i'm not sure if this is just the app being crap as i've had other reports that the updated module works fine.
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Have had this before in the past (both pre-root and post-root) and literally had to uninstall gfe, get a new pin, and then reinstall again from the play store!
[Android Software/Hacking General [Developers Only]] CPA Poke:
Thanks for the update!

For those of us who haven't updated GFE yet, is there a recommended way to install the updated patch apk (so I can update to the new version of GFE) without triggering detection on the current version of the app?

I tried clean-flashing my ROM and then downloading the new version directly from the Play Store (after installing your updated module and rebooting) and then restoring data only from TiBu, but after I entered my password on the app it just closed out immediately.
[Android Software/Hacking General [Developers Only]] dabrowsk:
For still the same :( after entering new pin it is stopping on starting services :(
[Android Software/Hacking General [Developers Only]] vault1965:
I can past service start but Good is disabling itself because of non compliant device,. New patch, root cloak and app permissions as for everybody else. Old version was running fine.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
Are you running v3.1 of the xposed module?
[Android Software/Hacking General [Developers Only]] vault1965:
Yes, the one attached to your post.

Bugger disabled my account on server I am waiting for my it team to add me back again,. We have pin provision portal, so that is not the problem. Let me know if I can help in any way.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
The new xposed module should still work with the previous version of gfe and so the best I can suggest is to backup the old version then uninstall or freeze it and the upgrade the module and activate before restoring the old age and update from the play store

---------- Post added at 08:40 PM ---------- Previous post was at 08:38 PM ----------

The only reason I ask is that the first one I attached today didn't work so I wanted to be sure you got the second one
[Android Software/Hacking General [Developers Only]] ojai00:
Good has stopped working for me with the latest official Play Store release. Even the Early Access 2.5 variants caused it to stop. I submitted a case to Good to see if 2.5 adds additional root detection techniques to block access to the application.
[Android Software/Hacking General [Developers Only]] vault1965:
Are you sure that 3.1 will work? I have uninstalled old version of good, update your module and then installed new version of good. Still got non compliant device.
[Android Software/Hacking General [Developers Only]] AnteusFogg:
Same here
[Android Software/Hacking General [Developers Only]] psg190:
New patch works for me. Thanks! :good:
[Android Software/Hacking General [Developers Only]] Phantasm4489:
I've had two reports of it working and a few saying there are problems so it's not completely clear as to where we stand yet
[Android Software/Hacking General [Developers Only]] AnteusFogg:
I uninstalled and reinstalled but still no luck, Good is dying whilst trying to retrieve the settings...

Anywhere I could find logs to help you?
[Android Software/Hacking General [Developers Only]] dabrowsk:
Me I did some tests with new PIN:

- previous version of Good and 3.1 - failure

- new version of Good and 3.1 - failure

- new version of Good and 1.0 - failure

- previous version of Good and 1.0 - success
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Haven't tried the new version of gfe as yet, but old version of good + 3.1 is working fine for me at the moment.
[Android Software/Hacking General [Developers Only]] vault1965:
Can anybody share previous version of Good? Apk from Titanium should do the trick.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
All I can suggest is try to unroot your phone and remove the xposed module and see if it works or not. Not an ideal situation but it might help identify the problem
[Android Software/Hacking General [Developers Only]] calisro:
prior apk version
[Android Software/Hacking General [Developers Only]] sean.trinidade:
FYI. Upgrade gfe this morning, and still seems to be working fine.

To repeat the steps I did:

1) Froze Gfe using TB

2) Upgraded the xposed module to 3.1

3) Restarted the phone

4) Defrosted Gfe using TB and logged in (now using old GFE + 3.1)

5) Updated Gfe via the Play Store (gfe was still logged in during the update)

All working fine!
[Android Software/Hacking General [Developers Only]] muzzy00_uk:
Not sure if its the same issue but after updating to the latest version good just closes itself. before i removed it it was just after accepting the password. Ive tried the module from xposed and the one a few pages back but same thing happening.

If its not the same issue any idea why its closing?

thanks in advance
[Android Software/Hacking General [Developers Only]] sean.trinidade:
All. FYI. Used the exact steps above to upgrade my 2nd device (Nexus 7) and everything is still working fine!
[Android Software/Hacking General [Developers Only]] ojai00:
So I opened a case with Good and they suggested reprovisioning and disabling root, neither of which worked. I decided to try to get a logcat going to see what was happening. I'm running eZKAT where SELINUX was set to Enforcing in About Device. As I was installing Good and also while I was attempting to reactivate I saw some of these entries:

I/SELinux ( 9684): Function: selinux_android_load_priority [0], There is no sepolicy file.

I/SELinux ( 9684):

I/SELinux ( 9684): Function: selinux_android_load_priority [1], There is no sepolicy version file.

I/SELinux ( 9684):

I/SELinux ( 9684): Function: selinux_android_load_priority , priority version is VE=SEPF_GT-N7105_4.4.2_0013

I/SELinux ( 9684):

I/SELinux ( 9684):

I/SELinux ( 9684): selinux_android_seapp_context_reload: seapp_contexts file is loaded from /seapp_contexts

I decided to give Agni a try and SELINUX shows Disabled now in About Device. I was just able to successfully activate. I gave the phone a reboot and Good is still working. Can anyone else in the same scenario give this a try and see if they have any luck?
[Android Software/Hacking General [Developers Only]] EvertonB:
All OK for me after a fresh install and new pin on two devices - n5 and n7 2013
[Android Software/Hacking General [Developers Only]] clintonroche:
Fresh install.... new PIN and everything worked perfectly running 3.1, Starting services took forever!!!

Thanks, Phantasm4489!!!
[Android Software/Hacking General [Developers Only]] rmccurdy:
I tried the one off play market and it would just crash so I downloaed the one you just posted "2.4.0.315"

* it seems to start services then bunch of windows close and open then I get .. "Compliance Check Failed" "rooted device detected"

:( using latest Xposed 2.6.1 with GFE mod ver 3.1 :(
[Android Software/Hacking General [Developers Only]] hawkeyejoe:
I did this exactly yesterday and it was one Starting Services for 4 hours before I stopped it. So I restored a backup. Today I tried this again but instead of updating GFE I completed removed it and then did a clean install of it. But had the same problem. Stuck on Starting Services for several hours. Each time I deleted the currently provisioned device from the Good Self Service Portal and added a new device. Any ideas on how to get around this?
[Android Software/Hacking General [Developers Only]] Hollow.Droid:
Just something you should be aware of guys:

http://good.custhelp.com/app/answers/detail/a_id/5208
[Android Software/Hacking General [Developers Only]] idanra:
Same for me on LG G2 D801. Old Good and new 3.1 xposed module work great together :D:D.

I'm still not sure how to upgrade the new good w/o detecting my root capabilities ....
[Android Software/Hacking General [Developers Only]] sean.trinidade:
I found simply updating the app via the Play Store (whilst Good was still logged in) worked fine.
[Android Software/Hacking General [Developers Only]] pamulli:
Not Working for me

My Bad...User error
[Android Software/Hacking General [Developers Only]] AnteusFogg:
Indeed installing the 3.1 module and then updating good worked. Note that xposed didn't want to just update the module, I had to uninstall it and install the new version. I froze good for the procedure and then updated it, all good :)

If I helped you, please thank me :)
[Android Software/Hacking General [Developers Only]] arkhipenko:
Same here. This worked:

Freeze Good

Update Xposed Framework (I was behind)

Update the GFE module to 3.1

Unfreeze Good - confirmed the old version worked

Update Good via Playstore

(Cross fingers and hold breath)
[Android Software/Hacking General [Developers Only]] hawkeyejoe:
I keep trying that method and for some reason Good gets stuck on Starting Services for hours and never goes any further. I let it go overnight once and still nothing. But from what people have said in the reviews of the updated app on Play it doesn't sound like the update was all that great anyway.
[Android Software/Hacking General [Developers Only]] wfagan59:
N5 4.4.3 working

I got my N5 working with the following:

Most recent Xposed Framework with both Phantasm's module and rootcloaker

added both good apk's to rootcloaker

downloaded and installed GRE 2.4 (2.5 kept force closing at retrieving services)

Used a new PIN and it was up and running in 5 min.

Thanks so much to everyone for making this happen. I'd been living w/o root for months, but couldn't help myself once 4.4.3 came out.
[Android Software/Hacking General [Developers Only]] crewzta:
BIG THANKS GUYS!

Got this working!!!, I love this forum!
[Android Software/Hacking General [Developers Only]] EVOme:
Awesome!! Updating to 3.1 got my freshly rooted s5 working with Good. Swell work
[Android Software/Hacking General [Developers Only]] stayley:
Note II GT-N7105 working!!

Thank you to everyone in this forum. Here's my situation:

I have a rooted att galaxy note II

currently running will03's slim kat 4.4.3 V20

my model number shows as GT-N7105

GFE is running with:

Xposed Framework 2.61

Phantasm's module 3.1

Rootcloaker

dl & installed GFE 2.4

https://get.good.com/ea/android/android.html

Used a new PIN and it's running!

As an extra measure, disabled auto update in playstore.

(I didn't add / remove anything from Rootcloaker b/c I didn't understand how to, just being honest)

Thank you all!!

:victory: :D
[Android Software/Hacking General [Developers Only]] jonsharky:
GFE Xposed 3.1 works on the latest Good Mobile update from playstore! Fyi!
[Android Software/Hacking General [Developers Only]] arkhipenko:
Do you mean the 2.5.1.363 update of June 23rd?

Sent from my SAMSUNG-SGH-I337
[Android Software/Hacking General [Developers Only]] clintonroche:
May I ask what process you used? Just straight update? Or freeze and update?

Sent from my Note 3
[Android Software/Hacking General [Developers Only]] jonsharky:
Yes today's!

---------- Post added at 02:29 AM ---------- Previous post was at 02:29 AM ----------

Just update and rebooted!
[Android Software/Hacking General [Developers Only]] jyo1:
This issue doesn't seem to be resolved in latest version also.
[Android Software/Hacking General [Developers Only]] javaguy110:
Confirmed. Working before the update, took the 6/23 Good update and it's still working. Rebooted phone to ensure it worked after restart as well.
[Android Software/Hacking General [Developers Only]] arkhipenko:
Yes. Same here. Worked like a charm.

Sent from my SAMSUNG-SGH-I337
[Android Software/Hacking General [Developers Only]] Zirillian:
Have been monitoring this thread for quite some time in the event I ever had to use it...well..the time has come. I've been on GFE for 2.5 years now on various different roms (CM, PA, Slim, etc.) throughout several versions of Android (Nexus 4). For some odd reason, I was never caught....never got the dreaded security lockout despite wiping my phone several times for new roms etc and doing fresh installs. Well, my days as an outlaw are officially over. I did a clean wipe last night to switch from Slim 4.4.2 to PA 4.4 (based on 4.4.4) and after installing GFE (from Playstore) and requesting a new PIN, was notified that my phone was rooted (I had no idea officer, honest!). Tried uninstalling and reinstalling, then restoring data from TiBu, but that never works for me because it can never reconnect to the severs to download email. I then had no choice but to restore my nandroid backup (back to Slim 4.4.2) and was again caught. They've got my fingerprints and my footprint. It's all over, kids.

Started getting caught up on the latest developments in the thread, I find the Xposed module's existence (brilliant). With the help of this, I got GFE working again, but using the old 2.4 apk. Updating to the latest GFE in the Playstore does not work with the module for me (I know it does for others)....it force closes itself when it tries to retrieve settings in the setup.

I may try to rewipe everything tonight and start from scratch on PA 4.4, installing Xposed module first, to see if I can successfully switch ROMs. I am on the lam now and ain't nobody gon' bring me back to stock unrooted (*shudder*).

Any suggestions on procedure to follow during the clean-wipe update are welcome.

Planning on as follows:

1. Clean wipe of data + system.

2. Install new ROM, Kernel, GAPPs, etc.

3. Install xposed, reboot, install xposed module 3.1, reboot.

4. Install the old GFE apk (2.4?).

5. If all goes well here, potentially stop and declare temporary victory; alternatively, try just updating straight to the Playstore version to see if that works (as others have had success with). If not....revert back to nandroid and/or old GFE after uninstalls etc.
[Android Software/Hacking General [Developers Only]] TheSilverStig:
Success!!!

This worked! I used the 2.4 apk instead of the 2.5 from the play store and it worked! Using the gfe security patch and that 2.4 apk it finally got it working on my HTC one m8 running 4.4.2.

When I tried with the play store apk and it hung up on retrieving settings and force closed. I then grabbed the 2.4 apk and used the same pin and finally had success.

Thank you so much!!
[Android Software/Hacking General [Developers Only]] jcw122:
I just rerooted my phone after taking a new ROM, and reinstalled the workaround and Good, but after entering my PIN the program force closes at the "Retrieving Settings" step. Any solutions?
[Android Software/Hacking General [Developers Only]] AnteusFogg:
You have to install the previous version of good (apk is somewhere on a previous page) with the previous version of the xposed module, get your pin, then update the xposed module and then update good.
[Android Software/Hacking General [Developers Only]] sean.trinidade:
That depends on what happened prior to flashing the new rom. I've always done the following:

1) Backup and then freeze Good with TB

2) Flash the new Rom

3) Install Xposed and the modules (with all of the various reboots etc.)

4) Unfreeze Good

And it's worked fine. Have done this a few times now on the latest version of both Good and the xposed module and not had any issues.
[Android Software/Hacking General [Developers Only]] AnteusFogg:
That's one way, that only works if you don't have to reinstall good (typically dirty flashing)

If you do a clean flash then your MO is irrelevant.

The person I was responding to has reinstalled good and what he observed is the issue observed by multiple people here where the initial setup would not complete.

And the workaround is what I described afaik
[Android Software/Hacking General [Developers Only]] crackface:
Verify steps

Hi -

I don't wanna piss off our IT mobile folks, so I wanna make 100% sure I have this right before I try it.

Currently on a fresh install of the Hperdrive ROM.

1. Install Xposed v1

2. Install GFE 2.4.0.315

3. Do i now need to get it all registered with my PIN? Or does that not make a difference?

4. Freeze GFE with TB

5. Install Xposed v3

6. Dethaw GFE

7. Optionally update GFE from playstore

I'd love clarification as to when I do the pin registration. Thanks for any input!!!

One other question - Are people finding that they can restart the whole process if Good does the lock/wipe/whatever after detecting root, if they revert back to prev state? I took nandroid backup, and curious if I get a second (or more) try while the activation pin hasn't expired.
[Android Software/Hacking General [Developers Only]] Zirillian:
Few things.

1. At least for me, a PIN is only good for one use only. Once you type it in, that's that. Others may have different experiences.

2. In my personal experience, once Good detected root (this was when I was not using Xposed modules etc.; see my post above), they had me even when I reverted back to my nandroid. The reason why there is once you activate one PIN, your old PIN is now useless and won't sync with your work mail servers. So for me, once I nandroided back after being caught, I had to generate a new PIN to get back to connected to the work severs, and they detected root. They have my digital fingerprints it seems.

3. At least for me, once root is detected you can get out of it easily...just clear the app data, uninstall, reinstall, and start over with roughly the same chance you had before (new PIN needed). If you are using the Xposed modules properly (and the old GFE), then it should block detection on the next install. For me, it is very easy to generate new PINs...so retrying doesn't hurt me.

Your steps may work, but I'm currently having success with a clean rom flash, install xposed, install the 3.1 module, then install the old GFE apk, then type in new PIN from IT. To me it makes the most sense to have the protection set up fully before I even mess with installing GFE or inputting the PIN to set it up. If I upgrade to the new GFE in the PlayStore, it detects my root or the app doesn't start/work, but others seem to be able to update just fine. YMMV.

Hope this helps...
[Android Software/Hacking General [Developers Only]] clintonroche:
+1 Zirillion

You must have either no root or root blocked with the exposed module before entering the pin on your device.
[Android Software/Hacking General [Developers Only]] crackface:
I did this, and plugged in the pin after the initial 2.4.0.315 install, and after it spent some time configuring, I got the lock/disable notification. I may be able to get away with one more pin request, but does anyone know what I'm doing wrong?
[Android Software/Hacking General [Developers Only]] javaguy110:
One thought...did you restart your phone after freezing GFE? There might be a proc still running if you don't. And if something is still running, it may inform the servers of rooted status. At least that's what I did and it worked for me. Also, make sure fast boot is disabled. If it's enabled there may also be the source of a running proc. Battery pull is ideal if you can.

Sent from my Gunmetal Grey M8