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?
As you may already know, Marshmallow now include support for Multi-Window interface but, it's disabled by default. You need a little bit of tinkering to get it to work.
-First, you will need to have a rooted device, so make sure you flashed SuperSU 2.61 or 2.62 (older version won't work on Marshmallow).
-Then, you will need to edit a single line inside build.prop (located in /system folder), I did this with Root Browser because many other file browsing apps have trouble getting root access with Marshmallow. Root Browser is working perfectly as long as you have the right version of SuperSU.
-Once you open build.prop with Root Browser, you need to look for the line "ro.build.type=user", then you will need to change this line to "ro.build.type=userdebug", once it's done, reboot your phone.
-Now, you need to enable Developer settings by going in Parameters/About phone and tap on "Build number" seven time.
-You will now see the Developer settings in Parameters, open it and scroll down till you see the option about Multi-window support, tap on it to enable it. You will get a warning telling you that it's an experimental feature but who care?
-That's it, now you will have a new icon appearing on top of each apps in recent apps screen, just tap on it to get an app to appear in Multi-Window mode.
I want to see how it looks like.. May be a screenshot could do that?
Gaurav619 said:
I want to see how it looks like.. May be a screenshot could do that?
Click to expand...
Click to collapse
Sorry you'll have to Google it, simply do a search with keywords "Marshmallow multi window", I tried so many times to make screenshots on my Moto X Play and it never worked. Pushing vol-down + power button never worked for me.
worked great
My phone won't boot with this setting
great! Working
Thanks for this tip☺ I enabled it without any problem. :thumbup:
I tried I couldn't edit the line yu said ro.bulid.type=userdebug plz help me out
---------- Post added at 07:41 PM ---------- Previous post was at 07:35 PM ----------
Jose2491 said:
I tried I couldn't edit the line yu said ro.bulid.type=userdebug plz help me out
Click to expand...
Click to collapse
Am using Moto x play
Changing ro.build.type to userdebug might interfere with other functions of the device. A better way to enable multi-window on Marshmallow would be to simply add persist.sys.debug.multi_window=true to build.prop.
Nico3d3 said:
As you may already know, Marshmallow now include support for Multi-Window interface but, it's disabled by default. You need a little bit of tinkering to get it to work.
-First, you will need to have a rooted device, so make sure you flashed SuperSU 2.61 or 2.62 (older version won't work on Marshmallow).
-Then, you will need to edit a single line inside build.prop (located in /system folder), I did this with Root Browser because many other file browsing apps have trouble getting root access with Marshmallow. Root Browser is working perfectly as long as you have the right version of SuperSU.
-Once you open build.prop with Root Browser, you need to look for the line "ro.build.type=user", then you will need to change this line to "ro.build.type=userdebug", once it's done, reboot your phone.
-Now, you need to enable Developer settings by going in Parameters/About phone and tap on "Build number" seven time.
-You will now see the Developer settings in Parameters, open it and scroll down till you see the option about Multi-window support, tap on it to enable it. You will get a warning telling you that it's an experimental feature but who care?
-That's it, now you will have a new icon appearing on top of each apps in recent apps screen, just tap on it to get an app to appear in Multi-Window mode.
Click to expand...
Click to collapse
after enabling multiwindow in marshmallow battery drains due to miscellaneous
as far as i know, no-one has managed to root on new firmware. Here's how i did it:
1. Get into developer mode by going to Settings -> About phone and keep on tapping 'Build number' until it says 'Congratulations, you are a developer'
2. exit 'About phone' and go to the new tab 'Developer options' and click 'USB debugging.' Press okay.
3. exit 'Developer options' and go to security, allow 'Unknown sources.'
4. Goto www(dot)kingroot(dot)net (can't do URLs. Srry). download the apk. if you downloaded it to your phone just install. if you downloaded it to pc use a usb to transfer or something- your choice on how it gets there- and install it on the phone.
5. run it and attempt root 2 times. both times should fail. straight after the second fail exit the app, shutdown and turn on. Do not reboot, as this doesn't work if you reboot.
6. Device should be rooted. Use Purify to check. If purify isn't installed, the process failed. If purify cant get root access, the process failed. Try an app that uses root. if a tab doesn't come up, the process failed.
this is how i rooted mine. not sure if it works generically or if it was one-time for me.
I posted it here, as there is no E4g forums, and this seemed like a popular place for the E4g posts.
Stay away from kingroot
Why must stay away from kingroot?
mie_shariff said:
Why must stay away from kingroot?
Click to expand...
Click to collapse
Kingroot dosent root the phone fully its an online root so you information can get access by the app, you phone can unroot any time etc..
Hey xda
Proxy settings messed up..
I forced pdanet tablet for android to my g2d80030f... :/ I believe v1.21 is the culprit as 3.1 just crashed.
I'm running @blastagator's mostly stock lollipop with magisk and phhsu. I used a mix of my own and [email protected]Äptiva's method of
1. stock
2. stump root
3. autorec twrp 2.8ish, update twrp
4. Fota dlpkgfile
5. flash @blastagator's d800 rom with twrp or LG flash don't recall
6. Flash unsu in twrp
7. Can't remember if I flashed kernel or SELinux enabler. Seems I needed a permissive kernel edit from aptivas post...
8. Flash magiskv6 in twrp
9. Flash cbump in twrp
10. Flash phh su in twrp
Then installed pdanet 3.1, always crashed. Tried 1.21. This asks to set your g2 proxy to 127.0.0.1 and the port to 1234. After changing thus setting, I cannot find a way to revert it. I have looked for proxy settings and get mostly computer stuff. Any ideas on how to revert these changes? What are the regular settings for those numbers are if I can alter them?
Mentioning you guys due to your knowledge base. If it's back to stock I need the practice, except my network device is a Samsung (smg900p) :'(
@Äptiva
@blastagator
andrew2432 said:
Then installed pdanet 3.1, always crashed. Tried 1.21. This asks to set your g2 proxy to 127.0.0.1 and the port to 1234. After changing thus setting, I cannot find a way to revert it. I have looked for proxy settings and get mostly computer stuff. Any ideas on how to revert these changes? What are the regular settings for those numbers are if I can alter them?
Click to expand...
Click to collapse
Proxy settings would be under your APN settings, so Cell Network Settings -> Access Point Names. That's what it's called in CM13, anyway. I'm sure stock is similar.
blastagator said:
Proxy settings would be under your APN settings, so Cell Network Settings -> Access Point Names. That's what it's called in CM13, anyway. I'm sure stock is similar.
Click to expand...
Click to collapse
My mobile networks in the settings is greyed out. For me it's settings->tethering and networks->mobile networks. I believe my apn settings are in there? The greyed out part. The g2 is unlocked but has no sim, no network. The pdanet app won't clear the settings and save them.
I'm running your d80030b lp for d800, which is why I mentioned you. Also need to thank you for the rom and a few other things, in case the thousands you have need to go up
andrew2432 said:
My mobile networks in the settings is greyed out. For me it's settings->tethering and networks->mobile networks. I believe my apn settings are in there? The greyed out part. The g2 is unlocked but has no sim, no network. The pdanet app won't clear the settings and save them.
I'm running your d80030b lp for d800, which is why I mentioned you. Also need to thank you for the rom and a few other things, in case the thousands you have need to go up
Click to expand...
Click to collapse
If you don't have a SIM, you wouldn't have APNs as APNs are for a mobile network. Wifi Settings for each Wifi network contain the proxt settings. Forget your wifi network and re-add it.
Hello, if anyone could help me with this, I've tried to find firmware for this phone I've read in another thread it's from ZTE but no luck in their website, I want to root or update the firmware if anyone could help, currently the phone is freaking out not working properly. It's from Altice MEO and the name is StarAddict 6.
hello you can easily root your starradict 6 by the app named "KingRoot".
its safe and easy ,the app have his proper's root permissions manager's(exactly like super su) ,and works fine.You can also unroot your device by the KingRoot app too;(if you want to unroot definitively ,factory reset your device is hughly recommended)
For the firmware ,its more hard ,its need to use the DFU mode.
But for now i cant help you for where found the firmware.
one good solution is to make a dump of your firmware,its look like a backup in recovery,for mmake this im sure you can easily find how to make this on xda or google.
im looking for the firmware too ,if i found how and where to download it ,i post here for the starraddict community users.
friendly
I found the firmware boys
https://drive.google.com/file/d/1qIgNdLwDc5p6WxrohIwIjpvheBCe6nKR/view
neves2k said:
I found the firmware boys
https://drive.google.com/file/d/1qIgNdLwDc5p6WxrohIwIjpvheBCe6nKR/view
Click to expand...
Click to collapse
Found the password. I looked up the file name on google and it lead me to firmware247 which had the password there. (It's https://firmware247.com).
How to unbrick:
Get any SDCard on your PC and paste the l730.v1 folder inside the root of the sdcard.
Put it back on the phone.
While pressing both Vol +, Vol - press Power Button.
This will put you into the "recovery mode" (if you can call it that...) which will read the files and install them
If you've reached this far hopefully your phone is working again
ROOT with Magisk:
Download and install Dr. Fone root tool (make sure it's the root tool and not the management/backup tool)
Go into phone developer settings and enable OEM Unlocker and USB debugging
Root the phone with Dr. Fone root tool (it will ask to install supersu, accept it)
When you open supersu, DO NOT UPDATE THE BINARIES, or you will go into bootloop (happened to me at least)
Install magisk manager apk
Open magisk so you get the prompt to allow on it supersu
Restart magisk and super su app (for some reason some options don't appear on magisk if you don't do this)
Download and install (patch) magisk to directly.
Reboot as prompted by the tool.
Open supersu and go into options.
Select delete supersu and remove "root" (you will need to allow supersu root permissions on magisk)
That's it, you now have your phone rooted with magisk.
Unfortunately I wasn't able to find a way to fix safety net, please let me know if you do. (CTS Profile is flagged)
Edit: Organized the post and added small guide.