[Q] How does MaaS360 detect root device? - Android Q&A, Help & Troubleshooting

My company has instituted use of MaaS360 as a MDM for BYOD android phones. The IT folks are preventing rooted and jailbroken phones from accessing corporate email from exchange.
On my Galaxy S4 I have tried several things to work around, including OTA Rootkeeper, Hide my root app, and SuperSU's temporary unroot. However MaaS360 manages to find out that the phone is still rooted. I tried the solution posted for Mobileiron on this site (freezing the MDM using TiBU immediately after rooting) but that does not work either.
My IT department is fine with "temporary" unroot but they do not think that it is possible to do so in MaaS360 while still ensuring that the device is not permanently rooted. I am wondering if someone knows how MaaS360 figures out that a device is rooted and whether there is a way for it to nor report when the device is temporarily unrooted using one of the methods discussed above.

---

Have you found a solution to this problem? I was wondering the same thing.
walletless said:
My company has instituted use of MaaS360 as a MDM for BYOD android phones. The IT folks are preventing rooted and jailbroken phones from accessing corporate email from exchange.
On my Galaxy S4 I have tried several things to work around, including OTA Rootkeeper, Hide my root app, and SuperSU's temporary unroot. However MaaS360 manages to find out that the phone is still rooted. I tried the solution posted for Mobileiron on this site (freezing the MDM using TiBU immediately after rooting) but that does not work either.
My IT department is fine with "temporary" unroot but they do not think that it is possible to do so in MaaS360 while still ensuring that the device is not permanently rooted. I am wondering if someone knows how MaaS360 figures out that a device is rooted and whether there is a way for it to nor report when the device is temporarily unrooted using one of the methods discussed above.
Click to expand...
Click to collapse

---

cloudspy said:
Have you found a solution to this problem? I was wondering the same thing.
Click to expand...
Click to collapse
Nope... the only solution is to do a permanent unroot after setting up the ROM/device to your liking and before adding the MaaS360-enabled account.

---

Sounds like a reasonable solution to me. Thank you.
walletless said:
Nope... the only solution is to do a permanent unroot after setting up the ROM/device to your liking and before adding the MaaS360-enabled account.
Click to expand...
Click to collapse

---

walletless said:
Nope... the only solution is to do a permanent unroot after setting up the ROM/device to your liking and before adding the MaaS360-enabled account.
Click to expand...
Click to collapse
Yes, I find it alright. Make sure you reboot twice after doing a perm unroot (and before adding your MaaS360 enabled account). Sometimes it takes a additional reboot before the phone actually removed all su-related binaries.
Sent from xda-developers mobile app on Galaxy S4 using GOLDENEYE ROM

---

walletless said:
Yes, I find it alright. Make sure you reboot twice after doing a perm unroot (and before adding your MaaS360 enabled account). Sometimes it takes a additional reboot before the phone actually removed all su-related binaries.
Sent from xda-developers mobile app on Galaxy S4 using GOLDENEYE ROM
Click to expand...
Click to collapse
Could you please confirm that it's okay to have a custom ROM flashed while using MDM so long as the device is no longer rooted?
I'd like to do this without ever getting flagged in the first place. My plan is to uninstall maas360, root the device, flash my custom rom, perm unroot the device, reboot twice and reinstall maas360. Will this be okay?
Thanks

---

illmatik said:
Could you please confirm that it's okay to have a custom ROM flashed while using MDM so long as the device is no longer rooted?
I'd like to do this without ever getting flagged in the first place. My plan is to uninstall maas360, root the device, flash my custom rom, perm unroot the device, reboot twice and reinstall maas360. Will this be okay?
Thanks
Click to expand...
Click to collapse
I believe that answer depends on how your organization has set security policies on the MDM. For me, I have been using custom ROM (GoldenEYE) for several months now, and not been flagged so long as I add the exchange account after doing a full unroot and rebooting twice. You may want to check with your IT if they are OK with custom ROMs.. Most IT would be OK if you unroot I guess.
The steps you outlines are fine - I pretty much use the same sequence everytime I update to a newer version of the ROM. So far, no problems since 6+ months!

---

you may want to try rootcloak plus http://forum.xda-developers.com/showthread.php?t=2607273
I'd be very interested in hearing if it works for Maas.

---

abandon42 said:
you may want to try rootcloak plus http://forum.xda-developers.com/showthread.php?t=2607273
I'd be very interested in hearing if it works for Maas.
Click to expand...
Click to collapse
Long-time lurker, first time poster just to confirm that yes the Rootcloak Xposed module worked for Maas360 on my HTC One! -Thanks

---

Rootcloak settings?
miguelsaps said:
Long-time lurker, first time poster just to confirm that yes the Rootcloak Xposed module worked for Maas360 on my HTC One! -Thanks
Click to expand...
Click to collapse
Excellent. Thanks, Miguelsaps.
What settings did you use in Rootcloak?

---

SkyHawk4 said:
Excellent. Thanks, Miguelsaps.
What settings did you use in Rootcloak?
Click to expand...
Click to collapse
No problem! All I did was download the RootCloak 1.4 framework in Xposed, then soft-rebooted my phone and and sent myself the Maas360 registration once again and it allowed me to complete it!
Edit: sorry I added the com.fiberlink... in Rootcloak firstly.

---

miguelsaps said:
No problem! All I did was download the RootCloak 1.4 framework in Xposed, then soft-rebooted my phone and and sent myself the Maas360 registration once again and it allowed me to complete it!
Edit: sorry I added the com.fiberlink... in Rootcloak firstly.
Click to expand...
Click to collapse
hi, could you please share with us your complete settings?
I have n5, currently Cataclysm rom (which comes prerooted), and both xposed with rootcloak and cydia with rootcloak+.
Maas 4.41 still detects root.
if you have an older version, could you please backup it and send me the link to it?
thanks!
mic

---

Success!
I've succeeded at this. http://forum.xda-developers.com/showpost.php?p=51990953&postcount=4

---

Hello
I speak very little English, excuse me for my English
I'm not new to the Root,I have a Samsung S4 Root with a lot of application for whom I need a root
My problem is that my company asked me to set the phone control app MaaS360
I installed MaaS360, the app tells me that I do not respect the safety and policy MaaS360 tells me to reset the phone to the original without Root.
I seek a way to make him believe that the phone is not root
Do you have any idea?
It's very urgent
Best regards

---

Maas360 Validating Samsung enterprse license
hi guys,
im having a problem with my maas360. after activating the maas as a device administrator im stuck with the loading page saying validating samsung enterprise license what does it means ? btw my phone is samsung note 3 and rooted with a custom rom installed.
i dont think i have the same problem with guys years ago . can you please help me with this ?

---

I have same problem... But ONLY with MIUI - with Flyme, EUI, Lineage, CM... all UNROOTED : MAAS360 WORKING
... And I not understand WHY! (all other app, control my machine... And the result is ALWAYS : UNROOTED)
Inviato dal mio Le X527 utilizzando Tapatalk

---

Does MAAS360 app is able to check remotly what you install or not? I mean I have I want to install teamviewer on my work tablet and Im afraid that they will notice I installed it. I just want to be in trouble. Does maas360 send any signal to administrator what is installed what not?
Thank you for your help