yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Noname-2013:
another question - titanium backup

hi,

ok, im on to it. I just installed the titanium backup app to be able to backup and remove the root explorer app. Can i keep the titanium app or do i have to deinstall that one also before the try or can i keep it installed?

thanks
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

keep it. just reboot after using it and before enabling good.
[Android Software/Hacking General [Developers Only]] Noname-2013:
one more thing

ok thanks for the fast reply.

one more thing: Shouldn't I wipe the data of good before i run enable as good starts with it?

Sorry for beeing novice..

thanks so much!
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

nah. when it starts it will just say the "not in compliance" message. then hit home, wipe its data and start it. it will let you type a pin in then.
[Android Software/Hacking General [Developers Only]] Noname-2013:
still issues

nope, that didnt work. It says that either the mail-address or the pin is wrong. I guess i can only use it once.

I did not hit "force stop" before i wiped the data of good.. ok?

I will have to try to get a new pin on monday.

Something else: Do you know some other good synch application instead of this moborobo. I need to synch my device with outlook.

thanks
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

I doubt that moborobo is the problem but figured once you get good working that you would know for sure once you reenable mobo. let me know Monday and its okay that u didn't force stop it.
[Android Software/Hacking General [Developers Only]] AussieHusky:
Worked on my GS2 Running stock with Root, Failed on my Desire running Cyanogenmod 10.1, GOOD detected root
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

I run on cm10.1.
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Same here, no problems with gfe after using the script.
[Android Software/Hacking General [Developers Only]] Noname-2013:
3 more questions before test..

Hi,

Just three more things before I try it (I have the new pin):

1. the etotalk tools? Do you know this "mobile uncle toolset" upon which it is based? (See the screenshots attached to see what is included in the package)

2. the other "good" entries in autostart?

* device admin -> should stay "active"?

* widget update -> should be "deactivated"?

3. why did you ask me to uninstall script manager? is this still valid? (That's the one I've been using the whole time. I think that app is a bit easier to work with but if you mean that it is better to deinstall it and use connectbot, then I will do it)

By the way. Moborobo definitely uses an ADB interface for USB access.

(Note: I can not get new pins as often as I would like to. Therefore I must try to get it straight as fast as possible)

Thanks a bunch
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

I disabled only the boot & reboot (autostart) receivers for GFE. Even this isn't strictly needed. It just prevents GFE from starting and detecting root after you upgrade your ROM (which usually includes a root). It won't be an issue until you upgrade your ROM (and forget to disable GFE first).

Killing GFE's admin access will stop it from working until you restore it. Just let it get admin when it complains & it's happy again. No new PIN or extra effort required.

At one point apparently SManager wasn't working & some people had to use an older version. I wasn't messing with this during that time & have never had a problem with SManager. Current (paid, I bought it) version works fine for me at least. Your mileage may vary.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Thanks Fallon. Let's see what Calisro says to the other points.
[Android Software/Hacking General [Developers Only]] mjgspr95:
Works with Rom toolbox Pro on my SGS2 i777. It has its on scriptor function built in just needed to put the r_ scripts in a romtoolbox folder.

Edit it also has startup manager and freeze/defrost feature too

Thanks
[Android Software/Hacking General [Developers Only]] calisro:
1. the etotalk tools

I have never seen that tool. Could be a trigger for your issues. remove it so you can add it back and see if it breaks good policy.

2. the other "good" entries in autostart?

* device admin -> should stay "active"?

* widget update -> should be "deactivated"?

That works.

3. why did you ask me to uninstall script manager? is this still valid? (That's the one I've been using the whole time. I think that app is a bit easier to work with but if you mean that it is better to deinstall it and use connectbot, then I will do it)

I had it actually detecting script manager on old versions. Im just suggesting to remove it temporarily and run it command line through connectbot for debugging purposes. If you can get it to 'activate' then by process of elimination you can see which app is triggering a policy break by introducing one at a time over a period of time until you get a policy break. Reboot between app installations and run it for a day between app adds.

By the way. Moborobo definitely uses an ADB interface for USB access.

ADB isn't necessarily a problem. All phones have ADB. Its really if you had su'd in a ADB session that causes the problem. but you can uninstall temporarily to make sure.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Pending

Hi,

