yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Fallon:
Big brother is watching...

Copied scripts & renamed spark to a folder on my internal flash

Rebooted, started GFE, no problems

Copied re-named spark to /system/xbin (from within TWRP)

Rebooted, started GFE, no problems

Copied disable_good_enable_root.sh to /system/xbin (from within TWRP)

Rebooted, started GFE, immediate compliance failure :crying:

Will try updating the scripts to random names later & see if they flag that way, but have lost motivation again for the moment.

---------- Post added at 05:28 PM ---------- Previous post was at 05:12 PM ----------

Disabled GFE admin so I could wipe the app data for GFE

Wiped app data for GFE

Deleted just the script from within TWRP

Rebooted

Re-registered GFE with a new PIN & it's happy again

Pretty much confirms that it's targeting the script, not that I had any doubt. Just needed to get GFE working again & figured I'd post a log & status.
[Android Software/Hacking General [Developers Only]] dc300m01:
OK. So I'm now running CarbonRom with baked in SU. Here is what I did:

Downloaded and installed the Full Unroot zip

Rebooted

Played around for a few minutes making sure my root programs didn't work (confirmed)

Rebooted into recovery.

Used file manager to confirm I somehow didnt have the enable and disable root scrips (confirmed)

Noticed busybox was still showing in xbin. Deleted it.

Rebooted

Installed Good.

Been about 10 minutes and good so far.
[Android Software/Hacking General [Developers Only]] RichMD:
I assume there isn't anything special about that ROM having "baked in SU" as far as running Good - correct? Also, I assume you didn't do anything with stopping Good from autostarting - correct? I have CleanROM (fairly stock ROM) but if we run the full unroot then most ROMs would act the same at that point I believe. Is that (running the full unroot script) really any different than running the "full unroot" in the supersu app if you had flashed clean and don't have the scripts installed?
[Android Software/Hacking General [Developers Only]] dc300m01:
Just confirmed. Rebooted a few times with out issue. Unzipped just the disable_good script and renamed it DG.sh and put it in the xbin folder via TWRP and all was still good. Renamed it back to the original in TWRP and as soon as good loaded I got the compliance error.

Well played, Good. Well played.

As a further test, I wiped the Good app data and restarted. Set it back up and immediately failed compliance.

Wiped app data again, restarted into recovery and renamed the script to something else. Rebooted and setup Good again and all is fine.
[Android Software/Hacking General [Developers Only]] calisro:
its different.
[Android Software/Hacking General [Developers Only]] calisro:
ill put our a new zip with new names. ill look into randomizing the names as well.
[Android Software/Hacking General [Developers Only]] dc300m01:
Just a thought, do you have your scripts named something different calisro? Weird that a bunch of us failed compliance, but you were spared.
[Android Software/Hacking General [Developers Only]] calisro:
Nope. I run the same exact one you do. That's what I don't really understand.... Mine still works with those script names.
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Out of curiosity, do you use su, supersu or superuser?
[Android Software/Hacking General [Developers Only]] Noname-2013:
Hi

Sorry for getting back a bit late. Loads of work and and. And sorry for not beeing any help with the development here at the moment. I must stay calm for a while due to trouble getting pins.

Just a thought concerning why calisro is fine when we got busted. Could it be that the IT guys where calisro work still havent updated their system? Or something like that?
[Android Software/Hacking General [Developers Only]] RichMD:
If your full unroot deletes spark and the scripts, can you say how it is different than using full unroot in the su app, etc? Are you leaving some kind of backdoor to make root easy to enable again? Do we have confirmation there are no GFE root violations after?
[Android Software/Hacking General [Developers Only]] RichMD:
I need to install GFE today or my PIN will expire. I have CleanRom 4.8 and will flash full unroot.zip. Is there anything else I should do before activating GFE if I want to be a bit conservativ at this point? I don't want a violation.

---------- Post added at 02:44 PM ---------- Previous post was at 02:01 PM ----------

