yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] gorthon:
Do you mean Blackberry work works with this or just the installation of Magisk?
[Android Software/Hacking General [Developers Only]] ghbuur:
i think blackberry could work with magisk but you have to try. unfortunately i cannot try as we still use gfe..
[Android Software/Hacking General [Developers Only]] Wild01:
Can you please tell me the exact steps. I am using old version of good with exposed in exodus MM rom. Moving to remix with magisk. Can we use new version of good with magisk?
[Android Software/Hacking General [Developers Only]] ghbuur:
first make a backup of the existing good with titanium then uninstall it. after updating rom/installing magisk just be sure to pass completely safetynet within magisk app. if all is green, install good from play store without setting up. just go in magisk hide and hide good from the list. as once something is hidden, after uninstalling and installing again, it will be hidden automatically again. so now delete good and restore your titanium backup. if it works, you can even update good from play store ;) that's how i did on s7e with superstock rom and it works great!
[Android Software/Hacking General [Developers Only]] Wild01:
WOW. Thanks a lot. working flawlessly. it was not able to restore the data from backup. But accepted the new pin
[Android Software/Hacking General [Developers Only]] gorthon:
Cool, now we just need confirmation that this also works with Blackberry Work.

One question, though: Do you still have XPosed running? I use XPosed for many other cool features it offers (just alone GarvityBox) and wouldn't like to lose it.
[Android Software/Hacking General [Developers Only]] Phantasm4489:
Newer versions of good will never work with xposed. It specifically checks for xposed and crashes out
[Android Software/Hacking General [Developers Only]] gorthon:
Even with systemless xposed / Magisk?
[Android Software/Hacking General [Developers Only]] Phantasm4489:
I don't know about that I'm afraid
[Android Software/Hacking General [Developers Only]] rocky78:
hi,

for whom that want's to know...

i can confirm good for enterprise (last version from play store) is working on nougat 7.1.2 (aosp extended v4.1 by marchetto96) with magisk v.12
[Android Software/Hacking General [Developers Only]] schorty:
hi,

I need to use Blackberry Works and my plan is to root my Samsung S7 edge (to get the 2nd SIM working).

Did somebody get the BB Work running on a rooted device?

Schorty
[Android Software/Hacking General [Developers Only]] ghbuur:
hey. i guess with magisk and its root/magiskhide it will work...
[Android Software/Hacking General [Developers Only]] gorthon:
This has been asked here many times, without anyone being able to confirm it.

So here is news: Yes, Good Work can be run on a rooted device with Magisk. This probably also applies to Blackberry Work, but I can only confirm what a friend of mine got running:

- policy of his Good/Blackberry Work administrator does not allow it to run on rooted devices

- he completely wiped his device including local storage and SD Card (Good is known for reporting false positives on non-rooted devices just based on some remains it finds in storage)

- he then installed TWRP and Helium Mod, which is rooted systemless with Magisk, on his device

- installed version 2.4.something of Blackberry Work, which was still called Good Work.

- enabled Magisk Hide in the Magisk app and selected Good Work under the Magisk hide options there.

- Done, it will work and not detect root. He then restored all his other apps with Titanium Backup.

If you try this with a more recent version of Blackberry Work, please let us know the results.
[Android Software/Hacking General [Developers Only]] schorty:
Thanks for the guidance. I'm still a bit shy to root my biz phone and try this.

Did somebody already got Work running on a rooted Samsung S7 edge??

Thanks

Schorty
[Android Software/Hacking General [Developers Only]] gorthon:
Yes!
[Android Software/Hacking General [Developers Only]] schorty:
Thanks Gorthon,

What Work version is running on your device?

I want also to change my single SIM device to a dual SIM device (reason for the root). Do you have also experiance with this?

Thanks

Schorty
[Android Software/Hacking General [Developers Only]] gorthon:
See my previous posts.

I am unaware of a possibility to get dual SIM to work just be rooting. But if you get this done, it would be great if you could let me know.
[Android Software/Hacking General [Developers Only]] ddimple4:
I've been using this solution for GFE for a couple of years without problems.

