yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Noname-2013:
Success!

Hi,

I upgraded to the last version earlier today and it works!

I can not say more than this: Calisro; you are the man! Thank you very much for the brilliant support.

Activities today before the tryout:

- deinstalled GFE

- Flashed new scripts (v16)

- ran "disable_good" (just to check)

- ran "enable_good" (just to check)

- ran "disable_good" (just to check)

- installed GFE

- disabled GFE in autostart

- reboot (via titanium backup)

- ran "disable_good"

- ran "enable_good"

- entered new key

- it still works since ~4 hours :)

(I use Connectbot)

Lessons learned. This trick works also with the "mod rom" from etotalk. My issue seem to have been the supersu pro add-on app.

I still have not tested the disable_good script. I will try this in a couple of days and then I will start installing the apps I uninstalled again to see if it works with them as well. I will come back here with information on what works and what does not.

Apps I did uninstall were:

- etotalk tools

- Moborobo deamon

- SuperSU Pro (You still have not included the SuperSU Pro disabling in the scripts have you?)

*Edit*: Forgot those:

- root explorer

- Scriptmanager (version mentioned in op)

One question: When being in when Enable_Good_Disable_Root mode; can I start any of the applications autstarts, busybox, titanium backup or should i better let those apps "sleep" ?? I guess yes as they require root? Am I right?

Regards and many thanks
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-03-2013] root workaround

When you've disabled root, you can run any apps even root ones but they won't get root since its disabled.

and yes I need to figure out how to deal with supersu pro still.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Disable

Ok, thanks for the infos:

Now i have tried the Disable Script.

Works fine. I will report later regarding the other apps.

Best
[Android Software/Hacking General [Developers Only]] mb:
Tried running v16 disable script with Root Explorer so I can do a "dirty flash" (great name!) but get a text output screen which has the line "echo $BKUPSU not found" then aborts. How can I get this script to run? Not sure what's going wrong to be honest. Thanks in advance.
[Android Software/Hacking General [Developers Only]] calisro:
reflash v16. the files that the zip deploys aren't in place.. the only way that can happen is if you flashed a rom and over wrote /system.
[Android Software/Hacking General [Developers Only]] mb:
I reflashed the PhilZ kernel, then the scripts worked fine. I've yet to run Good again but will do that on Monday when I.T. support are back waiting for my usual "hello, my phone is non compliant again" call :)
[Android Software/Hacking General [Developers Only]] calisro:
Does your pin only work once? I can reuse mine....
[Android Software/Hacking General [Developers Only]] mb:
Just the once unfortunately. I fell victim to this last week and had to call for another one.

I followed your "dirty" upgrade to the letter but it still detected I was in root and broke. So, I installed the latest Speedmod Kernel instead of Neat ROM's default PhilZ kernel with much better results. Your script worked fine and Good did not complain.

There must be something in PhilZ's Kernel that isn't compatible with your scripts. Thinking back to before I started having problems, Speedmod was the only kernel I was using and everything was fine. But when I did a dirty upgrade recently with PhilZ it all went wrong.
[Android Software/Hacking General [Developers Only]] Milkman00:
Hi all:

I looked through this thread and didn't find the answer to the following question, so please forgive me if it has been answered.

While I have had rooted Androids for a few years now, and have even flashed ROMs, I am unclear on how to execute this script. So here are my questions:

I assume I need to download some app to run the script right?

I assume that before running the script that root must be enabled through Super SU. Any other options that I need to be aware of??

When root is temporarily disabled, how does the script re-enable it without root access??

Will this work with a rooted

STOCK

ROM????

Anything else I should know?

My phone is an AT&T Note 2. Thanks in advance for the help?
[Android Software/Hacking General [Developers Only]] calisro:
milkman,

I assume I need to download some app to run the script right?

connectbot or script manager. see the op.

I assume that before running the script that root must be enabled through Super SU. Any other options that I need to be aware of??

correct. nothing else but I usually like to use the "make system app" because its quicker to root/unroot if its a system app.

When root is temporarily disabled, how does the script re-enable it without root access??

hehe. there is a file called "spark" that is an insecure su renamed to spark. it will give it root.

Will this work with a rooted

STOCK

ROM????

should be fine.

Anything else I should know?

any other info in the op...
[Android Software/Hacking General [Developers Only]] RichMD:
On my first attempt, something was wrong and I got a compliance failure. I have since completed a full wipe and ran the scripts again. Before attempting to run Good, I tried running TB to ensure it couldn't get root access. It just paused at requesting root so I know it is working. I know that I should reboot before running Good (just in case).

However, the point of my post is that maybe you should include a "test" action in your instructions for dirty or clean wipe. If everything is set, some test app should fail to get root access. If it does, then you are probably safe to reboot, run the script again and run Good. Just a thought for any of us that it is a pain to get a new PIN.

