Root Good for Enterprise

[i love grits]

actually the problem was that while I had removed the superuser.apk from the filesystem it still showed in the installed applications list in settings, uninstalld from there, which obviously failed, and good started OK.

What ROM are you running?

 

[santoro]

actually the problem was that while I had removed the superuser.apk from the filesystem it still showed in the installed applications list in settings, uninstalld from there, which obviously failed, and good started OK.

I had the same problem with the latest release, this did the trick for me too. Thanks!

 

[marcspez]

I was able to rename or remove I cant remember the SU and superuser app once before so that my Good application would work.

I have re rooted my phone to update my OS and now i can not get the terminal to remove or rename the files. I get the follow error.

rm: can't remove 'su': Read-only file system

does anyone have any idea how I can remove the files or why I am not able to this time. Thanks for your help

 

[Eryl Flynn]

Such a shame, my company decided to let non corporate blackberries to active sync, but chose GFE as well as root detection. Oh well, guess I won't be on time to all those important meetings they want me to help with.

 

[cbb77]

I had the same problem with the latest release, this did the trick for me too. Thanks!

Is this still working for you? Also are you able to go back to switch back to root whenever you need to? I have just got my phone and would like to not give up root due to some apps that require it; Titanium backup, Autoproxy, etc. It would be nice to be able to switch root on an off as needed. If you remove/ rename superuser and su, as well as remove the entry from the app list, is there a way to rename files later or once done are you locked out and need to fully root again via whatever original method was chosen?

 

[adoobiez]

I found a workaround which is a bit painful AND TIME-SENSITIVE but it works.

Here are VERY IMPORTANT assumptions I'm gunna make and I hope they apply to you:

1) your phone is NOT rooted.
2) you currently don't have Good installed, or you have the capability to un-install THEN re-install it (I believe companies' IT depts give you a PIN that is valid for 14 - 21 days so within that period you can un-install and re-install Good as many times as you want - if you fall within this time period, continue reading cause you're in luck!)
3) you already know pretty much everything that you want to achieve after rooting your phone, and not just 'exploring' it. Because at the end of this exercise (with Good installed) you will have an un-rooted phone.

If you're still reading, here are the steps:

0) confirm that you can still re-install Good, or at least talk to someone from IT to confirm that he/she can re-send you a PIN to re-install.
1) un-install Good (if it's installed already. If not, then you can skip both steps 0 and 1)
2) download and install VISIONARY TEMPROOTER! It's no longer on the Market as of today so just do a google search to find the creator's site and download from there (they're kind enough to still provide it online)
3) once TEMPROOTER is installed, open it, then do a TEMPROOT (just the temproot, DONT do a permroot). What this does is root your phone temporarily, which will return your phone to un-rooted status after you re-boot.
4) this is the time-sensitive part! Install/run/tweak/do everything you need to do to your phone with root access and get it over with (within the time period IT has given you to install Good). I know this is crazy but it's a compromise. Example of what I did for my phone after I did a temproot - deleted some useless apps, updated my boot splash screen and animation, enabled waking up of my screen by pressing the menu button, FULL bac7kup using ClockWorkMod Recovery app, and then I was done (not that I have a choice since I got no time left).
5) after doing everything you need to do with root access, re-boot your phone to bring it back to un-rooted state. Note that Steps 3 - 5 may have to be repeated many times if the things you're doing with your temp-rooted phone require multiple re-boots.
6) After you're back to un-rooted state, go to Manage Applications then delete these 2 apps - SUPERUSER PERMISSIONS, and VISIONARY TEMPROOTER (you can leave this one technically but you won't be using it anyways so there's no point leaving it on)
7) And finally, INSTALL GOOD, ACTIVATE, and ENJOY viewing corporate email and being a corporate slave once again . Do not re-root after installing Good as it will detect and wipe itself off your phone. It is the suck that way .

As far as I know, this method will work regardless of your ROM version and device (as long as it's an Android device of course). That is all. Hope this helped some of you work-around this issue.

 

[fauconjeff]

I found a workaround which is a bit painful AND TIME-SENSITIVE but it works.

Here are VERY IMPORTANT assumptions I'm gunna make and I hope they apply to you:

1) your phone is NOT rooted.
2) you currently don't have Good installed, or you have the capability to un-install THEN re-install it (I believe companies' IT depts give you a PIN that is valid for 14 - 21 days so within that period you can un-install and re-install Good as many times as you want - if you fall within this time period, continue reading cause you're in luck!)
3) you already know pretty much everything that you want to achieve after rooting your phone, and not just 'exploring' it. Because at the end of this exercise (with Good installed) you will have an un-rooted phone.

If you're still reading, here are the steps:

0) confirm that you can still re-install Good, or at least talk to someone from IT to confirm that he/she can re-send you a PIN to re-install.
1) un-install Good (if it's installed already. If not, then you can skip both steps 0 and 1)
2) download and install VISIONARY TEMPROOTER! It's no longer on the Market as of today so just do a google search to find the creator's site and download from there (they're kind enough to still provide it online)
3) once TEMPROOTER is installed, open it, then do a TEMPROOT (just the temproot, DONT do a permroot). What this does is root your phone temporarily, which will return your phone to un-rooted status after you re-boot.
4) this is the time-sensitive part! Install/run/tweak/do everything you need to do to your phone with root access and get it over with (within the time period IT has given you to install Good). I know this is crazy but it's a compromise. Example of what I did for my phone after I did a temproot - deleted some useless apps, updated my boot splash screen and animation, enabled waking up of my screen by pressing the menu button, FULL bac7kup using ClockWorkMod Recovery app, and then I was done (not that I have a choice since I got no time left).
5) after doing everything you need to do with root access, re-boot your phone to bring it back to un-rooted state. Note that Steps 3 - 5 may have to be repeated many times if the things you're doing with your temp-rooted phone require multiple re-boots.
6) After you're back to un-rooted state, go to Manage Applications then delete these 2 apps - SUPERUSER PERMISSIONS, and VISIONARY TEMPROOTER (you can leave this one technically but you won't be using it anyways so there's no point leaving it on)
7) And finally, INSTALL GOOD, ACTIVATE, and ENJOY viewing corporate email and being a corporate slave once again . Do not re-root after installing Good as it will detect and wipe itself off your phone. It is the suck that way .

As far as I know, this method will work regardless of your ROM version and device (as long as it's an Android device of course). That is all. Hope this helped some of you work-around this issue.

Hi. I used to have good for enterprise working with Coolexe Aces v2 ROM working well for months. Then i did an upgrade of GFE and it detected that i was rooted, and was disabled. Now i'm using Cyanogen7 nightly ROM. I just want to know if i can install Cyanogen7 ROM, unroot the phone while keeping CM7, and then install GFE.

Or do i absolutly have to run a official RUU ROM to use with gfe ?

 

[VoidedSaint]

what is GFE?


and you cannot unroot while having cm7 because the new cm7 roots your phone as you install it.


you cannot get other custom roms on the DX because it is not built for it, you have to take into consideration the encrypted bootloader that we cannot bypass, however custom roms are coming to our devices, just know all custom roms are not built to go between devices at will.

 

[paithara]

Hey guys, I too am looking to use GFE, on my N1 with MIUI. Is the method from one of the above posts, of renaming superuser.apk and denying permission to Good when prompted, still work? @swany11, are you still able to use this workaround? Doesn't good check for busybox, because I remember reading somewhere that it does?

If no, how do I remove root from MIUI and begin to use GFE? What should I do when I need root again, say, to update or backup? Please advise. This seems to be the only thread anywhere on the internet that discusses unrooting in this context for GFE while everywhere else it's just people wanting to restore to stock.

 

[Eryl Flynn]

Hey guys, I too am looking to use GFE, on my N1 with MIUI. Is the method from one of the above posts, of renaming superuser.apk and denying permission to Good when prompted, still work? @swany11, are you still able to use this workaround? Doesn't good check for busybox, because I remember reading somewhere that it does?

If no, how do I remove root from MIUI and begin to use GFE? What should I do when I need root again, say, to update or backup? Please advise. This seems to be the only thread anywhere on the internet that discusses unrooting in this context for GFE while everywhere else it's just people wanting to restore to stock.

None that I am aware of, it doesn't "ask" for permissions. Doesn't need to, it looks for certain files su is one of them. When it finds one of the known files for rooting it refuses to start.

I don't sweat it, this would have been beneficial to the company not me. They do not get to tell me if I can have administrator rights on my devices.

 

[paithara]

None that I am aware of, it doesn't "ask" for permissions. Doesn't need to, it looks for certain files su is one of them. When it finds one of the known files for rooting it refuses to start.

I don't sweat it, this would have been beneficial to the company not me. They do not get to tell me if I can have administrator rights on my devices.

I fought the need for as long as I could too. But, of late, I've found myself needing mail on-the-go a few too many times. Going from what swany11 had said, the way it checks for the su binary is by running a su command at which point superuser should display a prompt for permission (if you set it up that way of course). For the other files, superuser and busybox presumably, it simply checks for their existence. Which is why swany11's method seemed simple and promising.

Would you happen to know what happens when you pluck out su and superuser from a custom ROM? Would it break functionality of all the additional features of the ROM? And when I do need to backup, how do I get root back?

 

[dmk1]

Has anyone had any luck running GFE on a custom ROM (such as cm7) lately? Mine was working for a few days, but now detects root even if I rename su and Superuser.ask. Any other steps that have worked?

 

[jmsnyc]

Is it possible to freeze or disable GFE without root?