Now my company will be switching to MobileIron. Anyone managed to keep root with a MobileIron setup?
[Android Software/Hacking General [Developers Only]] redhonker:
Same here. GFT will stop working at my company. Now it's BlackBerry Work.
[Android Software/Hacking General [Developers Only]] calisro:
hehe. I was just typing something similar to your analysis. So here is the deal. There are some root tools that 'hold on' to root even though the su and apk are removed. That isn't to say that you have to remove titanium backup. But if you work with some root tools, you should reboot before re-enabling good. Titanium is one such tool. Other circumstances that I usually reboot before enabling good is if I was working in ADB as root. Then before enabling good, reboot. In connectbot, if you were in a 'su' session, make sure you exit out of that session before enabling good (no need to reboot there).

But the lesson here is that you can keep these root tools installed but if you use them to do a restore, for example, then reboot before enabling.

I'm pushing out a newer version of hte scripts today (better logging mostly) and I'll also add a command to terminate titanium before enabling since titanium is a pretty common app for people to use. Obviously I can't anticipate all root stuff running on someones device but im sure this will help more than just you and me.

It should work perfectly fine with PA. I use PACMan which is CM10+PA+AOKP together with no issues. PA isn't an issue.
[Android Software/Hacking General [Developers Only]] calisro:
FYI, new version is up (v12) minor update. You do not need to update unless you want to.

- Increased logging to sdcard

- termination of titanium before rerooting

- shell running in '-e' mode to abort if any commands 'fail' to further prevent a lockout.
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise ( GFE ) root workaround

I've been running CM10 + GFE for a few months just fine thanks to the scripts. Probably updating to the latest nightly & v12 today from one from a few weeks back & v10.
[Android Software/Hacking General [Developers Only]] IT Rider:
Running skyrocket nightlies 2/24 with different kernel and cpuspy. I also have v11 of the script. In the past is was working fine, but I have not tested since the 2/21 nightly. This time it failed validation and disabled my acct.

What files/logs do you need?

Edit: Here is a list of all my apps requiring root - AdAway, Titanium, ES Explorer (only when I turn it on), Incredicontrol
[Android Software/Hacking General [Developers Only]] calisro:
Let's make sure it isn't missing anything 1st. Download v12 (op). Then do this:

1) flash v12 and boot up.

2) run the disable good script.

3) run enable good script.

4) run disable good script again.

5) run the following commands in a connectbot shell after above:

su
find /system/app /data/app /system/bin /system/xbin > /sdcard/gfe.txt

Then give me the following logs:

/sdcard/gfe.txt

/sdcard/enable_good.......log

/sdcard/disable_good.......log

EDIT: Also make sure you turn OFF root mode entirely in es explorer and reboot after just to rule that out.
[Android Software/Hacking General [Developers Only]] IT Rider:
After your suggest post in the OP or first few pages, I can't remember about es explorer...I always do this :) Here are the requested files. I had my IT person who controls gfe reset my account (it was locked). Now when I try to run it (with all the items disabled), it just opens then closes very fast.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise ( GFE ) root workaround

I had given up on this and then your v12 script and insights provided a lot of information.

I'm currently able to do this for all the Roms. PA, Cyanogen, Stock Rooted variants etc. for Note2.

Can you please post these debug instructions in the op so that everyone will not as the same question over and over again like I did. :)

I also want to add one thing that was causing issues for me. Turn off automatic updates for super user from market.
[Android Software/Hacking General [Developers Only]] IT Rider:
Ok, I noticed a quick popup before my acct just disabled itself again, so I captured some logcat.

02-26 10:01:18.291: W/PackageManager(617): Permission group com.noshufou.android.su.permission-group.SUPERUSER from package com.noshufou.android.su ignored: original from com.noshufou.android.su