I would use TB to "freeze" Good after disabling it and then flash the new ROM. Then after everything is setup, (and good is disabled), I assume you could defrost it, disable it again to be sure, and then reboot. Would that work?
[Android Software/Hacking General [Developers Only]] calisro:
All TB is doing when you "freeze" is disabling the user via the 'am' utility. My script in fact is doing that... So you can't freeze the app since its frozen. :)
[Android Software/Hacking General [Developers Only]] mb:
I wholeheartedly agree with this. The disable script needs to check there's absolutely no Root BEFORE running Good. Or at least give you the option to bail out and check yourself with AdFree or whatever.
[Android Software/Hacking General [Developers Only]] teddosan:
Bizarre and frustrating!

So I've been happily running these scripts to root and unroot my SGS3 quite happily for a couple of months now. I've flashed the ROM every now and then to install a later CM10.1 nightly and all has been well.

I last did that a week or so ago, reinstalled the scripts, ran them, made sure Autostarts was stopping Good starting up after reboot, etc. everything was fine.

Last night, all working well. Battery died, so I plugged it in to recharge. Boot it up this morning and I get a non compliance error. Whatever I do, it won't let Good start.

I haven't had time to wipe all the data and completely reflash the ROM yet, but it is massively annoying. The thing that puzzles me is: what's changed? I haven't reinstalled and software, flashed the ROM, nor even rooted. Root was frozen last night, it was all working, battery died. Root was still frozen this morning, but Good is now detecting something that means it won't run.

Any thoughts on what that might be?

Thanks for any help or advice anyone can give.

Cheers

Ted
[Android Software/Hacking General [Developers Only]] mb:
I agree with the previous post. Something has changed. I wasn't in root and it's just booted me out WHILST RUNNING for having a rooted device. It's now locked for non - compliance. That's never happened before. Aaargh.
[Android Software/Hacking General [Developers Only]] teddosan:
Changed...

Glad it's not just me (although sorry it's happening to you as well).

I just don't understand what's changed though. I've not updated Good, I haven't updated my ROM or kernel, and I haven't updated any other apps... At least not between it working and it not working. I just can't see where the change has come in. Agreed, though.

AAAAARRRRGGGHHHHH!
[Android Software/Hacking General [Developers Only]] dc300m01:
Happened to me too! I think Good did something sneaky!

Yup. Just cleared the app data from Good, ran the disable good script, ran the enable good script, restarted, went through the good setup and failed the compliance check.

I bet they monitor this thread ;)
[Android Software/Hacking General [Developers Only]] RichMD:
Is there any way this could be set up even safer such as you have to use CWR to flash to get root again?
[Android Software/Hacking General [Developers Only]] dc300m01:
I don't think so. I think Good connects to a server to do the compliance check... So all they have to do is update the server with new checks.

I had the same issue today and I didn't change anything. It was working fine last night, but not this morning.
[Android Software/Hacking General [Developers Only]] mb:
Same here too. Nothing changed. Was working lovely yesterday after a PIN reset. Seemed to boot out and moan this morning after it had finished a sync. I was DEFINITELY non-root, as I always run a couple of apps just before to be absolutely sure. No updates as far as I know from the Play Store. Weird. I daren't call I.T. and ask for yet another PIN reset today!
[Android Software/Hacking General [Developers Only]] dc300m01:
Your Pin is only good for a day? Ours is good for 2 weeks. Go to settings, apps, Good, and clear cache/data. This will reset the good app and you can try setting up with the same pin.
[Android Software/Hacking General [Developers Only]] miyklusha:
You PIN normally is only good for one activation.
[Android Software/Hacking General [Developers Only]] dc300m01:
Weird! I used my first pin about 10 times in 2 weeks until it expired. My current pin is on its third use since 4/1. Maybe it's a company specific thing?
[Android Software/Hacking General [Developers Only]] miyklusha:
Yes. PIN can be allowed to be reusable, but this is not default GOOD server settings.

Anyway, Good quit working on my phone as well last night. I definitely was not rooted. Tried to reactivate 5 times - no luck.

