yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] gveloce:
Hm seems serious..... I will try the reboot but I am not sure if during reboot CM10 will mount again /system as RW. How can I check this?

Anyone else that has experience with other Native SD installations (non Nexus-Cm10) and does not have the same error (or fixed it somehow..)?

MANY THANKS

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

Just manually upgraded the new version of Good that appeared in the Market today. All good (sic) and still working with your script it would seem.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

reboot will make it rw again. but tuis may mean that you'll need to reboot each time... unless you can figure out what process is causing it to not remount. I wonder if nativesd needs a slightly different mount command.
[Android Software/Hacking General [Developers Only]] auslander1138:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Cheers man! I haven't yet updated on my phablet but I'll report back if I have any issues post update.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Since you have a setup that I can't test with, you should ask in your device forum how you would remount your particular system partition setup. What may be causing the issue is the way nativesd is setup. I am wondering if we need either the --bind and/or the -type options on the mount command.

If you can figure that out, you can customize the script for your device easily.
[Android Software/Hacking General [Developers Only]] gveloce:
You r right it is mounted RW again...

I found this btw

http://oletange.blogspot.de/2012/04/umount-device-is-busy-why.html

but dont know how it helps. I keep trying.....

thanks a lot

GV
[Android Software/Hacking General [Developers Only]] gveloce:
I am progressing with small steps

On my NativeSD installation /system is mounted on the same dev/block/mmcblk0p2 device as /NativeSD and /data.

Not a unix expert but seems that something is keeping the fs busy from the other two mounted .....??

Any help appreciated. Hope this will help others that happen to be in my case (hope more than one=me!)

GV
[Android Software/Hacking General [Developers Only]] calisro:
Paste the output of

su
mount
df
[Android Software/Hacking General [Developers Only]] gveloce:
Su: no output. Works

mount output (notice the common device for system data and NativeSD)

rootfs / rootfs rw 0 0

tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/block/mmcblk0p2 /NativeSD ext4 rw,noatime,nodiratime,barrier=0,stripe=64,data=ordered 0 0

/dev/block/mmcblk0p2 /system ext4 rw,noatime,nodiratime,barrier=0,stripe=64,data=ordered 0 0

/dev/block/mmcblk0p2 /data ext4 rw,noatime,nodiratime,barrier=0,stripe=64,data=ordered 0 0

/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

df (seems enough...)

Filesystem Size Used Free Blksize

/dev 205.2M 48K 205.2M 4096

/mnt/asec 205.2M 0K 205.2M 4096

/mnt/obb 205.2M 0K 205.2M 4096

/NativeSD 849.3M 620.3M 229M 4096

/system 849.3M 620.3M 229M 4096

/data 849.3M 620.3M 229M 4096

/storage/sdcard0 1009.9M 343.9M 666M 4096

/mnt/secure/asec 1009.9M 343.9M 666M 4096

thanks for your support efforts!

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

Still working fine after the GFE app update a couple days ago. Even after updating to the 3/6 CM 10.1 nightly.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

After a reboot is /system rw or ro? If system is always rw, then you won't get GOOD to run in this environment. GOOD detects the system mount as rw.

If when using nativesd the system mount is always rw that will be a problem hence why I ask if it changes to ro after reboot.
[Android Software/Hacking General [Developers Only]] gveloce:
Hm. What if I change the FSTAB to have /system mounted as RO? Would this work??

GV
[Android Software/Hacking General [Developers Only]] calisro:
I'm not sure if that will break your nativesd implementation. If it does not, it may work. This likely won't stop the error you are seeing when trying to make the /system RO again but this is the procedure you can likely follow:

Whenever you want to Enable good:

1. Run the enable* script.

2. The script will error at the end when making /system RO.

3. Reboot to correct the mount point.

4. Launch Good.

Whenever you want to Enable root:

1. Run the disable* script.

2. The script will error at the end when making /system RO but that is irrelevant at the moment.

3. You are rooted.
[Android Software/Hacking General [Developers Only]] calisro:
You can get creative IF you can set /system to RO in /etc/fstab 1st and if you continue to get the 'resource or device busy' when changing it from RO->RW->RO...

1. Change fstab.

2. Make a new mount point for accessing system

su
mkdir /data/gfesystem
mount --bind -o rw,noatime,barrier=1,data=ordered -t ext4 /system /data/gfesystem

3. Change my scripts to access /data/gfesystem instead of /system and simply remove the mount commands from the script. You can then make your modifications using /data/gfesystem instead of /system.

There is always a way. Depends on how much energy you want to spend on it. :cool:

The best approach would be to figure out what is blocking the remounts and terminate it but this is under the assumption that you can even set that filesystem to RO in fstab and have it not break your nativesd.
[Android Software/Hacking General [Developers Only]] gveloce:
Thanks a lot mate!

I ll try and report back!

BTW I hate GFE methods but is the only way not to carry 2 phones (mine and a Blackberry!)

GV
[Android Software/Hacking General [Developers Only]] Fallon:
[*]Just encountered some weirdness:

Went to scan a QC code & could only get a black screen with no video

Ended opening up the camera app & got an error message saying camera was disabled by security policy, even after a couple reboots

Ended up disabling GFE

When I re-enabled GFE I complained the security policy required a PIN (I already had one set)

I was then bounced me over to the PIN lockscreen configuration, which prompted me for my PIN (only once as I already had one set

Camera now works

No real long term problems, but it was weird. Not sure if it was related to our enable/disable hacks, an artifact of GFE being upgraded, or what.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

yea, I had that pin thing happen after the upgrade. I'm guessing is GOOD weirdness is all.
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Just had it happen again & GFE wouldn't let me in complaining about the lock screen even when I changed to password from pin. GFE was happy again going back to my pin after a reboot. Odd.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Do you have GFE set as a device administrator? settings - security - device administrator...

Mines been working fine on both my devices after that initial upgrade quirkyness.
[Android Software/Hacking General [Developers Only]] Fallon:
Yes GFE is an administrator. Complains GFE might lock if I disable it's admin access, might try that tonight & see if it borks GFE.

And it looks like it ate my camera again. Going to do a TiBu backup then wipe stuff & update to the latest nightly this weekend & re-install things. See if that helps, it's been a little while since I've done that anyways.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Interesting. mine isn't. I removed it a while back. ymmv.
[Android Software/Hacking General [Developers Only]] IT Rider:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

With the new su in the latest nightlies, I now found that when I disable root, the su app does not return to the application list. Thoughts?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

latest nightlies of what? and what superuser app are you using?
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

CM10.1, think they just changed the version of su in the past week or 2. No su related issues or policy violations though. What problems were you having with the new SManager? Latest one worked fine for me tonight on several enables & disables.

Screwing around with things now. Seems to always wig out about the pin after re-enabling GFE. Reboot fixes things though.

I'm wondering if my GFE admin didn't mess up and disable the camera by policy. Camera is disabled whenever GFE is enabled.

GFE refuses to work & just prompts you with the admin permissions screen when you uncheck the box for GFE under security > administrators. Works fine once you re-enabling its admin access no need for a new code or anything.
[Android Software/Hacking General [Developers Only]] IT Rider:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

In the commits the super user was updated. Cm10.1

Just the su that comes with the rom when flashed.

Are you using the one from your OP or do you have a different preference for the su app?
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

I use the one with cm10.1... Its the new superuser integrated with cm10.1....

If you have the same, it no longer has an app and instead is integrated in the rom settings menu.
[Android Software/Hacking General [Developers Only]] IT Rider:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Found it, thanks. Thought I was crazy for a minute there.
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

In the new nightly of aosp ROMs, developers are adding a new super user implementation. This is a new rewrite of super user application by koush (the cwm recovery developer). Since his superuser is free and open source, cm10.1 latest nightly has already included it and merged it in its code.

Its also in latest paranoid android nightly.

I'm also scared of upgrading my ROM due to this reason because I don't wanna loose or break my good.
[Android Software/Hacking General [Developers Only]] IT Rider:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

It didn't break the good on my phone. The scripts here work perfect! Just a note, if you turn off auto starting off the gfe app, leave the admin auto start on. That it's what was causing my earlier problems (See my posts a few pages back). It was all user error on my part.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

I do not see that issue but it may be because different companies enable different policy enforcement. ill add this note to the op so others won't disable that autostart of admin.
[Android Software/Hacking General [Developers Only]] IT Rider:
The problem was not that it broke the root policy from gfe, but that it would not "activate" on my phone, causing the white screen delay. I had to keep putting in new keys and wiping the gfe data each time it configured itself. I have noticed that every time I flash a new rom, it "activates" itself. If I have the admin service disabled, it will not work, thus, my user error problem :confused:
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Fallon, you may want to try to disable the device admin in autostarts for GOOD and see if that helps you. that will prevent good from registering on start as a device admin. Mind works fine like that. IT Rider said it caused him problems... Worth a try...
[Android Software/Hacking General [Developers Only]] Fallon:
Just got off the phone with our Good admin... Apparently the camera stuff is a new feature in the new version & it defaults to restricting. They removed the camera restrictions & things work fine now.

If it is a default as they claim, it might bite some other users.
[Android Software/Hacking General [Developers Only]] RichMD:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

I had no idea this thread existed but I have wanted this for months. I was looking to get dual-boot working - one ROM with superuser, etc removed to install GFE and the other (personal) to be able to flash and customize whatever I want. I will definitely try this on the weekend. Thanks for the thread and work so far... :)
[Android Software/Hacking General [Developers Only]] ceo.mtcl:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Trust me' you're gonna love it!
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

