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?
DISCLAIMER: I am NOT RESPONSIBLE on anything that will happen on your device such as getting bricked or malfunctioning. I only posted this little trick I found out to help others who are also in the same boat. This method MAY or MAY NOT WORK on your device, so proceed at your own risk.
=====================================
Maybe some of you have not seen any Superuser prompt that appears whenever you run apps that needs root (example are Link2SD, Titanium Backup) and etc. Out of frustration last night, I tried to find a way to fix this and I have indeed found it.
But before that here are some of the prerequisites needed:
-Phone/Tablet must be ROOTED
-Has access to system using File Explorers such as Mi(UI) File Explorer, Root Explorer and other explorer that DO NOT prompts Superuser. What I mean here is that you can see /data, /mnt, /etc folders and the like.
..and here are the little steps in fixing it:
1. Download and install BusyBox from Google Play Store.
2. Open BusyBox, select 1.20.2.
3. Click install, and wait for it and it's done.
4. After BusyBox has been installed, download SuperSU from Play Store.
5. Install and let it load.
6. After loading, press YES when asked to update SU Binary.
7. When it's done, press back and try apps that needs root like Titanium Backup.
And there, notification prompt would appear again!
NOTE: UNINSTALL, take note UNINSTALL previous Superuser app through Root Uninstaller. Main reason why that should be uninstalled so that there would be no conflicts with the SU app.
OPTIONAL: you MAY UNINSTALL BusyBox app but I recommend not so to avoid any problems.
I have also applied this method to my tablet that's already rooted but doesn't have Superuser app yet. A simple press of thanks is highly appreciated. :3
hey, I've been trying and trying again but still can't... what should I do? root explorer cant fix my problem.. superSU, superuser fixer, it can't fix my problem too.
ellynepain said:
hey, I've been trying and trying again but still can't... what should I do? root explorer cant fix my problem.. superSU, superuser fixer, it can't fix my problem too.
Click to expand...
Click to collapse
It's not working for me neither, i can't fix this superuse thing
I just rooted my Asus TF101 tablet with Brk's Root Toolkit v8.
It says I am now rooted, but is there any way to know for sure?
I have rooted my phone before & when I did that I was able to remove all the useless apps that came preinstalled, but on my Tablet it will not let me. I was thinking with root access I would be able to do this.
I am thinking of flashing to another ROM, but want to be sure this thing is rooted first.
Any insight is appreciated!!
Thx!!!
Do you have a SuperUser or SuperSU app installed?
I would open it and see what happens.
Also, I do not believe you can uninstall system apps JUST being rooted, you need an app like Titanium Backup to do the uninstalling. They still are not uninstallable in the Settings - Apps section just by rooting.
Alternatively, install a root explorer (or enable Root Explorer permissions in ES File Explorer) and see if you get prompted for root access without errors.
frederuco said:
Do you have a SuperUser or SuperSU app installed?
I would open it and see what happens.
Also, I do not believe you can uninstall system apps JUST being rooted, you need an app like Titanium Backup to do the uninstalling. They still are not uninstallable in the Settings - Apps section just by rooting.
Alternatively, install a root explorer (or enable Root Explorer permissions in ES File Explorer) and see if you get prompted for root access without errors.
Click to expand...
Click to collapse
Ah.....forgot about Titanium back up. I knew there was an app I needed to use.
I open SuperUser & it just says No Apps in List or something.
thx!!
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Boffortes said:
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Click to expand...
Click to collapse
uninstall supersu and try this one. some people have issues with supersu and have found superuser to work correctly.
Here is how to root the new BLU Life One, there are probably many ways to do it but this was the best way that I could find.
Note that I tried to root with framaroot, towelroot, and iroot and their apps have failed.
Try this of your own free will, I am not responsible for anything happening to your device (it worked for me so it should work for you).
What you will need:
kingoroot, supersu, busybox, root checker, and titanium backup.
First things first,
Go into settings and check the box next to "Unknown sources".
Next open up the internet tab and search for Kingoroot (kingorootapp dot com)
Click the download button for android (not the windows one)
When it finishes downloading, click in the drop down menu and install the apk.
Open the kingo root app, and click root circle.
After the app is finished rooting your device, you can download Root checker in the play store to ensure that your device is indeed rooted.
Now, I personally don't like kingo root, so the next steps are optional.
In the play store download three apps, SuperSU ( i use chainfire), busybox, and titanium backup (i suggest buying the paid version, it is well worth the money).
Next open up SuperSU (KingoUser should ask to grant SuperSU root access, allow it), and install the SU binary. Do not reboot system.
Next open titanium backup, click the middle tab, then scroll down until you see SuperSU. Long press, and then press install to system apps. (you can do this manually by using ES file explorer and copying the SuperSU.apk file [may need to download it from the internet] in to the/system/app folder.
Now restart your device.
When the device boots back up, check and make sure that your device is still rooted by using root checker again.
If it is still rooted, open SuperSU and make sure you dont have to install the binarys again (you shouldnt have to).
Next uninstall the kingo root app (it will not let you uninstall the kingouser app, for this you must use titanium backup)
Now go into your system, applications and then disable kingouser app.
After doing so, check and see if your device is still rooted (it should be)
If it is still rooted, proceed to use titanium backup to uninstall kingouser app.
Lastly install busy box. If you get an error saying "unable to install choose another location" simply click on where it says "/system/xbin" and change it to "system/bin".
And there you should have a freshly rooted device with no kingoroot. Not saying Kingoroot is bad, i just have always used SuperSU
Credits:
To the developers of kingoroot, supersu, busybox, root checker, and titanium backup!
ikpb said:
Here is how to root the new BLU Life One, there are probably many ways to do it but this was the best way that I could find.
Note that I tried to root with framaroot, towelroot, and iroot and their apps have failed.
Try this of your own free will, I am not responsible for anything happening to your device (it worked for me so it should work for you).
What you will need:
kingoroot, supersu, busybox, root checker, and titanium backup.
First things first,
Go into settings and check the box next to "Unknown sources".
Next open up the internet tab and search for Kingoroot (kingorootapp dot com)
Click the download button for android (not the windows one)
When it finishes downloading, click in the drop down menu and install the apk.
Open the kingo root app, and click root circle.
After the app is finished rooting your device, you can download Root checker in the play store to ensure that your device is indeed rooted.
Now, I personally don't like kingo root, so the next steps are optional.
In the play store download three apps, SuperSU ( i use chainfire), busybox, and titanium backup (i suggest buying the paid version, it is well worth the money).
Next open up SuperSU (KingoUser should ask to grant SuperSU root access, allow it), and install the SU binary. Do not reboot system.
Next open titanium backup, click the middle tab, then scroll down until you see SuperSU. Long press, and then press install to system apps. (you can do this manually by using ES file explorer and copying the SuperSU.apk file [may need to download it from the internet] in to the/system/app folder.
Now restart your device.
When the device boots back up, check and make sure that your device is still rooted by using root checker again.
If it is still rooted, open SuperSU and make sure you dont have to install the binarys again (you shouldnt have to).
Next uninstall the kingo root app (it will not let you uninstall the kingouser app, for this you must use titanium backup)
Now go into your system, applications and then disable kingouser app.
After doing so, check and see if your device is still rooted (it should be)
If it is still rooted, proceed to use titanium backup to uninstall kingouser app.
Lastly install busy box. If you get an error saying "unable to install choose another location" simply click on where it says "/system/xbin" and change it to "system/bin".
And there you should have a freshly rooted device with no kingoroot. Not saying Kingoroot is bad, i just have always used SuperSU
Credits:
To the developers of kingoroot, supersu, busybox, root checker, and titanium backup!
Click to expand...
Click to collapse
Hi, thanks for this info, works for me. You should publish this info in the official Blu Life One thread. Thanks again for this.
if someone here has a working blu life one 2015, could you do a rom dump. a bunch of us have soft bricked phones and can't get them working. Blu doesn't have the stock rom available
Hey thanks for this guide! I have one problem I'm hoping you could shed some light on. I've followed your steps and when I try to update the SU binaries it fails every time. The kingroot worked and the kingroot su asked if I wanted SuperSu to have root access and I selected yes. Each time it fails to update it suggest I reboot and try again, but I haven't yet.
Thanks again
Robert