02-26 10:01:18.962: E/AndroidRuntime(6136): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
02-26 10:01:18.962: E/AndroidRuntime(6136): java.lang.IllegalArgumentException: Unknown package: eu.chainfire.supersu.nonag
02-26 10:01:18.962: E/AndroidRuntime(6136):	at android.os.Parcel.readException(Parcel.java:1429)
02-26 10:01:18.962: E/AndroidRuntime(6136):	at android.os.Parcel.readException(Parcel.java:1379)
02-26 10:01:18.962: E/AndroidRuntime(6136):	at android.content.pm.IPackageManager$Stub$Proxy.setApplicationEnabledSetting(IPackageManager.java:2635)
02-26 10:01:18.962: E/AndroidRuntime(6136):	at com.android.commands.pm.Pm.runSetEnabledSetting(Pm.java:1226)
02-26 10:01:18.962: E/AndroidRuntime(6136):	at com.android.commands.pm.Pm.run(Pm.java:124)
02-26 10:01:18.962: E/AndroidRuntime(6136):	at com.android.commands.pm.Pm.main(Pm.java:77)
02-26 10:01:18.962: E/AndroidRuntime(6136):	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
02-26 10:01:18.962: E/AndroidRuntime(6136):	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
02-26 10:01:18.962: E/AndroidRuntime(6136):	at dalvik.system.NativeStart.main(Native Method)

Almost looks like one of my root apps is not shutting down like you previously mentioned. Doh!
[Android Software/Hacking General [Developers Only]] calisro:
For the opening/closing fast:

If its closing very fast and not doing anything, i'd suspect (superuser) is denying su access to the connectbot or smmanager app or whatever you are using to run this. Check superuser app for any denies.

For the lockout, the scripts are doing its job. I can see the apk and su getting hidden and unhidden. I do not see any left over things it is not hiding. It looks clean. that is good. You may have gotten a lockout because of es explorer or titanium. If es explorer was run in root mode before launching good I have seen policy breaks as a result. I put that in the op. Same situation for titanium.

You may want to try running these again. After flashing a new rom, you should always run the 'enable root disable good' script before doing anything to reset things.

Let me know.
[Android Software/Hacking General [Developers Only]] IT Rider:
Thanks Calisro for the quick replies. I do appreciate all the help on this. I may have not been clear on my steps to make sure it is working :)

GFE was closing very fast. This happened after it started the services. On the 3rd try to open it, it locked me out again. I confirmed that ES Explorer and Titanium are setup the way they have worked in the past. I also configured autostarts as suggest per the OP. I am wondering if one of the other listed root apps I mentioned are causing it (e.g. AdAway, Incredicontrol).

Do you know of a way for me to capture what GFE is detecting?

Edit: Oh, to answer your question, yes, I tried it again and did not access any of the root apps. I reflashed the rom and v12 script...no kernel this time, ran the disable script, ran the enable script, installed/started the gfe application. After it started it force closed itself and locked me again.
[Android Software/Hacking General [Developers Only]] calisro:
Done.
[Android Software/Hacking General [Developers Only]] calisro:
There is no way to capture what GFE is detecting. I have done a large amount of analysis about what it detects and what it doesn't by trial and error and 30475204304 lockouts. :eek:

I doubt incredicontrol is causing issues as that is something that would just run on boot to set up the parameters. Its not persistent. I run adblock so that isn't it.

What version of script manager are you using? One from the op? or from the market? Also are you using the regular script or did you also flash the sparky su alternative in the op?

After you reflashed your rom, did you reboot before running the scripts?

I hate to have you keep trying things only to get locked out. I'm not entirely sure what its detecting. I run CM (all kinds of nightlies and different bases along with AOKP and others) which is what you flashed so I am 100% sure it isn't anything related to CM or the nightly.

This is what I would do if I were in your situation and wanted to debug.

1) I would uninstall script manager if it is any version other than what is in the op.

2) If you installed the sparky su alternative, reboot to recovery and reflash the v12. that will overwrite it.

3) I would uninstall titanium and es explorer temporarily just to make sure.

4) Clear data on the good app if its in locked out state.

5) Then i'd reboot and let the rom settle for a few minutes so any startup programs can run and do their thing and close (like adblock)