Something has changed. I was running fine for more than a month.
[Android Software/Hacking General [Developers Only]] calisro:
It is part of the policy. My pin never expires and can be reused. Some expire. Some are one time use, etc....
[Android Software/Hacking General [Developers Only]] mb:
If only! It's a one-time PIN with my employer sadly.
[Android Software/Hacking General [Developers Only]] calisro:
:) Your 'check' isn't needed. Just because adfree or titanium doesn't get root, does NOT mean that components of root are not still present and Good will fail compliance. The script will NOT complete unless the components are gone. That being said, if there are back ground processes still retaining root in a sh session then you will get compliance errors even though 'root' is gone. These scripts are prone to errors. Its a nature of the beast.
[Android Software/Hacking General [Developers Only]] calisro:
you can attach the logs requested in the OP. These scripts are not perfect... When your phone crashed, it likely rerooted itself on the boot and that caused the compliance failed. Have you reactivated good? Once you get a compliance error, you need to reactivate it. Rerunning it will always show a compliance error until good is reactivated. You can wipe good's data and then reactivate with a PIN.
[Android Software/Hacking General [Developers Only]] calisro:
I feel your pain. the thing is, that if you find getting PINs aren't easy, then this will be painful for you. I will tell you that this solution is NOT perfect and you will get lockouts. I do sometimes for no apparent reason. but its very rare. Months go by without issues then I make a mistake (like leaving es explorer with root privileges for example).
[Android Software/Hacking General [Developers Only]] teddosan:
GFE

Yep. Reactivated several times. Deleted and reinstalled twice. Haven't reflashed ROM and reinstalled from scratch yet. Don't really want to have to, tbh, but will try if necessary.
[Android Software/Hacking General [Developers Only]] Fallon:
Pretty sure GFE changed their detection or something.

I haven't enabled root in weeks & have been running GFE just fine. This morning it blew up with rooted compliance failures.

Will investigate here tonight and see if I can find what is tripping it. My guess would be spark. My PINs only work once, but I can get new ones easily through our good web portal.
[Android Software/Hacking General [Developers Only]] calisro:
What iss interesting is that mine blew up this morning as well. BUT I reactivated it and all is well. If it was a change in compliance, wouldn't it still have failed? Been using it for hours now. Still not detecting spark or anything else. If it was spark, there are ways to further obscure that so it couldn't find it.
[Android Software/Hacking General [Developers Only]] dc300m01:
Tried reactivating twice today and it failed both times. I even got to the part to enter a password and thought all was well, but then it blew up.
[Android Software/Hacking General [Developers Only]] calisro:
logs and debug stuff from op.....
[Android Software/Hacking General [Developers Only]] mjgspr95:
Got me this morning too... now IT is saying it can't issue new pin... gbfkm!
[Android Software/Hacking General [Developers Only]] atulsaini_22:
Mine also not working, it was working till yesterday. Please help!!!!
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Provide logs
[Android Software/Hacking General [Developers Only]] RichMD:
Further obscuring spark is what I was thinking when I asked about using CWR or TWRP to flash when you want root access. If the kernel is rooted, couldn't you have a flashable zip that puts spark back when you want root? I'm just throwing ideas out hoping it might help. If it wouldn't work or doesn't make sense then no harm...
[Android Software/Hacking General [Developers Only]] calisro:
Spark isn't causing issues as of yet and I doubt it ever will. I prefer to be able to switch back and forth between good and root daily... that's the whole point of scripts. if we wanted yo filly unroot and reroot via cwm, its doable but a royal pain in the ass.
[Android Software/Hacking General [Developers Only]] RichMD:
Thanks,

I know it would not be as convenient but for some of us, the next policy violation can be the last we will be able to run Good. Therefore, some of us (such as myself) would prefer a little inconvenience to enable root only when necessary. Using supersu to remove root and then dirty-flashing the ROM would get root back but system apps, etc are affected. If you think it would make it much harder for GFE to detect (essentially needing to look at the unsecure kernel) then that might be helpful for us. I know there would be items such as how to disable Good after flashing the zip, etc but just a thought. I know you didn't originally write the process with this in mind but some of us would really appreciate it if it would make the procedure much less likely to be caught. I just got my account restaged after a violation but am not setting it up yet since I don't know if I will get another shot and hoping something will be figured out soon.
[Android Software/Hacking General [Developers Only]] calisro:
no promises but ill look into flashable zips to root/unroot. its possible... the ONLY thing it would help with is "left over" background processes and mistakes. there are some caveats as well... some roms reroot on reboot.... that will cause issues as well.
[Android Software/Hacking General [Developers Only]] dc300m01:
Here are my logs, minus gfe.txt since I don't know how to generate it with SM.

if you see "kraps" in the log, i just renamed spark while trying to kill some time at work... didn't work lol
[Android Software/Hacking General [Developers Only]] calisro:
the gfe.txt is the most important....
[Android Software/Hacking General [Developers Only]] dc300m01:
Done! I deleted my old logs (don't remember doing it) but you have them anyway.
[Android Software/Hacking General [Developers Only]] mb:
Logs before the last blow up hereby attached. Can't find gfe.txt. Where does it reside?
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
I was using it just fine tool now from a month or so... but today I just got randomly 'root device detected' message...
[Android Software/Hacking General [Developers Only]] mb:
Totally broken I think. Just started from scratch and it still detected root when it was installing. I give up!
[Android Software/Hacking General [Developers Only]] atulsaini_22:
where i can find logs??
[Android Software/Hacking General [Developers Only]] calisro:
its not totally broken. but I can tell you frustrated.... This is why I say in the op that if you can't get pins easily that this may not be a great solution for you...

mine is still working after a reactivation from yesterday... They must have pushed a chg yesterday since so many got pinched but I'm still working so it can't be *that* broken.
[Android Software/Hacking General [Developers Only]] calisro:
try reading the op.
[Android Software/Hacking General [Developers Only]] Bestbaldmanever:
What's interesting is the difference between your system and those of us who have been burned. If it's a server side compliance check they have changed, then what is different about your (and others who may still be working) system and ours? What version of Good are you running? And what device, Android version, kernel and ROM?

Oh, and name rank and serial number too please ;)