just wanted to say that I still wait for one message from the company i bought the phone from. Then I will try it. Tomorrow. Sorry for the delay.
[Android Software/Hacking General [Developers Only]] Noname-2013:
etotalk tool 2.x

By the way, here is the tool:

http://www.etotalk.com/blog/?p=473
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

A quick look made me think it needs root although it never explicitly said so.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Still no success

Hi,

I have additionally done the following steps.

1. Uninstalled

scriptmanager

with Titanium (backed it up for possible later use)

2. Reeboot (via Titanium)

3. Uninstalled

atotalk toolkit app

with Titanium (backed it up for possible later use)

4. Reboot (via Titanium)

5. Ran script (disable)

6. Reboot (via Titanium)

7. Ran script (enable) - stopped good

8. Settings>Apps>Good - wipe data

9. Started good and tried to activate

-> Good wiped the account - not compliant

attached you will find the last log files.

any ideas on how to proceed?

Was it ok to do the reboots with help from Titanium?

Note: 1. Titanium an Connectbot both had granted su access when doing the last reboot

Best regards
[Android Software/Hacking General [Developers Only]] calisro:
Hi. Sorry this isn't work for you. I am not sure what GFE is flagging on your phone but I can say with 99.9% confidence that it is some app. GFE's detection is pretty simple. If looks for these things:

1) /system in RW mode meaning it can be modified.

2) su binary in 'common' locations such as /system/xbin or /system/bin.

3) apks that look like they are superuser such as *supersu* or *superuser*.

4) package names (after an apk is loaded it has a package names as outlined in a apk's manifest. This is why I can rename a apk to bob.apk and it will still install as 'es explorer' or whatever it is. In the case of GFE, it looks for something like this:

*com.noshufou.android.su*

*eu.chainfire.supersu*

5) it will check background processes and looks for sessions that have an active shell with root privilege. I need to figure out *how* it does this.

6) it attempts to look in the system log for 'su like' activity. Probably combing that file for the package names.. In JB, it cant do that as it doesn't have permission to open the system log.

Let's try this. Let's look more deeply at #4,#5, #6 above.

Get me this from a root connectbot session please:

pm list packages > /sdcard/pack
pm list permissions > /sdcard/perm
ps | sort >/sdcard/psout
[Android Software/Hacking General [Developers Only]] wrxdrunkie:
Hi all,

Thanks for the guide it was really helpful!

I am currently running CM10.1 nightly build with the .33 radio. I got LTE working this morning and now just need to remove root so I can install GFE. I followed the guide and flashed the latest zip but I seem to have lost my connection completely? Any ideas of how that happened? I can only make emergency calls....

edit: nvm! new sim card was activated! Now for the moment of truth. To call my it department and see if I can get good working properly.

Darn. I did the script part incorrectly. Do I have to run the script everytime or once I have done it it should be good to go? I don't plan on re-enabling root.
[Android Software/Hacking General [Developers Only]] Noname-2013:
New logs

Hi and thanks for your fast reply.

I wont give up yet :)

Attached you will find the requested logs.

One more thing. I think i wrote this already but i have two launchers. ( It was installed that way). I still have not decided which one i want to use so i still have the question coming up every time the device starts or when i press home (see screenshot). No idea if this is of interest...

Best regards and thanks
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

paste this result please:

su
set -x
pm path eu.chainfire.supersu
pm path eu.chainfire.supersu.pro
[Android Software/Hacking General [Developers Only]] miyklusha:
Do not use Titanium. Looks like it course problem for Good Client. My account was ok on the server, but after I run Titanium I got "Good wiped the account - not compliant". But from the server side it was in compliance.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

if you use it, reboot before enabling good again... its ok to have it installed.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Result

result:

u0_a107@android:/ $ suu0_a107@android:/ # set -x
+ precmd
+ typeset e=0
+ let e
u0_a107@android:/ # pm path eu.chainfire.supersu
+ pm path eu.chainfire.supersu
package:/system/app/Superuser.apk
+ precmd
+ typeset e=0
+ let e
u0_a107@android:/ # pm path eu.chainfire.supersu.pro
+ pm path eu.chainfire.supersu.pro
package:/mnt/asec/eu.chainfire.supersu.pro-1/pkg.apk
+ precmd
+ typeset e=0
+ let e
u0_a107@android:/ #