6) Then i'd run disable good script from within connectbot. Just open a connectbot session and type /system/xbin/disable*sh.

7) Then i'd run the enable good script and it will ask you for the pin and reauth to good. In connectbot /system/xbin/enable*sh

8) see if you get locked out. IF not, then try to disable it and reenable it again with connectbot.

9) if all is well then you can reintroduce titanium and es explorer (root mode disabled in es explorer) and verify all is well

10) then you can reintroduce script manager if you want from the op but I personally use connectbot (see op)
[Android Software/Hacking General [Developers Only]] IT Rider:
Ok, that is good to know. I have AdAway, not adblock...not sure if there would be a difference on how they run.

I am running Irssi ConnectBot. No, I did not flash the alt su, just your scripts.

Yes. I usually let it sit because it updates the dalvik and apps...then reboot to make sure it is a clean boot.

Sounds good. I'll report back in a few.
[Android Software/Hacking General [Developers Only]] calisro:
Are you running 10.1 CM? Were you running just CM 10 before instead of CM 10.1?

EDIT: I just upgraded to 10.1 from 10 and I found an issue. Im verifying now.
[Android Software/Hacking General [Developers Only]] IT Rider:
CM10.1 latest nightly.

I'm almost done testing with your suggested steps. I should have a post up shortly.

Edit: sorry, you asked 2 questions. I have been using your scripts since CM10. I had it successfully working on 10.1 since v9 of your script.

---------- Post added at 12:03 PM ---------- Previous post was at 11:56 AM ----------

Hmmm, ok. I do not use gfe often, so the last time I checked it was when I was in Mexico for work using the 10.1 nightlies 2/14-19.

---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------

Status:

N/A

N/A, but I did reflash v12

Done.

Done. Actually, uninstalled app (each time I was locked) and deleted SD folder. Deleting the SD folder was the one thing I did not do the last time I was locked out. It may have had bad settings. What do you think?

Done.

Done.

Done.

Ok, annoying. Works this time w/o a lockout.

Installed titanium, opened it up, then restarted the phone. I then waited. I did notice that incredicontrol had a popup on the main screen that said it was granted superuser rights, though, I had not started it this time. I then ran the disable script, and finally the enable gfe script.

GFE prompted for the pw, then showed a white screen and force closed itself. So before it locked me out, I ran the disable script, uninstalled incredicontrol/cpuspy, rebooted, waited, ran the disable script again, then enable script. This time it closed again but no lockout. So I wiped the gfe data, sent another pin (because it was not locked out), and reconfigured it. With the new pin it hung on "starting servies" as usual, then closed itself. Tried again and it forced closed. I left it as is because I don't a lockout.

N/A. I also use the connectbot.
[Android Software/Hacking General [Developers Only]] calisro:
Are you sure you dont have script manager installed? I saw the apk in your log...

/data/app/os.tools.scriptmanager-1.apk

I am not clear from your post as to what state you are in. Do you think incredcontrol is causing it? I doubt is titanium or cpuspy. I wont be es explorer as long as it is NOT in root mode and you hadn't used it before rebooting while it was in root mode.... I have cpuspy/es explorer, titanium all installed without lockouts.

Remember, this Good POS doesn't detect root apps but can detect 'open root sessions' via looking at the background processes. If incredcontrol is leaving something open it could be that but I am not sure. I can try to install it real quick and see what happens.

EDIT: My kernel doesn't support incredicontrol and my phone doesn't have any custom kernels that would so I cant test it.
[Android Software/Hacking General [Developers Only]] calisro:
New Version up. It actually backs out some changes I did to improve the speed of execution. It caused me some issues.
[Android Software/Hacking General [Developers Only]] IT Rider:
No worries. I have the script mgr you post in your OP installed, but I don't use it. I never actually uninstalled it since I started using 10.1 and it worked w/o any problems. No, I don't think incredicontrol is causing it since right now it is uinstalled and gfe is still force closing. I left es explorer uninstalled for now.

I'll try your new scripts and post back.

---------- Post added at 01:28 PM ---------- Previous post was at 12:54 PM ----------