seriously, though, thanks for your help on this; even if I never getit working again it's better to have Root Good and lost than never to have had Root Good at all.

or something.
[Android Software/Hacking General [Developers Only]] calisro:
k

My rom/phone is in my signature but its not a rom thing. GFE makes their checks generic on purpose to mesh with all phones.

I was pinched yesterday too along with the rest... But mine reactivated clean. I think that they pushed a new policy down. I saw on their knowledge base that they botched a server side upgrade at the beginning of the month that may have contributed.

I'm sure the people that are having trouble could get activated if they didn't have trouble getting pins. Whomever would like to try, I'll work with but if that person has trouble getting pins its fruitless.

I believe the last round of failures are false positives. I believe they are not detecting anything new...

we'll see if flashable root/unroot zips will be better for some. scripts work fine for many though.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Mine is down as well....

Tuesday morning when I woke up I had an alert message from Avast on my device regarding the avast-log.txt file. "Invalid context during scan". Then when I started Good I went "uncompliant".

I updated the Avast app and tried again with a new pin. No change!

JFYI :(

(Edit: Sorry, day was wrong before....)
[Android Software/Hacking General [Developers Only]] dc300m01:
I'm good on PIN #s as far as I know.

I hadn't changed anything in the week leading up to getting busted.

Tried multiple times to get it to work again to no avail. Tried through SM, installed connection, still nothing. I'm going to restore one of my phone backups and see what happens.
[Android Software/Hacking General [Developers Only]] calisro:
did you follow the directions in the faq for a dirty flash to the T?
[Android Software/Hacking General [Developers Only]] mb:
I can get a new PIN easily enough. Thankfully our outsourced I.T. department is big enough to get a different person every time. However, it costs my employer around £5 per support call. As I'm now averaging about three PIN resets a week, someone somewhere is going to look at a spreadsheet at some point and pull me up on it.

I don't know if this is useful, but I've noticed that I get a crash about "GApps" has stopped responding (sorry, can't remember the exact words) whenever Good starts up. Is it checking for something being installed, or a history of something installed I wonder?
[Android Software/Hacking General [Developers Only]] calisro:
Android doesn't keep history.... play store does but gfe has no privileges to get purchase info for an account from the play store.

I gotcha about the support call costs and reports. :) We have a website for pins or we'd be getting charged for support calls too.
[Android Software/Hacking General [Developers Only]] calisro:
Let's get this train moving again.

I'm curious... It seems looking at the logs of the people who did get pinched, all of your had supersu installed and all of you had it installed in /data and some of you have multiple (one in data and one in system because of an upgrade). I never have it installed in data and I never keep more than one.

Fallon, What is your setup? supersu or superuser and do you have it only installed in /system, /data, or both? Im asking you because you'd had good success with this as I have and figured it would be good to compare notes

So... It may be a useful exercise to reduce the variables here. For the persons getting activation errors, Let's try something to see if this becomes more resilient if your okay with my proposal.

Let's try NOT using supersu. It does some funky things sometimes like leaving hanging processes out there (and its not opensource). I'm going to create a FULL UNROOT zip that will remove all known traces of superuser (as long as its not the newest version which is baked into the framework of CM) and supersu. Then we will install the latest apk version of superuser found here:

http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip

Give me a little bit to create a full unroot. If you know what you are doing, feel free to do that manually and if you want me to verify that you have fully unrooted and installed the above superuser, send me the gfe.txt log after you do it.
[Android Software/Hacking General [Developers Only]] calisro:
Attached is a FULL_UNROOT for removing all traces of supersu or superuser from your phone. This can be run on any phone including newer CM phones that have superuser baked into the rom's framework. It will not remove the framework stuff in that case and will only remove all other traces including the 'su' binary.

Once that is run in custom recovery, you can reinstall a standard superuser into /system with a custom recovery zip from here with 3.2-RC3 being the newest:

http://androidsu.com/superuser/.

*** If you have a newer version of CM with superuser installed in the framework, then you should dirty flash your rom to restore the su.

That should simplify your superuser installation. Once you've simplified, follow the 'dirty flash' instructions in the FAQ to see if you can again activate.