Related
I have to install citrix mobile connect to connect to the Exchange server at work, and citrix will not run on a rooted device
is there a way to overcome this or perhaps install a different app to receive exchange sync?
(for example will "hide root" work here)?
You can try voodoo rootkeeper that can perform a temporary unroot.
I will start with this thread and see if blocks the exchange sync, http://forum.xda-developers.com/showthread.php?t=1957273
I hope rooting doenst erase my data, as I am already working for a week with the device.
Anyway, I will run titnium backup before I start
ofird said:
I will start with this thread and see if blocks the exchange sync, http://forum.xda-developers.com/showthread.php?t=1957273
I hope rooting doenst erase my data, as I am already working for a week with the device.
Anyway, I will run titnium backup before I start
Click to expand...
Click to collapse
titanium backup needs root
just found that out
So - any other ROM back up program out there that doesnt neet root?
or perhaps i dont have to worry about losing data with CFAuto root?
ofird said:
just found that out
So - any other ROM back up program out there that doesnt neet root?
or perhaps i dont have to worry about losing data with CFAuto root?
Click to expand...
Click to collapse
rooting does not delete data, whereas you never can be sure 100% that it will go as planned. Nevertheless there is not app that can backup 100% of your rom without root.
so i will take my chances :0)
Ke sera sera
done, went smooth
although I am running "root checker" and it says system running slow and doenst return results
is there a specific app i should install now ? "super SU" or something?
ofird said:
done, went smooth
although I am running "root checker" and it says system running slow and doenst return results
is there a specific app i should install now ? "super SU" or something?
Click to expand...
Click to collapse
If you rooted it correctly SuperSU or SuperUser should already be installed. Did you have any progress getting Citrix to work while rooted? Im in the same situation and I've only been able to get it to work briefly with Touchwiz based ROMs with SuperSU. All others give me a " cannot connect due to a security policy" error - even after disabling root and trying to re-enroll. Its a beast...
Yes I have
I used hide my root throughout all the process.
I check with root checker to validate it's indeed hidden.
And I keep running hide my root at all times
ofird said:
Yes I have
I used hide my root throughout all the process.
I check with root checker to validate it's indeed hidden.
And I keep running hide my root at all times
Click to expand...
Click to collapse
Nice! I'm gonna give that a go then. Thanks
tscalia2 said:
Nice! I'm gonna give that a go then. Thanks
Click to expand...
Click to collapse
I have had to do the same...and all seems to work. But I had to also install two more apps enforced by policy; Lookout, and Touchdown.
Any ideas on what these do?
Touchdown is a great app for synching all your mails, notes and Exchange data.
I use it
I don't know what lookout is for
Hi,
I really like the slim bean rom.
However, I would like to unroot my phone.
Can I unroot my phone and still keep slim bean?
If yes, how?
Thanks for your help!
in the superuser app settings
Thanks Glebun!
However, it is already set to disabled.
For example my Good for Enterprise app still fails the compliance check.
So I would like to know if I can completely unroot my phone while still keeping Slim Bean.
what superuser app are you using? SuperSU allows for a full unroot
Its built into settings
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Its built into settings
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Exactly.
I can't find a superuser.apk on my phone.
It's not visible in as an app anywhere.
There is no option to uninstall if I open superuser via the settigns - superuser menu..
I've searched the internet to no end and I'm getting more and more confused.
Hope you can help.
get supersu from play then
Glebun said:
get supersu from play then
Click to expand...
Click to collapse
I did install supersu, but again installing it and then uninstalling it still leaves me with the "# Superuser" setting in the settings menu and it's still rooted.
By the way: I just installed another superuser app (I think it is from the CM mod) and I get a notice saying "Normal, the 'su' file needs to be edited. Choose an installation method. 'Via recovery' is recommended for HTC-devices.
So no succes there.
installing and the uninstalling it will have no effect. read my post - supersu has a setting for a full unroot, use it
Glebun said:
installing and the uninstalling it will have no effect. read my post - supersu has a setting for a full unroot, use it
Click to expand...
Click to collapse
root consists of 2 elements
1) The app (or settings) which is a gateway to root if you like, but not actually root itself
2) The SU binary /system/bin/su. This is what actually gives root. The above just allows or denies root access. Using one of the superuser apps, you should be able to unroot, removing this. The settings menu will always remain but means nothing.
You may just be able to use a file manager with root permissions to delete the binary.
that is what I meant
rootSU said:
root consists of 2 elements
1) The app (or settings) which is a gateway to root if you like, but not actually root itself
2) The SU binary /system/bin/su. This is what actually gives root. The above just allows or denies root access. Using one of the superuser apps, you should be able to unroot, removing this. The settings menu will always remain but means nothing.
You may just be able to use a file manager with root permissions to delete the binary.
Click to expand...
Click to collapse
Guys: you're the best!
Turns out that I had to reboot (duh) before the change took effect.
Now I have slimbean 4.2.2 unrooted and can make use of Good for Enterprise.
Thanks a bunch!
A small summary:
1. Install SuperSU.
2. Use the "Full unroot" function of SuperSU.
3. Reboot :laugh:
Glebun said:
that is what I meant
Click to expand...
Click to collapse
Sorry, I didn't mean to quote your post.
I've got an app that is listed as 'disabled' in application manager list, but when I select it to try and re-enable the button is grayed out and says 'disable' on it as if it was never disabled to start with.
How do I un-stick this app? TIA
What app is it?
You should be able to use any app or file manager to uninstall it.
Do you have root access?
440bro said:
What app is it?
You should be able to use any app or file manager to uninstall it.
Do you have root access?
Click to expand...
Click to collapse
The basic 'email' app. I had originally disabled that and 'exchange services' way back at the beginning (root required) because I wasn't using anything but gmail and was paring down on apps as much as possible. Now I have a reason to use it, and while I was able to enable 'exchange services' again, the other one just seems stuck. After the update to ICS and then JB I never installed root, and with the OTA updates it seems this particular app has gotten into a bit of a mangled state.
tigerknight said:
The basic 'email' app. I had originally disabled that and 'exchange services' way back at the beginning (root required) because I wasn't using anything but gmail and was paring down on apps as much as possible. Now I have a reason to use it, and while I was able to enable 'exchange services' again, the other one just seems stuck. After the update to ICS and then JB I never installed root, and with the OTA updates it seems this particular app has gotten into a bit of a mangled state.
Click to expand...
Click to collapse
Well you can try installing them again. I'm going to assume you're on the latest 4.1.2 version. So here is the email apk and here is the exchange apk just in case you want to reinstall both.
Or you could gain root access and use an app to unfreeze them that way.
To root the stock 4.1.2 rom
1. Use Odin 1.85 in Admin Mode for Windows users.
2. Install TWRP 2.5 via PDA settings.
3. Reboot phone into Recovery.
4. Install SuperSU via the Zip.
5. Reboot phone and viola You're rooted!. SuperSU is there and works.
440bro said:
Well you can try installing them again. I'm going to assume you're on the latest 4.1.2 version. So here is the email apk and here is the exchange apk just in case you want to reinstall both.
Or you could gain root access and use an app to unfreeze them that way.
To root the stock 4.1.2 rom
1. Use Odin 1.85 in Admin Mode for Windows users.
2. Install TWRP 2.5 via PDA settings.
3. Reboot phone into Recovery.
4. Install SuperSU via the Zip.
5. Reboot phone and viola You're rooted!. SuperSU is there and works.
Click to expand...
Click to collapse
Grr. I downloaded the email apk and tried to run it, and it just failed with 'application not installed'. Apparently I buggered myself up good - I'll have to go the root option, any tips/tricks to keep in mind before I do that?
I was wondering if anyone has installed Viper4Android on this device. I had it on my previous phone and it worked flawlessly; all my music sounded amazing.
But ever since we achieved root, I couldn't successfully install it. It keeps telling me Busybox is broken or not installed, and therefore won't let me install the audio drivers.
Can anyone try installing it, if they can? My favorite band just released a new album and I'd love to hear it with a good equalizer.
Sent from my MT2L03 using XDA Free mobile app
I have just installed it successfully and it works perfectly on MT2-L05 4.4.2
I have busybox ( stericson ) installed on my phone. Maybe you can delete whatever version of busybox that you have installed and try to install stericson Busybox from playstore?
Good Luck !
4L0M said:
I have just installed it successfully and it works perfectly on MT2-L05 4.4.2
I have busybox ( stericson ) installed on my phone. Maybe you can delete whatever version of busybox that you have installed and try to install stericson Busybox from playstore?
Good Luck !
Click to expand...
Click to collapse
I've tried many Busybox versions, including stericson and it still won't work. Maybe the OS has something to do with it, if it works on KitKat and not Jelly Bean?
I failed to as well. I even tried the zip install.
Sent from my MT2L03 using Tapatalk
I tried everything today: manual Viper installation, different Busybox versions, etc., still doesn't work.
Maybe the KitKat update will make it possible. That is, if we ever get a KitKat update... I may not use a Huawei phone again if we don't get updates. There's already been so many issues (for me at least) with Emotion being so extensively modified from regular Android. And we don't have any developers at all. I'll probably go Nexus next time.
ScoobSTi said:
I was wondering if anyone has installed Viper4Android on this device. I had it on my previous phone and it worked flawlessly; all my music sounded amazing.
But ever since we achieved root, I couldn't successfully install it. It keeps telling me Busybox is broken or not installed, and therefore won't let me install the audio drivers.
Can anyone try installing it, if they can? My favorite band just released a new album and I'd love to hear it with a good equalizer.
Sent from my MT2L03 using XDA Free mobile app
Click to expand...
Click to collapse
I am using it now flawlessly. The driver cannot be installed automatically but you can manage to use the flashable zip file to install it manually.
First uninstall the app and backup your build.prop.
Download the flashable zip file here.
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Reboot to your TWRP and flash the zip file and reboot. The zip file would install the apk file in /system/priv-app which is actually not recognized by the Huawei system. So please manually move the apk file to /system/app or /data/app , or just install it and remove whatever file left in /system/priv-app
And then start the app you should be able to install the driver. Actually the driver has been installed after you flashed the zip file.
Since it will modify your build.prop, so please make a backup. And in my case it broke my build.prop so I had to modify the file manually. There is an example in the link above. Please append the followings at the end of your build.prop.
Code:
##Viper4android
lpa.decode=false
tunnel.decode=false
lpa.use-stagefright=false
lpa.releaselock=false
OK. Reboot and you are all set.
Again, if you encounter soft brick and the system ui fails to appear, high chances that V4a broke or deleted your build.prop. Make sure you make a back up of that file first.
dbmj said:
I am using it now flawlessly. The driver cannot be installed automatically but you can try to use the flashable zip file to install it manually...
[snip]
Click to expand...
Click to collapse
Do you have this working on the US version MT2L03? And can V4A be used to boost the handset (earpiece) volume?
Thanks,
arcadesdude said:
Do you have this working on the US version MT2L03? And can V4A be used to boost the handset (earpiece) volume?
Thanks,
Click to expand...
Click to collapse
Yes and yes. I am using the US version MT2L03 and it can be used to boost my earbud volume.
Sweet, I thought you had the non-US version at first. I'll install TWRP soon, try this and report back!
I managed to install it...but I dont know which settings will let me do this.
I want to increase the volume of the phone when using it as a phone held up to my ear without affecting battery drain. There are too many options. The FAQ links to a site to explain the settings but that site is down. Help?
Update: never mind I uninstalled viper4android (reverted to backup actually). It barely increased the volume but it would crash my phone when connecting to Bluetooth despite it being disabled for bluetooth.
Works great but shuts down when the screen sleeps. No option in the apps list to keep it running.
MikeyLee said:
Works great but shuts down when the screen sleeps. No option in the apps list to keep it running.
Click to expand...
Click to collapse
There was the option to mark it as a protected app for me but that's because i installed it to /data/app by copying it there. Did you install it to /system/app maybe?
I found it too buggy to keep though so I dont use it now.
Sent from my MT2L03 using Tapatalk
arcadesdude said:
There was the option to mark it as a protected app for me but that's because i installed it to /data/app by copying it there. Did you install it to /system/app maybe?
I found it too buggy to keep though so I dont use it now.
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
No I pushed it to data/app. No protect option for me
Aw, I forgot to install TWRP and try Viper over the weekend. I don't want to risk messing up my phone during the week, leaving me phone-less!
MikeyLee said:
Works great but shuts down when the screen sleeps. No option in the apps list to keep it running.
Click to expand...
Click to collapse
In the Viper settings, you can set "Show notification", so the system won't kill the app when the screen is off. If that's not enough, what I did on my previous phone was use this app to protect Viper. Install that, go to "Tasks", tap on Viper, and select "Exclude" on the bottom left.
Root the device (search how to root the device Huwei Mate 2)
Change to permissive mode with “SELinux Mode Changer” apk from xda or search.
Enable developer options (tapping the Settings->Builld Number several times will enable the developer options, by default it is hidden from the user) and uncheck Use Nuplayer option.
Install the viper4android (get the latest untouched viper4android from original viper4android thread).
optional making viper4andriod as system app(refer how to make system app, if you want to make viper4andorid as system app)
set following values on the “build.prop” using the (Build Prop Editor, search for apk)
##Viper4android
lpa.decode=false
tunnel.decode=false
lpa.use-stagefright=false
lpa.releaselock=false
Run following commands with “Terminal Emulator” apk (search playstore or internet)
>>su
>>/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
Open the viper4android and install the drivers.
Reboot the device
After reboot Launch the viper4android and check the driver status then you will see driver status normal.
feel free to play with compatible mode option or other options to suit your needs.
Thanks, guy with one post who revived a year old thread. If anyone tries this let us know how you made out, I guess.
kimtyson said:
Thanks, guy with one post who revived a year old thread. If anyone tries this let us know how you made out, I guess.
Click to expand...
Click to collapse
I've been using V4A on stock ROMS and on CM ROMS with no issues at all.
Newest stable version works but doesn't ask for root privilege. Rooted using Chainfire's supersu.
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now
Best of luck
Sent from my Sony Xperia SP using XDA Labs
Which settings require root? I've toggled all the settings and none of them made it ask for root.
olliebean said:
Which settings require root? I've toggled all the settings and none of them made it ask for root.
Click to expand...
Click to collapse
For me it asked for root when I changed settings under "wake up tracking and cut off".
If nothing happens to you reboot your phone and try again, you could also check to see if there is any denied requests of greenery in super su app and manually grant it.
Sent from my Sony Xperia SP using XDA Labs
ghst7 said:
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now
Best of luck
Click to expand...
Click to collapse
Oh it works just fine. It's just not showing up in Supersu as having root access.
I have the same problem.
After I updated from the market today I can't get greenify to properly request root access.
When I run it I tell it I'll rooted, see it saying it's requesting root access but supersu doesn't prompt then says it can't get root. Same results with rebooting.
In supersu there are no request prompts from greenify. I deleted the greenify access to see if that would get it to reprompt but it still says can't get root and supersu shows no requests in logs.
Other apps still work fine in supersu.
Edit --
Interesting, I disabled the module in xposed and when it prompts for root supersu pops right up. So I gave it access that way but logs show that once the module is reenabled it never asks for root.
Weird
Can't get root privilege
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
rockah said:
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
Click to expand...
Click to collapse
Got mine to work by deselecting Greenify module in Xposed and rebooting. Started Greenify app and it said to either to activate the Xposed module or select non-root mode. I clicked on Greenify settings and tried to change Xposed settings and a popup window asked if I wanted to activate Xposed module. I selected yes, Xposed started, I selected Greenify module and rebooted. During the bootup process, Greenify asked for root permissions.
A similar process worked for me: deactivated the Xposed module, rebooted, started the Greenify app, then I went into the Greenify settings and turned on the enhanced wake up tracker, which caused Greenify to request root. Granted permission, then reactivated the Xposed module and rebooted again. Checked in SuperSU that Greenify had permissions, then I just had to re-enable the Xposed based features in the Greenify settings.
Having done that, however, I see from the SuperSU logs that Greenify isn't actually requesting any root permissions since I re-enabled the Xposed module. I suspect the new version is using Xposed for all its root access and no longer needs root permissions for the app in Boost (Xposed) mode.
Lots of guessing here.
I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
dreinulldrei said:
Lots of guessing here.
I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
Click to expand...
Click to collapse
Read prior posts for further guidance. Seems others have got it to work. I had zero/nada/no problems on latest betas w/Xposed and SuperSU 2.76. YMMV.
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
dreinulldrei said:
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
Click to expand...
Click to collapse
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).
BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.
Wonder if I should drop back to v2.76 and how to even do that without losing root?
Davey126 said:
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).
BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
Click to expand...
Click to collapse
---------- Post added at 03:55 PM ---------- Previous post was at 03:43 PM ----------
This page has a link to the SuperSU v2.76 zip on ChainFire's site, which can be flashed with TWRP, etc depending on your phone.
https://www.progeeksblog.com/download-supersu-for-android/
I have not tried to flash it myself.
divineBliss said:
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.
Wonder if I should drop back to v2.76 and how to even do that without losing root?
Click to expand...
Click to collapse
If life is good don't change anything! I'm not out to skewer SuperSU v2.78; the problems I and a few others experienced are likely outliers with various contributing factors. That said, SuperSU 2.76 has been rock solid on my devices as have most of ChainFire's previous releases. Sticking with what works for now.
rockah said:
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
Click to expand...
Click to collapse
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
If you moved Greenify apk to
"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
craigevil said:
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
Click to expand...
Click to collapse
divineBliss said:
If you moved Greenify apk to
"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
Click to expand...
Click to collapse
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
I don't think you can do anything to the SuperSU configuration to make it so apps in priv-app have to ask for SU permission. I have other apps in there and have never seen them ask and they are not in SuperSU log either.
I moved my Greenify apk into priv-app because it wasn't clear to me that there was nothing to gain by doing that as I already had Xposed installed and working. Have since moved it back to original folder in /data/app/.
Davey126 said:
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
Click to expand...
Click to collapse
- Android 6.0.1
- SuperSU 2.78 (systemless root)
- Xposed
- latest Greenify Beta from PlayStore (in Root+Boost mode)
- NOT installed as system app or anything.
Same problem here -- Greenify never asks for root, is not listed in SuperSU logs. Greenify initially had root access iirc, but one of the updates from PlayStore removed it.
Nevertheless Greenify seems to be working fine though.
EDIT: All other root apps on my phone (OnePlus 2, stock OxygenOS 3.1) don't have any issues with root access.
Sent from my OnePlus 2 using Tapatalk