Was this what you were looking for?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

yes. :) Uninstall supersu pro key. you can readd it after I update my scripts for you. I bet that is what is triggering it.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Ok... but how..

Hi,

not sure how you mean. you mean i should downgrade from supersu pro to standard supersu?

(sorry for being a very new to android)
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

when you install and buy supersu, you'll install the free one and then buy a key to allow the free one to work as a pro version. they are technically two apps installed for that. you should be able to just remove the pro portion.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Excactly what i thought... but.

When i check the app list or the sw list in Titanium, there is only one entry:

SuperSU Pro

I guess i will have to deinstall it and install the standard version right? As far as I understand it this will be a quite straight forward activity? right?

Or is there something special to keep in mind?

---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------

Note: My phone was delivered with SuperSU. I upgraded it to PRO.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

its straightforward. you won't lose supersu. its a system app... so uninstalling supersu pro will leave behind supersu.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Right

you were right. I just unnstalled (backed up with Titanium) SuperSU Pro and the Free version stayed. So far so good.

you want me to check something else as well? (I will order a new pin tomorrow or do you reckon it makes sense to try it out with the old pin?)
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

old pin if it works....
[Android Software/Hacking General [Developers Only]] Noname-2013:
nope,

it does not. It says: "The email address or PIN you entered is incorrect".... What the heck, it was worth a try.

I will then have to get a new pin.

Please check if there is something else which might be the error so that I can disable/uninstall that as well.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

that is a policy the company sets if they want reusable pins. mine is always reusable.

nah. I think that is it...
[Android Software/Hacking General [Developers Only]] Noname-2013:
Hi,

It will take me a while to get a new pin due to the Easter holidays :(

I will report as soon as I can ;)
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Install the .zip

Run the script to remove root

Forget about it until you update (CM will reinstall root when installed/updated)
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

no prob. I'm pretty sure that was your issue so you should be good to go. I just need to update the scripts to handle supersu pro....
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Possibly a noob question/statement, but I presume this will work with the superuser app from koush?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

yes. I'm using that.
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Thanks - and do you use ConnectBot or ScriptManager?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

I use connectbot
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

I use SManager with no problems.
[Android Software/Hacking General [Developers Only]] dc300m01:
Having an issue. I can't return to root for some reason. It just sits on the attached screen. Running JB 4.2.2.

I was using this for a while on my old rom (JB 4.2.1) without any issues. tonight I flashed a new rom (4.2.2) and didn't realize my PIN expired a week ago. I wanted to enable root until i get a new pin.... but it just hangs?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

flash sparky su alternative in op and try again. also post the logs in /sdcard gor me to look at.
[Android Software/Hacking General [Developers Only]] dc300m01:
Thanks! That worked. Logs are attached.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-01-2013] root workaround

awesome. v14 will have that fix in it.... thx for confirming.
[Android Software/Hacking General [Developers Only]] mb:
Re: Good for Enterprise (GFE) [04-01-2013] root workaround

Locked out for having a rooted device today for the first time.

Upgraded to v14 before I did it. Also using Kernel: XWLSN-4.91.5-PhilZ following an update to Neat ROM 4.6 yesterday. This might be related?

Hope you can work your magic again! Log file coming...
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-01-2013] root workaround

what steps did you do for upgrading? including when did you reboot and flash and when did you run scripts.....
[Android Software/Hacking General [Developers Only]] sean.trinidade:
Is the only change to v14 the superuser apk that is used? I only ask is that I have installed v13 at the weekend which seems to be working fine with koush's superuser, so don't really want to touch it unless there are other bug fixes included.

Btw, thanks to everyone who helped me get this up and running. :)
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-01-2013] root workaround

It doesn't change the device superuser. It won't remove or replace Koush's superuser. It changes the "backdoor" su used to reroot your phone with whatever you had installed prior to temp unrooting.

There would be no chg in implementing the new version but there is also no need to upgrade if things are okay.
[Android Software/Hacking General [Developers Only]] mb:
Upgraded my ROM yesterday (CWM flash of a ZIP). Also did a further reboot very early this morning (a fair few hours before running these Good workaround scripts) in order to do a CWM backup. Ran v14 script late this morning. Also, I always execute the Good scripts via Root Explorer, which threw up a "can't get root, try again" error message. Second time it executed and then Good told me off for non-compliance. But this was the first time I've seen an error like that with Root Explorer, which might be a co-incidence. Either way, this was the first time I've ever had a problem with your scripts not working for me.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-01-2013] root workaround