Well, the darn gfe app keeps force closing with no notifications, so I think my acct might be locked. Unfortunately, the admins for that server are +7hrs so I cannot unlock it until tomorrow. I'll post back.

EDIT#2: Okay, my account was not locked on the most recent attempts. Let's chalk this one up to user error. I am so used to disabling gfe in the autostarts, that I actually disabled all the services before the program could finish its initial configuration. So the app would just close. I also had to uninstall incredicontrol since it was running a service in the background that triggered gfe.

So to report, the latest 2/26 10.1 nightly, with v13 of the script and some root apps uninstalled, gfe is working successfully.

Calisro, thank you again for your help and patience!
[Android Software/Hacking General [Developers Only]] knjaz1:
Hi Calisro

Could you please advise if these scripts will be working on SGT 2 7.0 (3100). I also interested to make GFE working on my device. I now have 4.1.2 version.

I tried to download v12, v11 and v10 and it's not installing on my device with message like parsing error.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise ( GFE ) root workaround

What's the error and what are you doing to install them?
[Android Software/Hacking General [Developers Only]] MZKS3:
Hi I am running JB 4.1.1 Tmobile S3 with root. I only use my root to tether 4g rarely on occasion and have stock touch wiz. I want to be able to use GFE. Can you please advise me. I am a noob at most of this stuff and have trouble with some of the acronyms on this blog so please spell out acronyms. I emailed Calisro earlier. Thanks
[Android Software/Hacking General [Developers Only]] knjaz1:
I download .ZIP from 1st page of the tread and rename it to .APK which is general way to install.

When I run it it shows message "There is a problem parsing the package"

If I try to install it through recovery console it run the package but then show message "signature verification failed"

(I'm IT person but beginner in Android)
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

its not an apk so renaming it won't install it. It sounds like you don't have a custom recovery installed which would be required to flash zips in a custom recovery. You could still use the scripts but you'd have to manually copy them to /system/xbin with root.

This is really beyond the scope of this thread. Are you proficient in linux?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Do you have a custom recovery or just a stock rooted rom without recovery?
[Android Software/Hacking General [Developers Only]] segelfreund:
Sorry,

but do it works with the Nexus 4 and Jelly Bean 4.2.2?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

It isn't device specific.

You need root, a recovery to install it (although its possible to do it manually) and you need a very basic installation of busybox. Other than that its just q script.
[Android Software/Hacking General [Developers Only]] segelfreund:
AW: Good for Enterprise (GFE) [02-24-2014] root workaround

Thanks

The device have root. So i needed the script.

I will tested.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] segelfreund:
AW: Good for Enterprise (GFE) [02-24-2014] root workaround

Ok the unabled good an enabled root doesent work for me.

Anyone an Idee?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] calisro:
review the debug section in the op and put the logs here.
[Android Software/Hacking General [Developers Only]] segelfreund:
After a reboot it works.

I don´t know why
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Well good thing then. Thanks for confirming that it works :)
[Android Software/Hacking General [Developers Only]] MZKS3:
I have a stock rom on my phone. i dont know much about recovery?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

you need a custom recovery to flash the zip. alternatively you can manually copy the files in the zip to /system/xbin manually and set permissions but frankly that's beyond the scope of this thread.
[Android Software/Hacking General [Developers Only]] segelfreund:
I don´t know.

But the good app say "Taht the device is not confirm the good policy".

Anyone an idea?
[Android Software/Hacking General [Developers Only]] knjaz1:
Calirso

You were right about custom recovery. I completely forgot that I've lost it when reload firmware. Now I restored it with RomManager and installed your scripts.

So I able to run it.

I run enable_good_disable_root and it seams working Ok. But Good anyway see rooted device even after device restart.

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

Take a look at the op for debugging logs. Post them.
[Android Software/Hacking General [Developers Only]] knjaz1:
Just downloaded new version (13) you posted. And it's starts working. Thanks a lot.

Advise where the logs are sitting. Will post it anyway to help you make it better.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

If its working, no need to post.. they are in /sdcard/*log