Has anyone had a problem with the intial setup for Good for Enterprise on custom Android ROMs? I installed it (using an issued PIN) on stock eclair on my Captivate and it worked fine. I then rooted, backed it up via TIBU and restored on Froyo and it still worked fine. The same process worked recently on Gingerbread. However, I have tried multiple custom Froyo ROMs and 1 GB recently and if I try the initial setup (with a new PIN) on anything other than stock eclair (even rooted), it will stop at "retrieving policies" and never complete. I then have to ask for a new PIN from my IT support and revert to eclair and finish the setup, backup, and restore on the later custom ROMs. Has anyone seen this and have any idea why? My IT support has no idea. I am not in a policy checking for root access and it does continue to work with root.
EDIT: I wonder if it is that the device name used in build properties is referenced during that step and it fails due to an unknown device...
Also, I have found that after I have it working after a certain PIN used, if I ever restore to an ealier point (due to a theme gone wrong, etc) then it stops syncing even if the restore point is AFTER I had it working with that PIN. It seems like the local software either is exchanging a dynamic password with the server or there is a message index, etc that has to be in sync. Any thoughts?
When in the Good setup screen, go to Menu>Device Info. Does the Phone number appear? I've been using CM7 just fine with Good but after the last few nightlies, Good no longer works. The phone number doesn't appear in the device info. Good thinks there is no phone network present.
I am a heavy Good user, unfortunately also addicted to changing ROMs on a frequent basis. I have never had an issue with Good running on any ROM, just on restoring from TiBu. I can flash new kernels, themes, etc, and Good works just fine. If I re-flash the same ROM, it resides and works just fine. It is only when flashing a new ROM I have problems. Good appears to restore OK, but won't pull new emails to the inbox. I ave to get a new PIN and re-install.
Same here.. i am addicted to flashing as well.
I tried Titanium backup to backup and restore to new ROM, but somehow Good just keep crashing after i put in my password.
I am sure I can ask for new pin, reinstall and what not.. but how often can we ask IT people (for my company at least) for new pins, until one day they may say, bugger off you ROM addict!
Finally figured it out, I think. The trick is to NOT have Good running in persistent mode when you do the backup with TiBu. IOW, reboot and backup with TiBu before you start Good and log in. I did that the last couple of new ROMs and it restored and worked just fine.
Sent from my SGH-I897 using XDA App
GOOD for Enterprise on Imito AM801 Tablet
I am also getting the Phone network is off. This is a tablet and does not have any phone piece or sim card installed. No hardware is even inside the tablet. Has anyone ran accross this issue on tablets?
This works for me.
http://forum.xda-developers.com/showthread.php?p=35263313#post35263313
Good with custom roms
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Anteus20 said:
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Click to expand...
Click to collapse
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
joshic75 said:
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
Click to expand...
Click to collapse
You quoted a 1 year old post, might be hard to get a reply. Also this is for the S1, while the app (GFE) might be the same, the ROMs definitely aren't.
That being said, chances are that the app was updated to prevent that workaround. You could flash a TW based ROM and test it though.
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
joshic75 said:
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
Click to expand...
Click to collapse
There is an xposed module for this.
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
joshic75 said:
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
Click to expand...
Click to collapse
I'm a bit confused here, Custom ROMs are pre-rooted. Therefor, if you're not on TW, you're rooted.
And yes, Xposed does require root. As for Wanam, I duno if it works on AOSP but best way to know is you try
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
joshic75 said:
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
Click to expand...
Click to collapse
I have never personally tried it without root but you can test that fairly easily. I expect it would depend on the module you're using, some require more permissions than others.
I tried it out but it didn't work.
I have to go back to stock ROM
Hi there,
A week ago I handed over my Nexus One to a relative so he could install gingerbread for me. He couldn't install it, and now I have an unlocked, semi-working phone (yeah, I'm not happy). I'll list the details below and hopefully someone can point me in the right direction of how to fix things myself.
- Recovery mode won't boot. The screen freezes on the multi-coloured cross.
- Wifi won't work. I get 'Error' everytime I try and activate it.
The build number is FRG83D, android v 2.2.1
Theres an applicaiton installed called 'superuser' with a pirate android icon
I've wiped everything several times, still doesn't work, and the superuser app is still there.
and PS, I'm using a mac.
I'm told theres some problem with the permissions and updates can't be installed. Any help would be greatly appreciated. Even just a hard reset to reinstall the base operating system would be great. Just want a working phone again! cheers
Do you have root access (open a terminal emulator app and type "su". If the $ prompt changes to #, then you have root access)?
What recovery do you use? AmonRa or Clockwork?
Your best option (if you can get into the bootloader), would be to follow the unroot/restore guide in the wiki.
If you have root access, you could install ROM Manager, flash a recovery, and then use that to do whatever (probably install a fresh ROM).
Hello happy new year, i see Cyanogenmod 11 comes with a superuser tab so i assume it's rooted, but root checker says my device isn't rooted.
I tried installing it anyways and rebooted the phone, no errors. But after i rebooted i saw a forum post saying i could get my phone bricked if i run xposed on an unrooted phone.
So i unistalled it before running the app again.
What should i do? Can i just install xposed with CM 11 as it comes or i need to do something else first?.
I've used eRoot with GB, ICS, JB with no issues but it doesn't work with Kitkat, so i'm not sure if i should just install it or what.
I really want some modules but i don't wanna break the phone :c
Installing Xposed on non rooted phone can't brick your device simply because root operations can't be done.
Xposed needs root access for installation process.
Madbezier said:
Hello happy new year, i see Cyanogenmod 11 comes with a superuser tab so i assume it's rooted, but root checker says my device isn't rooted.
I tried installing it anyways and rebooted the phone, no errors. But after i rebooted i saw a forum post saying i could get my phone bricked if i run xposed on an unrooted phone.
So i unistalled it before running the app again.
What should i do? Can i just install xposed with CM 11 as it comes or i need to do something else first?.
I've used eRoot with GB, ICS, JB with no issues but it doesn't work with Kitkat, so i'm not sure if i should just install it or what.
I really want some modules but i don't wanna break the phone :c
Click to expand...
Click to collapse
Go into developer options and make sure root access is set to apps, or apps and adb.
Common sense isn't all that common
Download set up first and then run the file after complete it.
Hello!
I'm rooting noob.
I've got a big problem with my phone. I have rooted my device some time ago, now i want to go back to stock. When i choose supersu option to fully unroot nothing hapend. After reboot, supersu is still there. I tried to flash zip with newest version of supersu-nothing. I tried to remove supersu manually it doesnt help either. Supersu seems to miss some of the libaries but when i try to instal it via twrp it shows no md5 file found error. Is there any easy way to return to stock? I mean something like clear all phone memory and just flash stock rom? Getting to fully operating root its also fine.
Go easy on me, im learning hard way. English is not my native language so sorry for all the mistakes i made.
Hi!
I previously had rooted my S7 Edge with Super SU v2.79 years ago but now I want to switch to Magisk because I need to hide root from certain apps. Magisk fails to install saying:
! Boot image patched by unsupported programs
! Please restore to stock boot image.
Click to expand...
Click to collapse
From here I read I can try unSU. But in my case it did not work. How exactly can I fix this now? As I understand I need to reflash some stock images? But what exactly is the minimum requirement? Just boot.img? Or system? Also if I don't want to loose my apps, data, config, can I flash them without loosing them? Or if not is it possible to hide root while still using SuperSU since I really don't want to lose my data/apps/config.
You get the info to restore the stock boot image, which is just the kernel image. As you are rooted right now, use a backup tool like Swift Backup (full version is paid) or Neo backup (FOSS) to backup all app data and apps and personal data in case something goes wrong. Backup that stuff to your PC of course, saving all data that was created by the backup app and your other stuff. Then flash stock kernel, test if all is good and stick to Magisk stable plus needed modules.
Next time please provide all system data like used (custom?) ROM and Android version. If you use a custom ROM you need to revert to the unrooted custom ROM kernel of course.
Thank you for your response!
I am not rooted currently as I uninstalled Super SU but I think I can install it back if needed. Will flashing stock kernel always cause app data to be lost? Or is there chance that it does not get touched? As for ROM I use stock android 7 rom. I am not sure where and if can I still find it.
I don't really trust backup because because previous attempts have ended up with boot loops and broken apps. If there is chance that that app data stays intact without backup then I might try it but if the process factory resets everything and then relies on restoring backup as one part of the process then for now I would try to come up with some other solution.
Also will it cause all the stock bloatware to come back or is the kernel separate from apps?
sysctl said:
Thank you for your response!
I am not rooted currently as I uninstalled Super SU but I think I can install it back if needed. Will flashing stock kernel always cause app data to be lost? Or is there chance that it does not get touched? As for ROM I use stock android 7 rom. I am not sure where and if can I still find it.
I don't really trust backup because because previous attempts have ended up with boot loops and broken apps. If there is chance that that app data stays intact without backup then I might try it but if the process factory resets everything and then relies on restoring backup as one part of the process then for now I would try to come up with some other solution.
Also will it cause all the stock bloatware to come back or is the kernel separate from apps?
Click to expand...
Click to collapse
to back up use smart switch in pc, to install magisk is recommended to flash stock firmware first and instal magisk to avoid issues like bootloops