New GFE out. Mentions some camera fixes (similar/same issue affected me on the previous version until my GFE admins updated the camera policy). No compliance issues here yet, haven't enabled root recently though.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

working fine for me on new version as well. I've rerooted/unrooted quite a bit.
[Android Software/Hacking General [Developers Only]] f@milym@n:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Thanks so much for putting this together. This thread was a godsend for me. I'm running stock rooted on SG3 from Vzw. It worked perfectly. So now that I have this working... I want to load a new ROM. I'm looking at CleanROM 6 R2. Reading through this thread, here's my thoughts on the steps needed:

- run the disable good script

- backup good data with TitanumBackup (assuming I need pro for this?)

- backup my other stuff

- install the ROM

- flash the script

- restore good data

- use "autostarts app" to turn off all autostarting flags for Good app

- reboot

- run the enable good script

Am I missing anything? I'd prefer to not have to request a new key as it's a fairly painful process here. Is there any way I could 'bake in' the good app and data right into the ROM? (Maybe that's a question for the CleanROM thread...)

Any help is greatly appreicated. I know enough to be dangerous... :fingers-crossed:
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

looks right to me.
[Android Software/Hacking General [Developers Only]] Noname-2013:
scripts on Lenovo P770

Hi Calisro

First of all, thanks a bunch for all your effort. Secondly, I would very much like to get this thing working on my Lenovo P770 also.

The unit has a modded Chinese ROM from etotalk.com (I bought it that way)

Name: P770-S121-V4-MOD-by-DEAN@etotalk.com

OS: Android 4.1.1

Etotalk-ROM includes loads of stuff but I guess these are the essential tools of interest here

- Etotalk tools (More or less the same as the Tools from “Mobile uncle”)

- Root Explorer 2.19 (Mounted as r/o)

- SuperSU Pro (I have updated it to the last version)

- Experia Launcher Home 0.9.1

- Nova Launcher 1.3 Beta 5

Done steps:

1. Flashed the gfe_workaround_setup zip from OP. v13 via the built in CWM-based recovery tool v6.0.1.1 from Mobile uncle tools

2. Installed SManager ads2.5.3.1_test

and

Irssi ConnectBot 1.7.1-irssi

3. Setup the scripts in SManager (scriptwith widgets.

4. Installed autostart 1.7.5

5. Installed GFE 2.1.1.251

6. Disabled auto start of good

7. Reboot (not 100% sure if I did it but I think I did)

8. Ran enable good disable root script via Widget from SManager. Didn’t work with the following message:

Command:

'/system/xbin/enable_good_disable_root.sh'

-------------

Out:

u0_a108@android:/ $ exec /system/bin/sh -e '/system/xbin/enable_good_disable_root.sh'

/system/xbin/enable_good_disable_root.sh[6]: basename: not found

8. Ran disable good enable root script via Widget from SManager.. Didn’t work with the following message:

Command:

'/system/xbin/disable_good_enable_root.sh'

-------------

Out:

u0_a108@android:/ $ exec /system/bin/sh -e '/system/xbin/disable_good_enable_root.sh'

/system/xbin/disable_good_enable_root.sh[6]: basename: not found

9. Tried to run the steps in your debugging part but do not find the logs you are mentioning.

I did find the gfe.txt in (/storage/sdcard0) but the file is empty when i try to read it through root explorer.

I haven’t opened GFE since I installed it as the enable_good script didn’t work.

Now I’m a bit confused and I don’t know how to proceed. If you have any ideas please tell me.

Note: I am really a novice on Android

I noticed that in the /system/xbin not only:

disable_good_enable_root.sh

enable_good_disable_root.sh

but also also two other files have appeared

r_disable_good_enable_root.sh

r_enable_good_disable_root.sh

is this right?

(I hope i didnt forget some important information)

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

Looks like you are missing some busybox commands. "basename" is part if shell/busybox.

I know zero about your rom but you should be able to do a basic busybox install from the many installers in the play market.
[Android Software/Hacking General [Developers Only]] Fallon:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Finally used the script, still fine with the latest GFE.

Uninstalled all versions of SManager then just the latest (paid) version. It has been working fine as well. The SManager incompatibility seems to be resolved.
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

Thx. Ill test it out and update the op.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Busybox was missing

Hi,

thanks for you reply. I am aware of the fact that the ROM is very special. First of all; does it make sense for me to try this out? Is there a reasonable chance that I (with some support from you) will get this to work?

Secondly: You were right:

1. I installed the BusyBox Free 9.2 (Stericson)

2. Ran the disable_good script

3. Ran the enable_good script (However, I currently did not have a functionable key for Good so i tried my old one which did not work so had to skip that step and closed the setup of good)

4. Ran the disable_good script

Log files are attached:

enable_good_disable_root.sh.log

disable_good_enable_root.sh.log

gfe.txt was empty

I guess i must fetch a new key and let GFE install properly to get the install procedure results for you to be able to make something out of it right?

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

It isn't rom specific and works on aosp which is likely what your rom is closest to. The logs look fine. If your GFE was activated it would likely work okay.
[Android Software/Hacking General [Developers Only]] Noname-2013:
Status.. negative

Hi,

just tried it out but got a blocked.

Please have a look at the log files and check if you can make something out of it.

(all three in there)

Thanks a bunch in advance
[Android Software/Hacking General [Developers Only]] calisro:
The script looks to be correctly rooting/unrooting.

What apps are you running that need superuser permission? I am wondering if one once hanging out there actively holding superuser permission when Good was activating.

Did you have any other connectbot or script manager sessions open that had su already in the terminal?

Were you connect via ADB?

Try uninstalling script manager and doing the following:

Run in connectbot: /system/xbin/disable*

Reboot

Run in connectbot: /system/xbin/disable*

Run in connectbot: /system/xbin/enable*

Run in connectbot: /system/xbin/disable*

Activate Good (you can likely use the same PIN)

See if that activates and works. I do not see anything that GOOD would barf over.

EDIT: You mentioned that you disabled autostart for ALL GOOD stuff. I do that too but there was someone I remember posted that they had trouble if they disabled 'device admin'. Try enabling that.l
[Android Software/Hacking General [Developers Only]] Noname-2013:
update..

Hi,

First of all: thanks for your reply. Here are the requested infos:

Concerning apps with superuser access need. You can see the apps listed in SuperSU in the attached pic. All of them have "Access:Grant" except for Autostarts which is on Prompt. (Or do I have to check it somewhere else also?`)

Concerning other open connectbot or script manager sessions. As far as I understand, no I did not!

If I understand it right, on the “bookmark-hosts” on the “desktop” screen of connectbot, the “light” in connectboot to the right of the “session” should be green if it is connected. Am I right?

I actually had one “listed” from a previous try with the scripts, but this was marked as “gray”. Note: The settings were standard for this bookmarked host (local).

In scriptmanager i only have the scripts from you set up as bookmarks. But as far as I see, they don't even have root access. (No green jolly-roger icon).

(I use scriptmanager cus i still havent figured out how to make bookmarks and widgets in Connectbot)

Note: I rebooted the device before I started the tryout and I did not start any other programs except the scripts and good (which starts automatically with the “enable_good” script)

No i do not use any ADB. (as far as I know). The only SW I use for connecting to the device from my laptop, synchronizing and such is Moborobo. There was no connection at the time of the tryout. In moborobo you need to turn on “usb debugging” when you install it. This however was set to no before the reboot before the tryout.

Concerning the “disabled autostart” I was a bit unclear in my former post. I only found one entry which was connected to Good. It is called “Good”. This entry is under “After startup” and was (and still is) deactivated.

Looking at it again now I found a couple under other headings. Such as:

Device Admin Enabled:

Mobile Device Management​

Widget updating:

Good Email​

Good Calendar​

None of these was deactivated. Should they be?

Something else: What do you think about this app “Root explorer” (v2.19 from Speedsoftware) I don’t really use that app anyway. The "Faster GPS" (v1.6)I can get rid of as well.

Before I try the suggested test in your post: am I supposed to reinstall good before? Anything else? I will wait for your reply before I make another try.

thank you very much for taking the time
[Android Software/Hacking General [Developers Only]] calisro:
Re: Good for Enterprise (GFE) [02-24-2014] root workaround

remove that mobodemon thing and root explorer. reboot. then run enable*. after it comes up, in settings-> apps, wipe data on good. That will let you activate it again. try activating it. if it works its likely one of those two apps is causing issues. you can try to introduce one at a time to see which.