Disclaimer: This is for testing purposes only. I do not condone breaking company policy, or breaking any laws. I am not responsible for you getting fired as a result of you making these modifications. You should always read and abide by company policies and any laws pertaining to such modifications. Use of this tutorial is at your own risk.
Preface: I have tested the new method on multiple devices and it has been flawless so far.
UPDATE: I have found a new method that so far has been flawless across multiple devices so far for me. With this new method you won't even have MobileIron installed when you're done! I have tested this on my Galaxy Nexus, My Nexus 7 and my Galaxy Note II and believe it should work regardless of device. Your company may have different security policies than mine so it's possible this may not work for you.
The easiest way to do this is with one of mskip's toolkits, but it can also be done manually with adb (must have the latest sdk).
Toolkit Method
0. Make sure you have MobileIron and Touchdown installed, configured and syncing. Your phone does NOT have to be rooted to do this.
1. Download mskip's Toolkit Here and install.
2. Make sure you have the adb drivers for your phone installed on your computer and android debugging is turned on in the developer settings on your phone.
3. Open the toolkit and connect your phone to your computer
4. It shouldn't matter what model phone you choose for the purpose of what we're doing, and the options may be slightly different based on which toolkit you download
5. Choose the option backup and restore your device
6. Choose backup all installed apps
7. Choose do NOT include system apps in the backup
8. Choose backup apk's AND respective app data
9. Choose do NOT back up internal storage data in backup
10. Wake your phone and it will ask you to start the backup, choose to do so
Once it is finished you will need to wipe your phone. It may work without wiping and just uninstalling touchdown and Mobileiron before proceeding to the next section, but I haven't tested this.
11. Connect your phone to your computer and enable android debugging
12. Browse to C:\Galaxy Nexus Toolkit (or whatever the name of your toolkit is under c:\)
13. Open the folder backups and rename the backup file to backup.bak. (if you don't see the file extension just name it backup)
14. Open the toolkit and choose a model
15. Choose Backup and Restore
16. Choose Restore apps from a backup file
17. type backup.bak and press enter
18. Wake your phone and choose to begin the restore
19. When it's finished, uninstall mobileiron, open touchdown and see if it's syncs!
ADB Method
adb backup -all -system -shared -apk
recovery> backup, wipe, flash rom, flash gapps, reboot
adb restore backup.ab
Requirements For ICS:
1. Rooted Android Phone running ICS based ROM
2. Titanium Backup (app installed)
3. Hide my Root (app installed)
4. Mobileiron (app installed but never run)
5. Touchdown (app installed but never run)
Instructions for ICS:
0. Make a Nandroid backup
1. Open Hide my Root
2. Choose hide SU binary
3. Press home
4. Menu, settings, apps, all apps
5. Choose Superuser.apk
6. Choose disable
7. Now open mobileiron and configure the settings per your company's instruction.
8. Set up your email in the Touchdown application and let it sync everything.
9. Open Hide my Root and choose restore SU Binary
10. Go back to menu, settings, apps, superser.apk and choose enable. (Its at the bottom when disabled)
11. Open Titanium Backup
12. Choose backup/restore from the top
13. Scroll to Mobileiron and tap it and choose freeze.
14. Profit
Now restore your nandroid backup before you get in trouble.
**Update** for Jelly Bean
It seems the builds out there for Jelly Bean use a new version of SuperUser that as of yet isn't compatible with Hide My Root. I wrote the developer of Hide My Root and he is looking into this but currently doesn't have a device running Jelly Bean to test on, so I took it upon myself to figure this out once again. I tested this and it does work. Again this was tested on a VZW Galaxy Nexus only.
Instructions for Jelly Bean:
0. Make a Nandroid backup!
1. Download MobileIron (App installed but never run)
2. Download Touchdown (or any apps that depend on MobileIron and do not launch them)
3. Download Titanium Backup (You may need the premium version to freeze apps)
4. Download SuperSU flashable zip from HERE and place on your SDcard.
5. From the app drawer launch SuperSU (that app already installed, not the zip you just downloaded)
7. Swipe 2 screens to the right to Settings
8. Choose Full unroot.
9. Install and configure MobileIron and dependent apps and let them fully sync.
10. Enable Airplane Mode
11. Reboot to recovery and flash the SuperSU zip you downloaded
12. Boot into Android, open Titanium Backup and freeze MobileIron
13. Turn off Airplane Mode
14. Profit
Now restore your nandroid backup before you get in trouble.
After a reboot all of the lockscreen options will reappear allowing you to have an insecure lockscreen.
This is great
You just saved me hours of frustration.
Thanks!
Thanks - this is a huge help!!
Question: does this work only with Touchdown, or any Android email client? (I prefer the app Enhanced Email).
SoCalNewb said:
Thanks - this is a huge help!!
Question: does this work only with Touchdown, or any Android email client? (I prefer the app Enhanced Email).
Click to expand...
Click to collapse
I have only tested this as posted. Make a nandroid backup and play around with it
How to re-enable superuser?
Made a nandroid backup. Followed instructions below. Works great, now I can synch email with MobileIron fortified corp server AND change the PIN lock requirement that MobileIron required! Thank you
Only one issue: I couldn't complete step 10 ("Go back to menu, settings, apps, superser.apk and choose enable"). Superuser was no longer in the "All" list under menu, settings, apps. As a result, I seem to have lost the ability to grant root access to new applications.
QUESTION: How do I re-enable superuser?
Notes:
- ADB: I can connect to device via ADB, but if I type "adb shell", and then type "su" at the "sh-3.2#" promot, no $ access is granted).
- Terminal Emulator: TE cannot get root (I type "su" at the "sh-3.2$" command, and TE says "Permission denied")
- Root Access - Old Apps: Any apps that previously had root privileges still do (Root Explorer can navigate to "/" and enable "Mount R/W", Wifi Tether still works, etc).
- Root Access - New Apps: New apps requiring root are not able to get root (no superuser prompt comes up)
- Re-Installing Superuser.apk: I tried using root installer to re-install superuser.apk (in the "/system/app" directory). It said it installed successfully, but still no superuser in the "All" list under menu, settings, apps.
- Re-Rooting: I tried re-rooting (using mskip's exceelend GNEX toolkit HERE), to no avail (process completes, but no superuser access).
If anyone can help me troubleshoot I would be extremely appreciative. I've tried to not be a helpless newb and to try a few fixes (above), but I would be ecstatic if one of XDA's Android ninjas could tell me how to re-enable superuser. Hoping to avoid comments of "restore nandroid backup and give up"
bhilgeman said:
1. Open Hide my Root
2. Choose hide SU binary
3. Press home
4. Menu, settings, apps, all apps
5. Choose Superuser.apk
6. Choose disable
7. Now open mobileiron and configure the settings per your company's instruction.
8. Set up your email in the Touchdown application and let it sync everything.
9. Open Hide my Root and choose restore SU Binary
10. Go back to menu, settings, apps, superser.apk and choose enable.
11. Open Titanium Backup
12. Choose backup/restore from the top
13. Scroll to Mobileiron and tap it and choose freeze.
Click to expand...
Click to collapse
SoCalNewb said:
Made a nandroid backup. Followed instructions below. Works great, now I can synch email with MobileIron fortified corp server AND change the PIN lock requirement that MobileIron required! Thank you
Only one issue: I couldn't complete step 10 ("Go back to menu, settings, apps, superser.apk and choose enable"). Superuser was no longer in the "All" list under menu, settings, apps. As a result, I seem to have lost the ability to grant root access to new applications.
QUESTION: How do I re-enable superuser?
Notes:
- ADB: I can connect to device via ADB, but if I type "adb shell", and then type "su" at the "sh-3.2#" promot, no $ access is granted).
- Terminal Emulator: TE cannot get root (I type "su" at the "sh-3.2$" command, and TE says "Permission denied")
- Root Access - Old Apps: Any apps that previously had root privileges still do (Root Explorer can navigate to "/" and enable "Mount R/W", Wifi Tether still works, etc).
- Root Access - New Apps: New apps requiring root are not able to get root (no superuser prompt comes up)
- Re-Installing Superuser.apk: I tried using root installer to re-install superuser.apk (in the "/system/app" directory). It said it installed successfully, but still no superuser in the "All" list under menu, settings, apps.
- Re-Rooting: I tried re-rooting (using mskip's exceelend GNEX toolkit HERE), to no avail (process completes, but no superuser access).
If anyone can help me troubleshoot I would be extremely appreciative. I've tried to not be a helpless newb and to try a few fixes (above), but I would be ecstatic if one of XDA's Android ninjas could tell me how to re-enable superuser. Hoping to avoid comments of "restore nandroid backup and give up"
Click to expand...
Click to collapse
When you disable superuser.apk in the apps list it moves it from the alphabetical order to the bottom of the apps list. Look there and see if its at the bottom of your apps list.
bhilgeman said:
When you disable superuser.apk in the apps list it moves it from the alphabetical order to the bottom of the apps list. Look there and see if its at the bottom of your apps list.
Click to expand...
Click to collapse
YOU ARE THE MAN.
That was so simple, but I spent an hour trying stuff and still missed it
My Android experience is back to awesome despite Mobile Iron - THANK YOU!!!!
Thanks for that. Great idea.
I followed your instructions but I had to switch 9 and 10 because Hide my root cannot restore a deactivated app.
But my TouchDown says "Synchronization Error" --> access denied (update your password). Maybe too strong policies?
And by the way: you have to use tintanium backup PRO to enable or disable apps
---------------------
Edit: I made a system application of "Hide my root" with TI Backup - works. I had to uninstall TI Backup now - currently TouchDown is syncing again. We will see if it works, next: I try to use LBE Privacy Guard... will report. Disabling "MobileIron" seems not working for me...
Hey, is not possible solve it on 2.X version of Andriod? Thanks...
OP Updated to reflect Changes for those running JellyBean. Long live the Android experience!
bhilgeman said:
The SU change needed for JellyBean makes this previous method unusable. I did however figure out how to still get to the same result if you're running JellyBean.
I will so an update to the OP soon to reflect this.
Click to expand...
Click to collapse
Looking forward to the instructions for making this work on JB
SoCalNewb said:
Looking forward to the instructions for making this work on JB
Click to expand...
Click to collapse
OP updated for JB instructions.
Sorry, I haven't tested this on a 2.x build so I'm not sure. If I get time I'll try to test this for you, I'm just super slammed with projects right now...
Will we appear "normal" on the Server that the app links us to our Corp acct??
Yes, you will appear as a non rooted phone. I just updated the JB instructions again. Realized I left out a step.
Anyone test this for Airwatch yet?
FWIW.....my experience has shown this to be merely a temporary solution, by itself. Yes...following the JB instructions will allow you to sync up just fine. But.....when mobileiron does not report back as device administrator, the red flags go up. My solution, thus far, has been to suspend root access on the phone, after reactivating mobileiron. In my case, after re-activating mobileiron, the app, itself, now FC's, which may be helping me out....not sure. At this point I seem to be able to continue remaining synced, without root access. As long as I use airplane mode before enabling root access to do root-type stuff, I seem to be fine. Word of caution, though....disabling root, seems screw up TB when I re-enable root. Specificaly...even though I have TB pro, it does not register after re-enabling root, so freezing and unfreezing mobileiron at will has not been possible. Could just be my system though.I recommend using airplane mode liberally if there is any doubt regarding your recognized root/non-root status. This definitely changes how I use the device, though, for sure.
makelegs said:
FWIW.....my experience has shown this to be merely a temporary solution, by itself. Yes...following the JB instructions will allow you to sync up just fine. But.....when mobileiron does not report back as device administrator, the red flags go up. My solution, thus far, has been to suspend root access on the phone, after reactivating mobileiron. In my case, after re-activating mobileiron, the app, itself, now FC's, which may be helping me out....not sure. At this point I seem to be able to continue remaining synced, without root access. As long as I use airplane mode before enabling root access to do root-type stuff, I seem to be fine. Word of caution, though....disabling root, seems screw up TB when I re-enable root. Specificaly...even though I have TB pro, it does not register after re-enabling root, so freezing and unfreezing mobileiron at will has not been possible. Could just be my system though.I recommend using airplane mode liberally if there is any doubt regarding your recognized root/non-root status. This definitely changes how I use the device, though, for sure.
Click to expand...
Click to collapse
I run your CM10 build on my nex7 and love it. Great to have navbar mods.
On my nex7 it took me a few tries to get it to stick but I finally got it. I hadn't updated a nightly for a couple weeks and when I did Mobileiron got me. I decided I don't care about getting work email on my tablet as much as I do my phone so no big deal. I freaking hate Mobileiron and touchdown nearly as bad.
On my galaxy nexus (running fitsnugly cm10) I don't have any issues. I flash the nightlies every day and I've gone a couple months without Mobileiron flagging me.
Sent from my Nexus 7 using xda app-developers app
bhilgeman said:
I run your CM10 build on my nex7 and love it. Great to have navbar mods.
On my nex7 it took me a few tries to get it to stick but I finally got it. I hadn't updated a nightly for a couple weeks and when I did Mobileiron got me. I decided I don't care about getting work email on my tablet as much as I do my phone so no big deal. I freaking hate Mobileiron and touchdown nearly as bad.
On my galaxy nexus (running fitsnugly cm10) I don't have any issues. I flash the nightlies every day and I've gone a couple months without Mobileiron flagging me.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Skanklove!
I was completely under the radar, due to some corporate user configs, until I screwed up and raised the red flag. Then I had to encrypt, and install mobileiron. I was perfectly happy with touchdown until mobileiron got involved. I don't want work email on any device other than my work phone (toro). I can still run email without mobileiron, but no activesync and no email attachments......meh
Steps on ICS
Hello,
I am new to using mobileiron, as my corporation just started to use this program. Can I use your steps on ICS and keep my root undetected or will I eventually have issues. Last question, why is it necessary to restore your nandroid backup at the end?
Of course superuser got updated again and everything goes crazy.
Titanium backup can't get root after this new superuser updates today. What to do what to do?
I was planning to go to the previous version by using titanium backup but i can't use it because of no root..
stupid superuser...
Have you tried running superuser to allow it to enable root access for itself?
I've just updated it, ran it, set auto response to allow then ran ES File Explorer and Link2SD and everything works.
automatic response is on allow set.
link2sd works, but titanium backup doesn't and now neither busybox.
i manually installed from recovery this:
su-bin-3.1-arm-signed.zip
Superuser-3.1.3-arm-signed.zip
but i still can't obtain root with titanium backup and busybox.
what else to do?
Try checking the superuser app on the market. See if there are any other reports about this issue. If not, then email developer via the available options on the app page.
In my case with sony live with walkman w19i, I need to always enable usb debugging to get it work.
If I disable usb debug, then I'll get problem like yours.
Please report this bug. Don't know how to contact the dev,,,,,
I have also performed the following:
Settings -> Apps - Superuser -> Force stop -> Clear data -> Open su and update binaries.
As you may know, Google has remove App Ops on Android 4.4.2. This app helps you to bring it back
Root device only for now
What is App Ops
App Ops is an activity, within the Settings app, that allows users to enable or disable operations on a per-app basis. These operations cover many common scenarios identified by permissions (e.g., read contacts, write contacts, access location), though it is not a pure one-to-one mapping.
Operations blocked by App Ops are inaccessible by the affected app, though that may vary by device.
Toggle-able permissions
- Access notifications
- Alarm volume
- Audio focus
- Bluetooth volume
- Call phone
- Camera
- Draw on top
- Keep awake
- Location
- Master volume
- Media buttons
- Media volume
- Modify calendar
- Modify call log
- Modify clipboard
- Modify contacts
- Modify settings
- Notification volume
- Play audio
- Post notification
- Read calendar
- Read call log
- Read clipboard
- Read contacts
- Read SMS/MMS
- Receive SMS/MMS
- Record audio
- Ring volume
- Send SMS/MMS
- Vibrate
- Voice volume
- Write SMS/MMS
Download
Google Play:
Free: https://play.google.com/store/apps/details?id=droidmate.appopsinstaller
Pro: https://play.google.com/store/apps/details?id=droidmate.appopsinstallerpro
Any feedback, report, please leave your comment.
Change logs
Ver 1.1
- Add uninstall AppOps
- Add update AppOps
- Fixed minor bugs
- Refine permission list
Ver 1.0
- Initial release
It's weird that this thread has no activity.. it's a proper mod tbh.
After clicking to "Install AppOps Root", the device reboots, but nothing seems to change. Starting the Installer again still shows the same message: "Click to install AppOps Root..."
If I click "Launch Stock App Ops", I see Settings that promptly closes.
I am rooted and running a 4.4.2 ROM.
What am I missing?
App is working great. But can you please change the Icon in the drawer? It is really hard to see with this dark grey color
gadgetguy08 said:
After clicking to "Install AppOps Root", the device reboots, but nothing seems to change. Starting the Installer again still shows the same message: "Click to install AppOps Root..."
If I click "Launch Stock App Ops", I see Settings that promptly closes.
I am rooted and running a 4.4.2 ROM.
What am I missing?
Click to expand...
Click to collapse
There are now two icons in the Drawer to choose. Select "AppOps Root"
haelmchen said:
There are now two icons in the Drawer to choose. Select "AppOps Root"
Click to expand...
Click to collapse
Not for me.
I have run through installation twice and didn't see any errors.
I just got prompted to d/l new firmware for my note 3 today. and after hearing they took this out. I declined it! keeping an eye on this, hopefully there will be a way to bring this back for non rooted devices. as my phone is only 2 months old. and I wana wait 4-6 months to make sure its not faulty B4 I go rooting it. plus there arent enough stable ROMS for note 3 anyway. I like Wanam as its stock ish without bloat. so waiting for wanam!
Reboot after install
Im using CM11.0 and the phone reboots after I click "Install AppOps Root" but seems to work fine with the "Lauch Stock AppOps" option.
Good job. Thank you.
Works great for me running Stock 4.4.2 on Nexus 5.
Can i use this app with ART?
Gesendet von meinem Nexus 4 mit Tapatalk
[email protected] said:
Can i use this app with ART?
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
It's working for me with ART
same here
gadgetguy08 said:
After clicking to "Install AppOps Root", the device reboots, but nothing seems to change. Starting the Installer again still shows the same message: "Click to install AppOps Root..."
If I click "Launch Stock App Ops", I see Settings that promptly closes.
I am rooted and running a 4.4.2 ROM.
What am I missing?
Click to expand...
Click to collapse
same for me. i can only run "Launch Stock AppOps", install method causes restart with no change. I can change permissions though, which is nice. (running codefirex ROM, android 4.3 on Oppo Find 5 - couldnt find app ops option in this ROM )
thanks developer
Awesome. I was looking for something like this.
As this changes this system files can we uninstall if we want? I have not installed it yet
Jarvis4 said:
As this changes this system files can we uninstall if we want? I have not installed it yet
Click to expand...
Click to collapse
It only installs one apk in /system/priv-app/
If you are rooted and have titanium backup or other toolbox you can easily uninstall it (titanium can uninstall system apps); second easiest option is to use ES File Explorer or other root file manager; other ways include adb shell commands (mount / rm), and finally another method that actually doesn't require root is via custom recovery that has a builtin file manager like twrp does... you would mount /system and delete the apk from /system/priv-app
sordna said:
It only installs one apk in /system/priv-app/
If you are rooted and have titanium backup or other toolbox you can easily uninstall it (titanium can uninstall system apps); second easiest option is to use ES File Explorer or other root file manager; other ways include adb shell commands (mount / rm), and finally another method that actually doesn't require root is via custom recovery that has a builtin file manager like twrp does... you would mount /system and delete the apk from /system/priv-app
Click to expand...
Click to collapse
Thanks have titanium backup installed, will just use that if I want to uninstall, good to know for other root apps that I might use in the future
:good:
How does this compare to the likes of XPrivacy. It appears this completely denies the permission which would cause certain apps to crash vs providing random false data.
SilentSummer said:
How does this compare to the likes of XPrivacy. It appears this completely denies the permission which would cause certain apps to crash vs providing random false data.
Click to expand...
Click to collapse
XPrivacy is way more powerful and allows you to revoke many more permissions, but App Ops although limited, works quite well. You cannot remove network access with it, but I removed location, contacts, vibrate, camera, from some apps, and none crashed so far. I've been using App Ops since it was introduced in Jelly Bean, and still do in KitKat.
Jarvis4 said:
As this changes this system files can we uninstall if we want? I have not installed it yet
Click to expand...
Click to collapse
Version 1.1 is out which supports to unisntall App Ops.
safet.me said:
Version 1.1 is out which supports to unisntall App Ops.
Click to expand...
Click to collapse
I still get a quick reboot and nothing else.
On 4.4.2, rooted and have given the app SuperUser privileges.
gadgetguy08 said:
I still get a quick reboot and nothing else.
On 4.4.2, rooted and have given the app SuperUser privileges.
Click to expand...
Click to collapse
If it works, you should see a new app named "App Ops [Root]" in your app drawer. Anyway, which is your ROM?
Hi Everyone.
I'm having issues trying to get secure settings set up with tasker. When I attempt to enable System+ Module it initializes forever. The one time I got it to work, it was operational for about five minutes, before it disabled itself on its own. I have SuperSU set to allow all apps that request root. Its still not working.
Any ideas? Thanks!
I have it running fine on my device. What steps have you tried to get it working? Rebooted the device? Cleared data and cache? Uninstalled and reinstalled?
curry101 said:
Hi Everyone.
I'm having issues trying to get secure settings set up with tasker. When I attempt to enable System+ Module it initializes forever. The one time I got it to work, it was operational for about five minutes, before it disabled itself on its own. I have SuperSU set to allow all apps that request root. Its still not working.
Any ideas? Thanks!
Click to expand...
Click to collapse
Make sure you activate the system+ module prior to granting administrative access. Also make sure you have root.