Not sure why, but I'd like to share with the community that I have Android Pay working on my Nexus 6p, running stock Android version 6.01, build MHC19Q, with beta 2.71 of SuperSU by Chainfire.
I flashed the Factory image using fastboot, flashed TWRP 3.01 via fastboot, and then flashed SuperSU within TWRP recovery using the Beta 2.71 ZIP file from Chainfire
During the setup of Android, I added my Google Account, but skipped the passcode and nexus imprint setup. Before completing the setup process, I restarted back into recovery, and wiped the internal storage. Once I did that, I copied the SuperSU zip back on the device storage via my USB, and installed it again once more. I restarted my Nexus, followed the entire setup and created a PIN only, NOT the nexus imprint. Once I was into the Google Now Launcher, I opened Android Pay...added my payment cards without any error messages at all. I confirmed root access is available, and then set up my Nexus imprint. I then confirmed at POS terminal that Android Pay does in fact work.
Not sure if this matters, but I have not yet enable DEV settings access within Android as of this writing. Also, I have not encrypted the device, and did not elect to use a pin when starting the phone.
Can anyone else confirm this works for them?
Have u tried buying anything with it yet?
Sent from my Nexus 6P using Tapatalk
---------- Post added at 07:47 PM ---------- Previous post was at 07:38 PM ----------
And u right it lets u setup now while rooted!
Sent from my Nexus 6P using Tapatalk
systemless root I'm guessing? have you tried with modded system?
Systemless mode.
Haven't tried any other mod. Yes, I used the tap & pay at the local bodega.
Can you check your supersu settings and look towards the bottom it should tell you if it's a system app or if it's running systemless
Sent from my Nexus 6P using Tapatalk
pretty sure it's systemless. I mean, no system level root has made it to Android pay. but I'm just speculating
screenshot
I'll post a screenshot asap, but I did check and SU is installed system-less mode.
Also....
I use the app Secure Settings, and it does report that Root is not available (WITHIN the Secure Settings application) however, other apps, such as Adaway, can request, and are able to be granted, root access, with no apparent issues.
Here....
Ahh so it was systemless no surprise there but good to know.
Sent from my Nexus 6P using Tapatalk
You can do this by chmod-ing the correct folder. See https://www.reddit.com/r/Nexus6P/comments/4coc1e/easiest_way_to_systemless_root_while_keeping/
speedinfreaky84 said:
Not sure why, but I'd like to share with the community that I have Android Pay working on my Nexus 6p, running stock Android version 6.01, build MHC19Q, with beta 2.71 of SuperSU by Chainfire.
I flashed the Factory image using fastboot, flashed TWRP 3.01 via fastboot, and then flashed SuperSU within TWRP recovery using the Beta 2.71 ZIP file from Chainfire
During the setup of Android, I added my Google Account, but skipped the passcode and nexus imprint setup. Before completing the setup process, I restarted back into recovery, and wiped the internal storage. Once I did that, I copied the SuperSU zip back on the device storage via my USB, and installed it again once more. I restarted my Nexus, followed the entire setup and created a PIN only, NOT the nexus imprint. Once I was into the Google Now Launcher, I opened Android Pay...added my payment cards without any error messages at all. I confirmed root access is available, and then set up my Nexus imprint. I then confirmed at POS terminal that Android Pay does in fact work.
Not sure if this matters, but I have not yet enable DEV settings access within Android as of this writing. Also, I have not encrypted the device, and did not elect to use a pin when starting the phone.
Can anyone else confirm this works for them?
Click to expand...
Click to collapse
Why the extra steps, why not just flash TWRP, Flash SU as Systemless, then reboot and use Android Pay? That's how I was able to do it. And I didn't need the extra steps of deleting xbin_bind or chmoding the folder /su/bin (I am guessing SU did that for me.)
Way too many steps.
CFAutoRoot updated to 3.71 beta. 3.71 won't install xbin_bind. su/bin already chmodded to 751 in 3.71.
Don't even need TWRP. CFAutoRoot on factory stock and you're good to go with Android Pay.
You're probably right, I know a lot less about the process than you, so I wanted to make sure I provided as much information about what I did during setup that could replicate my success....since I wasn't really trying to get it to work since it didn't work up until now on a rooted device.
But cool man I'm glad it can be done so much easier.
zeezz said:
You can do this by chmod-ing the correct folder. See https://www.reddit.com/r/Nexus6P/comments/4coc1e/easiest_way_to_systemless_root_while_keeping/
Click to expand...
Click to collapse
No need to do that anymore. The supersu setup script has been doing that for the last 4 versions (starting at v2.68).
Google Wallet?
Didn't Google Wallet work on any rooted or ROM system? Android Pay is really annoying when it comes to this regard.
how do you get the 2.71 to install as systemless?
i downloaded the 2.71 from this Beta thread
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
and it wont install as system less. is there something that has to be done or another 2.71 zip that is converted to systemless?
TimesNeverWasted said:
Didn't Google Wallet work on any rooted or ROM system? Android Pay is really annoying when it comes to this regard.
Click to expand...
Click to collapse
Google Wallet did work, but is being phased out and replaced with Android Pay.
nextelbuddy said:
how do you get the 2.71 to install as systemless?
i downloaded the 2.71 from this Beta thread
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
and it wont install as system less. is there something that has to be done or another 2.71 zip that is converted to systemless?
Click to expand...
Click to collapse
It should install in systemless mode by default, are you 100% stock? With not modifed boot.img?
Sent from my Nexus 6P using Tapatalk
MrKaon said:
It should install in systemless mode by default, are you 100% stock? With not modifed boot.img?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
i was able to get it to work with help from another thread.
if have never been rooted before with systemless, then people that install 2.71 will get installed as SYSTEM by default unless you came from one of the original systemless ZIp files such as 2.56 which sets some parameters first that the new ones do not do by default.
I had to:
boot into TWRP and go into TERMINAL and then type
echo SYSTEMLESS=true>>/data/.supersu
Then
echo BINDSYSTEMXBIN=false>>/data/.supersu
Once that is complete then flash latest BETA SuperSU such as 2.71
that worked for me.
Related
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.
Hello,
I have a Samsung Galaxy S6 Edge SM-G925W8 and had SuperSU root access and XPosed Framework installed. I am now attempting to remove all of it so that I can pass Google's safetynet helper test. I have tried numerous things, but the safetynet result is always:
SafetyNet Request: Success
Response Validation: Success
CTS Profile Match: False
I first attempted to remove Root by clicking "Completely remove root" within SuperSU. After doing this, Response Validation was false, which, after doing some research, I learned was caused by XPosed Framework. I then boot into TWRP recovery and flash the Xposed uninstaller. This causes my phone to boot loop, forcing me to restore a NAND backup to before I removed anything. I then try to flash the XPosed Uninstaller BEFORE removing root access and it runs successfully. After this, I use SuperSU to completely remove all root, which also runs successfully then give the phone a reboot removing the app entirely. This is when I receive the SafetyNet Helper response above stating CTS Profile match is false. I'm not sure how to fix this error.
Any suggestions would be very appreciated! Thank you
Edit: I have no idea why this thread appeared twice...sorry I can't seem to delete one of them
Er.. Any ideas?
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
vgplayer54 said:
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
Click to expand...
Click to collapse
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hello, I attempted to use ES File Explorer to search both the system/bin directory and the system/xbin directories. system/bin does not have the "busybox" or "su" files in them, so I assume they were removed when I uninstalled SuperSU. /system/xbin however does have these two files, but I am unable to delete them. I get the error "Cannot delete file". I'm guessing this is because I've already unrooted?
I then opened the terminal in my TWRP Recovery, however when changing directories into the system folder, the terminal shows that it is empty. when using ls -la, only two files are there, both called root and neither can be opened. rm -r /system/xbin/busybox does nothing either, it claims there's no such directory. Any suggestions? or just wipe?
Until the latest release of Microsofts Intune Company Portal (5.0.3503.0) for android exposed module rootcloak has worked to hide that the phone is root'ed but since a week back or something like that the company portal is detecting that my CM13 phone is rooted, so I'm looked out from syncing mails.
Anyone here having the same issue and have a solution for this?
Have you tried Su hide by chainfire
Sent from my iPhone 4s using Tapatalk I also own a g900v
[email protected] said:
Have you tried Su hide by chainfire
Click to expand...
Click to collapse
yes I have, SuHide 0.55, no success
Sorry for your troubles [emoji53]
Sent from my iPhone 4s using Tapatalk I also own a g900v
---------- Post added at 04:02 PM ---------- Previous post was at 03:56 PM ----------
Have you tried Uninstalling xposed and just using Su hide I've heard some apps can detect xposed framework
Sent from my iPhone 4s using Tapatalk I also own a g900v
Thanks for the tips! I tryied right away but still no luck!
ljon said:
Thanks for the tips! I tryied right away but still no luck!
Click to expand...
Click to collapse
is it possible to install a previous version of Intune where it still works, and how to get this version?
Try to find the apk on apkmirror or apkpure and install it manually if you find a significantly earlier version uninstallb the version on your device and install the old apk
[email protected] said:
Try to find the apk on apkmirror or apkpure and install it manually if you find a significantly earlier version uninstallb the version on your device and install the old apk
Click to expand...
Click to collapse
i found several older versions that do install but they obviously have an inbuilt check for that so they dont work and just tell me i have to upgrade. as a result it seems its currently not possible to use microsoft company tools on a rooted phone. An unrooted phone is more or less useless.
Are you using systemless supersu most recent version is 2.79 sr3
[email protected] said:
Are you using systemless supersu most recent version is 2.79 sr3
Click to expand...
Click to collapse
The info in the SuperSU app says 2.79 and I installed it systemless on my elephone P9000 stock rom. Also have xposed framework running. I tried a lot of tools but none works.
It does not seem to use safenet check, because I can pass the safenet check by using magisk, but still fails on app's compliance check, saying my phone is rooted.
Damn!
You could always turn off root in developer options and reboot then sync emaills then turn back on root in developer options
Hi,
I'm facing the same issue on my S7 Edge with a Superman Rom on Nougat. I have Magisk 12, Safetynet check Ok but Company Portal still detects root. May be it's because the app is registered as a Device Administrator. I guess with these permissions it can check root differently.
I found an Xposed module for that specific issue but Xposed on Nougat is still unavailable
Do you only have magisk super user installed or do you also have SuperSU installed if you have SuperSU installed remove it
I have just Magisk Super User installed. I never installed SuperSU. The Xposed module that I was talking about is "Security Bypass for Company Portal".
I think we need a Magisk Module doing the same thing if possible.
I recently installed outlook and had the same problem running MagiskSU. Safetynet passes, and Magisk hide was enabled, but no luck. I used Tasker to get around the root check with the with the following tasks:
Launch App (Outlook)
Run Shell command:
su
chmod 0754 /data/magisk
sleep 25
chmod 0755 /data/magisk
This launches the outlook app and changes the permissions of the magisk folder for 25 seconds so that when it does the root check after I input my pin everything checks out. After 25 seconds it restores the permissions to what they were. I exported this as an app (long hold on task, click menu in upper right and export as app) and it seems to work like a charm.
I've tried your solution, but it doesn't work for me. I still have the same message showing up ?
Nakah95 said:
I've tried your solution, but it doesn't work for me. I still have the same message showing up ?
Click to expand...
Click to collapse
It's still one of the strongest root detection apps I know, was there once an xposed framework app that allowed a rooted device to access Portal?
dizzybrow said:
I recently installed outlook and had the same problem running MagiskSU. Safetynet passes, and Magisk hide was enabled, but no luck. I used Tasker to get around the root check with the with the following tasks:
Launch App (Outlook)
Run Shell command:
su
chmod 0754 /data/magisk
sleep 25
chmod 0755 /data/magisk
This launches the outlook app and changes the permissions of the magisk folder for 25 seconds so that when it does the root check after I input my pin everything checks out. After 25 seconds it restores the permissions to what they were. I exported this as an app (long hold on task, click menu in upper right and export as app) and it seems to work like a charm.
Click to expand...
Click to collapse
For now only this method works... Thank you...
kpmohamedhussain said:
For now only this method works... Thank you...
Click to expand...
Click to collapse
Hi, can I ask you to help me get this to work? I am not sure if I am implementing it right..I installed tasker but not sure if I am setting it up correctly cause when I launch the task I still get the same root detection error. I use a galaxy s7 edge with superman rom 2.8 Nougat, magisk 15.3 and xposed.
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
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
AP756 said:
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
Click to expand...
Click to collapse
Excellent. You use XDA guide to Root and install TWRP? You don't have brick?
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Click to expand...
Click to collapse
Thanks to shared. You have sucess to make root?
PedroArmindo said:
Thanks to shared. You have sucess to make root?
Click to expand...
Click to collapse
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Vikindor said:
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Click to expand...
Click to collapse
Could you test if the Titanium Backup app works?
grinna said:
Could you test if the Titanium Backup app works?
Click to expand...
Click to collapse
Checked. Yep, it works.
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3. ...
Click to expand...
Click to collapse
lunger said:
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Click to expand...
Click to collapse
Hi. Sorry, haven't seen this message.
TWRP: https://twrp.me/
Magisk can be found here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (or in app stores).
Hi,
Can anyone help me with my phone ZE554kL on how to root this or link me to a guide? Thanks in advance.
"Continue reading only if interested what happen."
I've never done this before and I just want to do root because my internal storage was wiped out when I was backing up all my files to PC. Windows explorer stops responding while transferring files then after the not responding issue, my internal storage is empty and when I checked my phone all the files is gone (photos, videos, PDFs).
I tried different android recovery software in windows and everytime i do a scan, i always ending up being asked by the software to root my phone so it can scan through to my internal storage.
Since my files was lost, i never touch my phone since then so nothing will be written on internal storage that could take away the chance of recovering my files.