Hello,
I wish to install (and use) the application DME Excitor (corporate emails) but it is detecting the root in some way.
I have a i9100 device with cm9.1 (latest stable one) & siyah kernel 5.0.1.
I've also made sure (using ExTweaks) that the kernel is not re-rooting the device every boot.
I've tried to remove the root using "Hide my root" / "ExTweaks" / "SuperSU" - and others that say they will hide the root - so far with no success!!!
Can you please suggest how to prevent DME from detecting my root?
I really don't mind unrooting the device - but please do not suggest me to return to stock!
Any help will be highly appreciated! :good::good::good:
bump
bump
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
florox said:
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
Click to expand...
Click to collapse
sorry - no success yet
In case you find any way, please let me know
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
bkraptor said:
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
Click to expand...
Click to collapse
Did you tried it with DME ?
By default, installing the SuperSU from the play store is in '/data' (you can later change that option in settings to be set on '/system')
Anyway, tried that, didn't worked.
Any help would be highly appreciated. :good:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
bkraptor said:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
Click to expand...
Click to collapse
Hi,
First of all thanks for trying to help.
There's no any Superuser.apk in /system/app/ (that's the first thing I've checked).
And I did made sure to uncheck the "Enable Superuser" option within SuperSU.
Still doesn't work.
If you don't mind me asking, could you please provide me with more details on your firmware?
Which rom are you using (is it Cyanogenmod)?
Special kernel?
CWM ?
Any details would help.
And once again, thanks!
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
bkraptor said:
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
Click to expand...
Click to collapse
Thanks for the info.
I was afraid that you would note you're using a rooted stock firmware.
The thing is that by going back to stock rom, there's no need to root it and then unroot it to use the DME (simply use the stock firmware unrooted).
The first post on this thread was a question on how to use the DME on different rom than the stock one (such as CM).
After that being said, I would like to thank you for trying, but this didn't help me, since I wish to use the Cyanogenmod rom and DME together.
If you still have any suggestions on how to use the DME with a non-stock rom, I would be more than happy to hear.
I don't see how running CM is any different than running official. You should check that after disabling Superuser from within SuperSU that there is no "su" binary anywhere within the directories in the PATH variable (i.e. /system/bin or /system/xbin).
Is dual booting a stock/cm setup possible, and would that serve as a "workaround"?
Edit...just thought....even if possible, the dual boot kernel would probably give the game away....
Sent from my CM10 powered S2 via XDA Developers App
is there any solution at this point? I have cm installed and i want to use dme on my rooted phone...
finally!!! fully functional nexus 7 ))
meaning stock browser AND DME running
rooted with this method (from stock 4.2.2):
http://forum.xda-developers.com/showthread.php?t=2233852
installed stock browser from here:
https://play.google.com/store/apps/details?id=de.mkrtchyan.aospinstaller
SuperSU settings (many thanks to bkraptor):
http://forum.xda-developers.com/showpost.php?p=42009031&postcount=6
Can someone please let me know how to install superSU in /data. As If I instal UPDATE-SuperSU-v1.51.zip by using PhilZ-cwm6. It is installed by default in /system.
If I install it using Playstore it does the same got installed in /system. and further conflicts with SU installed by PhilZ-cwm6.
Will appreciate any suitable advice
If possible, I'd like to remove root from my stock image, leaving the recovery, so I can use it for a business app that doesn't operate with root. Can this be done?
crackface said:
If possible, I'd like to remove root from my stock image, leaving the recovery, so I can use it for a business app that doesn't operate with root. Can this be done?
Click to expand...
Click to collapse
Yes. Open SuperSU, and use the "Settings", "Full unroot" option. That'll remove SU and allow your app to run if it only looks if you're rooted.
Some applications, like "Good", don't just check for rooted device - they also check for evidence that the device is rooted. I fight this battle all the time on my Galaxy Tab - it's rooted, kind of, but Good can't tell.. but I can't use the root permissions without disabling Good, rebooting, then enabling root.
You've got to remove any evidence of busybox having been installed as well as any evidence of any rooting programs for Good to be happy.
See the Saferoot thread for an unrooting script which may work for you.
I have an application (required for work) which will not run on any rooted ROM. In order to remove bloatware (on ICS) I rooted the ROM, deleted bloatware and then unrooted
Im now looking at installing Kit-Kat. However, there are no original ROMs of Kit-Kat for ST15i (unlike ICS). The application not only checks for SU, BUsy box etc but also checks to see if the system is using a non original ROM
Is there anyway of changing signature of the ROM so that it is not detected as an AOSP version? I will also need to completely unroot the ROM for the application to work
P.S. I have already tried Rootcloak plus etc - no good. The ROM MUST be unrooted for the application to work. The app checks for following
SU, Superuser, AOSP ROM, Busybox and various other binaries associated with rooted roms, build.prop
there is xposed module to "hide" root for apps
godlesplay said:
there is xposed module to "hide" root for apps
Click to expand...
Click to collapse
Hi
Yes - tried that - it doesn't work for this app
Hello. I have the non root app. I see that if i want to check the option "greenifying system apps" i have to purchase the donation package.
The question is: do i need also root ? Thanks
No, you do not need root. That is the beauty of the app now. But the hibernated system apps may wake up sometimes. With root, once hibernated, they stay that way.
gxg10 said:
Hello. I have the non root app. I see that if i want to check the option "greenifying system apps" i have to purchase the donation package.
The question is: do i need also root ? Thanks
Click to expand...
Click to collapse
After I tried to understand the text under the "Greenifying system apps" I found out that, no, you would not require root. However, the process might not be smooth as if you installed Xposed and use boost mode. But still, you can hibernate system apps.
So I have seen the 6.0 and the CM permission system before.
Both have a toggle that allows setting permissions for preinstalled system apps aswell.
Is that possible in OxygenOS too?
(The whole reason for me to get a phone with a permission system was to be able to restrain all that Google Play stuff...)
NotieB said:
So I have seen the 6.0 and the CM permission system before.
Both have a toggle that allows setting permissions for preinstalled system apps aswell.
Is that possible in OxygenOS too?
(The whole reason for me to get a phone with a permission system was to be able to restrain all that Google Play stuff...)
Click to expand...
Click to collapse
CM's privacy guard can do exactly that, even with system apps. OOS's permissions can only limit non-system apps, so you'd need to remove all the Google Play apps as system apps and re-install as user apps (or convert them to user apps with Titanium Backup). However, this would need root. Not sure if you wanted a non-root option, but I can't think of any that would not require root.
MrKhozam said:
However, this would need root. Not sure if you wanted a non-root option, but I can't think of any that would not require root.
Click to expand...
Click to collapse
I was indeed wondering about a non root option, i.e. if there is a toggle i just missed.
So I guess I'll wait for the 6.0 update as the native android permission system works for system apps aswell, and they'd be stupid to replace it.