Before you flashed your new rom, did you run the disablegoodenableroot script? If not, then good likely detected a compliance problem well before you tried to run the scripts but after you flashed the rom.

I've found on a first boot of a new rom that if your not very careful how you do it that you may have an issue.

Do you remember if you disabled good prior to flashing?

The correct order is this:

1) disable good enable root

2) reboot cwm

3) flash rom and do any other rom specific instructions

4) boot into rom

5) set it up as you like with root...

6) run disable good again to make sure things are well after rom flash

7) reboot

8) use scripts as normal

I think this will be good info for the op. ill clean the directions up and put it there for others.

IT'S LIKE DANCING AROUND A LAND MINE!
[Android Software/Hacking General [Developers Only]] calisro:
FAQ section added to the OP. As we get more 'info', we'll put it in there. Maybe it will help someone. :highfive:
[Android Software/Hacking General [Developers Only]] mb:
Almost certainly I didn't follow those instructions. My bad. And yes, that would be incredibly helpful so I have them here to stop me from being a naughty boy again.

By the way, is it easy to get your "disable Root..." script NOT to launch Good after running (or at least ask if you want to run it)? I run AdFree just to double-check that root is disabled before I launch it.

Thanks again for all your efforts with this. It's the biggest pain in the backside of all the Apps on my phone to get re-instated with my employer's IT contractor! Bet they love me calling every week.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-01-2013] root workaround

ill add a command line option allowing you to stop it from launching. stay tuned.
[Android Software/Hacking General [Developers Only]] dc300m01:
Re: Good for Enterprise (GFE) [04-01-2013] root workaround

Thanks for asking for this! I knew there was something I wanted to ask but forgot.

Thanks for hooking this up Calisro.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-02-2013] root workaround

v15 now has an option to turn off auto launch. The "default" will remain to auto launch however. People not wanting to disable it do not need to change anything....

To disable it add a space and a zero after the script name as a parameter. Like this:

Before

/system/xbin/enable_good_disable_root.sh;exit

After

/system/xbin/enable_good_disable_root.sh 0;exit

if your using another app besides connectbot to launch, there may be a different way to pass command line arguments to a script. If someone finds it different in script manager, paste some instructions and I'll put in the op.
[Android Software/Hacking General [Developers Only]] dc300m01:
I'll check it out in SManager. What's the proper way to upgrade? I'm running v13. Just DL and flash?
[Android Software/Hacking General [Developers Only]] calisro:
Just run the disable good script to return root. reboot into recovery. Flash said zip. Boot (no need to clear cache or anything) and test it. Thanks a lot..
[Android Software/Hacking General [Developers Only]] dc300m01:
Re: Good for Enterprise (GFE) [04-02-2013] root workaround

Worked! Screens attached. Thanks!

Edit: that first screen will appear every time you run a script and it saved the argument after the first time I entered it. I "tested" it 2 times (I sometimes get an error "xposed blah blah blah whitelist blah" while running the enable_good script and Good would lock if I didn't kill it and reboot first.)
[Android Software/Hacking General [Developers Only]] calisro:
thanks for testing. It probably wont hurt anything but you can remove the ;exit from the script manager arguments. thats only for connectbot. you should only need a zero in there.... Thx!
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [04-02-2013] root workaround

Might want to add an exit/completion message on the next ver. "Script complete, GFE should now be enabled" & "Script complete, root should now be enabled". I use to wait & wonder if the script was still grinding away at something while it had already finished. Not sure if Connectbot is any better, but SManager isnt clear when it's done running a script.
[Android Software/Hacking General [Developers Only]] sean.trinidade:
If you check the OP, there's an example command of getting the script to exit as soon as it's completed - I use it on connectbot which works fine.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-02-2013] root workaround

ill add that.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-02-2013] root workaround

yes. works good for connectbot. script manager isn't the same so ill just add it... real easy...
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [04-02-2013] root workaround

New minor update with script completion messages. v16.