Tram full unroot And got a compliance failure. Argg
[Android Software/Hacking General [Developers Only]] dc300m01:
When I ran the full unroot I made sure the old scripts were deleted from the xbin folder and manually deleted busybox in xbin folder and it worked.
[Android Software/Hacking General [Developers Only]] unknown_owner:
I called my files Supercalifragilisticexpialidocious.sh and Imgonnaemailutomorrow4sure.sh. Let's see if they add that to their list of files to look for
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
I had to odin back to stock. I needed good for my work emails :( stock att rom sux.
[Android Software/Hacking General [Developers Only]] calisro:
superuser....
[Android Software/Hacking General [Developers Only]] calisro:
Mine deletes all traces of su. the one in supersu removes all traces of supersu. and mine deletes all my stuff as well.
[Android Software/Hacking General [Developers Only]] calisro:
then its finding something else on your phone...... :(
[Android Software/Hacking General [Developers Only]] gveloce:
I come back with my findings. Not having the (proper) way to rename the scripts inside ZIP i did the work on my device.

Renamed the scripts (and changed contents accordingly) reinstalled GOOD (or may be called BAD because torturing us?) then activated it again with new PIN and luckily works witout Compliance Error since yesterday.

If someone could provide a detailed guide to change the scrips inside the ZIp would be very nice.

I think that Callisrob did (and does) a WONDERFUL job for this issue but it s time to go independently and have the scripts customized for ourselves WITHOUT letting Good know their names/paths/internals etc.

If this works we are happy (except Good)

If someones scripts break he/she may post here to ask for advice (better no scripts sharing/posting).

I know this proposal has some drawbacks but if we keep like before it will still be a CAT an MOUSE game as Fallon pointed out.

Any comments welcome!

GV
[Android Software/Hacking General [Developers Only]] calisro:
There are lots of tutorials on xda for modifying flashables...

That being said, I still do not believe they are looking at this thread. They don't care that much. Just look at their SLOW development. GFE can't even keep up on making their app work on jelly bean. their browser plugins still is only compatible with ICS.

If they are catching the scripts, they are getting "lucky". They are probably catching the word "root" in the script. You guys give "GFE" way too much credit...

Anyway, I have some ideas on how to fully randomize the script naming by having a custom installer script where you will pass a word to the script and it will create a hash value based on that word. that hash value will be how the script will be named.... That would make it all unique per device.

My second idea is to push the scripts to a sub folder (also randomized) and then remove the read privileges on that folder. That would allow you to execute the scripts but would prevent some other user from scanning it.

It will take some time to deliver this but in the mean time ill put out a different named script zip.
[Android Software/Hacking General [Developers Only]] RichMD:
Thanks for all your work Calisro. Obviously, I was frustrated when I got the compliance failure again yesterday but it was not directed at you in the slightest. I think your above suggestions sound good (no pun intended). I agree that GFE is poor in development but I think meeting corporate security is their primary focus - not end-user functionality. The hash value for the names sounds good. If you mark any folders "unreadable" though, would that be a very "non-standard" configuration and possibly cause a problem since GFE scanning should have full access short of what Android prevents by default?
[Android Software/Hacking General [Developers Only]] calisro:
No. there are MANY ROMs and some have inaccessible folders. This is just another one of those.
[Android Software/Hacking General [Developers Only]] calisro:
I didnt take it that way... We are all here to keep the river flowing. :good:
[Android Software/Hacking General [Developers Only]] Fallon:
[GUIDE] How to make a cwm recovery flashable ziphttp://xdaforums.com/showthread.php?p=27645882

Probably relevant for people looking to update things on their own.

Calisro's scripts are pretty simple if you know anything about programming or scripting. All you need to do is rename some files inside a .zip & search/replace a few strings in a few text files.
[Android Software/Hacking General [Developers Only]] RichMD:
Has anyone used this (custom script names) and still had a violation?
[Android Software/Hacking General [Developers Only]] gveloce:
Thanks Fallon

Already changed the scripts using vi on my mobile device and since then have Good running again w/o compliance issues.

If vi selection surpiises someone, I explain that although not so probable I am an old (age and knowledge-wise) Unix guy having administered AT&T SVR4 systems some decades ago and was really very happy Android was based on Unix/Linux to try to un-rust my knowledge, but time restrictions did not let me improve so much...

Anyway.

Cheers

GV
[Android Software/Hacking General [Developers Only]] mb:
Any chance of having these scripts to try please? Or any word on v17?

In the meantime, I've been using this app https://play.google.com/store/apps/details?id=com.wwongdev.outlookwebmobile (paid unfortunately) which does work on rooted devices with my employer's email.
[Android Software/Hacking General [Developers Only]] calisro:
ill put a intermediate version this morning.
[Android Software/Hacking General [Developers Only]] calisro:
new ver attached. will add/update op later. new script names are egdr and dger. it will remove the older files....
[Android Software/Hacking General [Developers Only]] Bestbaldmanever:
V17

Finally managed to get round to trying v17 last night. Upgraded to the latest CM10.1 nightly, then installed and ran the scripts.

Got a new pin from our self service portal, and set GfE off and running. 12 hours later I haven't been pinched. Fingers crossed it is working... Although if GfE are monitoring this thread, I'm not sure how long it'll be!

Thanks, Calisro, for all your efforts n this; it's good to have mobile email again.
[Android Software/Hacking General [Developers Only]] Fallon:
Good so far here too.

Installed v17

Used GFE

No problems yet

I haven't engaged root or ran the scripts yet though, just installed em.
[Android Software/Hacking General [Developers Only]] mb:
v17 didn't work for me unfortunately. Busted straight away upon installation. Again, followed the instructions precisely.
[Android Software/Hacking General [Developers Only]] gveloce:
Did you clean GFE data first?

GV
[Android Software/Hacking General [Developers Only]] mb:
I didn't have it installed, so was there nothing to clean? So I downloaded it then ran the scripts. I have always uninstalled it in recent failed attempts to get it working. Then re-downloaded it prior to trying these scripts again.
[Android Software/Hacking General [Developers Only]] sean.trinidade:
v17 working fine for me - installed the scripts, ran the good enabler, then installed GFE and everything is fine.
[Android Software/Hacking General [Developers Only]] Fallon:
No GFE installed

Install v17

Run enable GFE script (removes root)

Reboot (not always needed, but can help clear out apps that got root before the script ran)

Install GFE

Activate GFE

That should work, unless you have something funky.
[Android Software/Hacking General [Developers Only]] RichMD:
I tried these instructions but I apparently am running a ROM that is automatically re-enabling root somehow. I flashed V17 and have run egdr and dger many times via script manager and I see the scripts execute and complete. I keep testing by running Titanium Backup to ensure it can't get root access. After trying multiple times, and running egdr after a reboot I tried TB and it stalled at requesting root. I figured I finally had it working. I didn't do anything other than reboot and ran TB after the reboot and it had root access again...

During the testing (before I finally once got root denied for TB) I ran dger, egdr, dger, and the commands to create GFE.TXT. The files are attached. Any ideas? I could run a different ROM if necessary. It is currently android 4.1.2 (CleanROM 4.8) for the Galaxy Note2
[Android Software/Hacking General [Developers Only]] gveloce:
Are you perhaps using a NATIVESG installation? I had issues with NATIVESD and the only way to use the scripts was to switch to NAND (and miss my WIN7.8-NAND install...)

GV
[Android Software/Hacking General [Developers Only]] Fallon:
Cyanogen based ROMs have a good track record across several users & devices of working in this context.
[Android Software/Hacking General [Developers Only]] RichMD:
I will run official CM 10.1 if that is the best chance of the GFE workaround working. However, would any AOSP or AOKP (not SamSung or carrier based) work just as well? Basically did you specifically mean people running CM haven't had problems or AOSP/AOKP in general?
[Android Software/Hacking General [Developers Only]] RichMD:
I did a factory reset, cleared cache/dalvik, formatted SD and then installed the latest CM10.1. I flashed V17 and ran the dger, egdr and rebooted. I checked TB and root failed. I rebooted, ran egdr again and installed GFE. I completed the setup and everything was working. I rebooted a couple of times - still working. I ran dger and then ran TB and restored 2 apps. I rebooted and then ran egdr - Compliance failure right away.... :mad:

Without doing anything else, I tried TB and it failed to get root access.

Can the workaround be changed so egdr does NOT start good right away - just "disable root" and maybe, just enable GFE enough so it can autostart processes and then reboot before actually running the app? This is just in case it detects that processes that should have autostarted are not yet running when the app starts?
[Android Software/Hacking General [Developers Only]] Fallon:
Read back a couple pages functionality to prevent GFE from auto-launching was put in & only needs a command line parameter to enable it.
[Android Software/Hacking General [Developers Only]] RichMD:
That's not what I was trying to ask. I believe you are talking about how to stop GFE processes from autostarting before the app launches even when it is enablled - just in case we flash a new ROM that enables root again, etc.

Based on what I saw, I was speculating that if the app is started (via the enable script) and the autostart processes were not already running then it is deemed a violation since that shouldn't happen. I assume that when we have enabled root and disabled GFE then those autostart processes can not run. I was thinking maybe the "enable good" script should simply disable root access and enable the GFE autostart processes to run and then reboot. Then the phone would reboot and the GFE autostart processes would start as they normally should. Then when you start the app it doesn't see anything unusual.

I mentioned earlier that if it isn't difficult to run a script in CWR or TWRP to make the changes then that would probably be the safest since no app processes should be running. I know that isn't the most convenient but for some of us, it is our only option to run Good without going back to complete stock. I don't know if I will even have another chance to get another PIN at this point.

I don't want to sound like I am complaining. I really appreciate this effort. :good: I am just trying to suggest ways to create a relatively "foolproof" method.
[Android Software/Hacking General [Developers Only]] calisro:
the app doesn't know anything about if android isn't sending it the "boot completed" when it boots.

in your case, gfe is finding something on your phone and flagging it. a cwm script wouldn't help you. I have not had a chance to look at your logs.
[Android Software/Hacking General [Developers Only]] RichMD:
Thanks but I sent the logs based on a 4.1.2 build I had so I wouldn't bother. The compliance failure I got was after a CLEAN CM10.1 nightly builld. I did a factory reset, cleared cache, dalvik, system and even wiped the internal SD card. I didn't do anything to my external SD card but the internal was completely formatted and I installed CM10.1. As I posted I had Good working with no problems through multiple reboots. I eventually tried disabling good / enabling root and TB then had root access. I restored two apps as a test - nothing requiring root. I then rebooted and ran the egdr and BAM - compliance failure. I had a clean CM10.1 ROM with TB (which was nott run after the reboot) and two insignificant apps and nothing more at that point. As I posted, I even tried TB after getting the failure and it didn't have root access anymore. I did not run anything for to capture the packages at the time but I just uploaded the attached from yesterday morning when I got the failure. I have since installed many more apps (ROM toolbox Pro, etc) so it wouldn't make sense (I assume) to run the commands to capture GFE.TXT
[Android Software/Hacking General [Developers Only]] Milkman00:
Well this is what I was afraid of. There were no real clear directions for running this, and it seems that I screwed something up. All of the files are in /system/xbin. Busybox is installed as well (something else I didn't know was required but seems to be).

There are 5 files in the v17 of the script. the fu I assumed was a renamed su binary, then there were 4 files. 2 seemed to be for enabling and 2 seemed to be for disabling.

I couldn't get them to run correctly using script manager, then I pressed the little root button and now it seems to work correctly to disable root. The problem??? Nothing I do seems to reenable root. Any ideas?
[Android Software/Hacking General [Developers Only]] calisro:
There are directions in the op. if your having issues you can post logs like the op says....
[Android Software/Hacking General [Developers Only]] Milkman00:
If I just copy the 5 files into the /system/xbin directory, what should the permissions be on each of the files??? That could be my problem.
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Read: Yes

Write: Yes

Hidden: No

Or full permissions are: rwx r-x r-x
[Android Software/Hacking General [Developers Only]] calisro:
the cwm script sets the permissions.
[Android Software/Hacking General [Developers Only]] TUDrewser:
This solution is sooooo great. Took me a few days to get everything working right (mostly my screw-ups...read and re-read this thread, all works). I can't tell you how thankful I am for this solution! Great work! I'm seriously giddy that this works so well.
[Android Software/Hacking General [Developers Only]] calisro:
Thank-you sir. Once I get a little more time, there are some more changes coming that will help mask the files further.

EDIT: Also thanks for the big glass of Guinness you just got me.
[Android Software/Hacking General [Developers Only]] Milkman00:
I don't have CWM installed ATM which is why I wanted to copy the files manually and permission them appropriately.

Thanks for the help so far.
[Android Software/Hacking General [Developers Only]] calisro:
This is what the CWM script does... as of v17

busybox mount -o remount,rw /system
---- Copy all 5 files to /system/xbin
chmod 6755 /system/xbin/fu
chmod 0755 /system/xbin/dger
chmod 0755 /system/xbin/r_dger
chmod 0755 /system/xbin/egdr
chmod 0755 /system/xbin/r_egdr
busybox mount -o remount,ro /system
reboot
[Android Software/Hacking General [Developers Only]] TUDrewser:
Good is wanting to update in the app store. Haven't heard of it breaking anything yet, but wondering if I should stay put with old version. Would hate for them to add more root detection or something like that. Guess I could always uninstall the update if it borks things...just curious of anyone's experience with the latest update.
[Android Software/Hacking General [Developers Only]] calisro:
Working perfect for me with the last update of good
[Android Software/Hacking General [Developers Only]] TUDrewser:
Cool, on that note just updated and also don't have any issues. Gracias.
[Android Software/Hacking General [Developers Only]] TUDrewser:
I spoke too soon...shut down on me and detected root. :crying: Cleared data, uninstalled, ran disable good/enable root, installed (but didn't run) set autorun to not start (all 4), set permissions to block read logs, rebooted. Ran enable good/disable root and it's still blocking me as being rooted! Any tips? Or anyone have the older APK I could install to see if that fixes it?
[Android Software/Hacking General [Developers Only]] calisro:
I found the issue. v17 was missing the 'delete' commands for hte old scripts since we replaced them.

I HIGHLY RECOMMEND THAT ANYONE WHO UPGRADE FROM a release before v17 and flashed the v17 from the OP reflash v17. I replaced v17 with the correct one. You will likely have old scripts hanging out there if you dont do this. reflashing v17 addresses it.
[Android Software/Hacking General [Developers Only]] TUDrewser:
I may be jumping the gun and you just haven't updated first post yet, but it appears there are no downloads listed any more...

EDIT: It's there now, thx. Trying new scripts, along with an older version of Good that was on Amazon app store.

---------- Post added at 10:07 AM ---------- Previous post was at 09:41 AM ----------

Ok, new v17 of script plus older version of Good from Amazon App store has got it working again. Honestly, don't know which one fixed it, but as I'm on my 4th PIN request today, I think I need to hold off testing the newer version. Not sure what happened...what a pain. Appreciate the prompt replies though...thanks!
[Android Software/Hacking General [Developers Only]] EVOme:
Any idea why I get this in script manager when I run either of the commands??? Removed Good...reinstalled it, run script. Have not configured Good yet with my email and pin. I get the same error with Connectbot

I am stocked rooted using Casual. Stock rom
[Android Software/Hacking General [Developers Only]] calisro:
your missing the basename command from busybox.
[Android Software/Hacking General [Developers Only]] EVOme:
Awesome!! This is now working great for me. It's great being the admin and check compliance on my device myself. I'm all good to go....darn puns.

Great work on this!
[Android Software/Hacking General [Developers Only]] mb:
Finally got around to doing a "deep clean" of my SGS2, install a new ROM and all seems very well with the new script. No issues so far. Although I was very unlucky to find a real jobsworth on the I.T. helpdesk who has reported me to Information Security for breaking the T & Cs of having the app on a rooted device!!
[Android Software/Hacking General [Developers Only]] calisro:
:banghead:
[Android Software/Hacking General [Developers Only]] dc300m01:
Well, when you hide SU, you loose root access. Technically you're not rooted? :) just show them that you don't have root access anymore!
[Android Software/Hacking General [Developers Only]] RichMD:
Is this working reliably for everyone now? I gave up trying after getting failures so many times - even after a clean flash. However, that wasn't with the latest script.
[Android Software/Hacking General [Developers Only]] calisro:
Try the new script. Fallon was able to determine it was actually detecting the script themselves or the word 'root' in the script or something. Most people have been reporting that its working. If it doesn't for you, then provide logs because you could have something else going on.