Related
What are the correct steps to get android pay working with systemless root. I flashed in the following order: Pure nexus(supports pay), banks GAPPS, unSU, Systemless 2.66. Now, I heard i need to delete /su/xbin_bind but i can't find that.
I'm using 2.61 and androidpay has always worked fine. Never deleted any files after flashing that. I'd love to hear from anyone on 2.66 to know if it's working.
Edit: upgraded to 2.66 myself and it works fine so far. Will test androidpay soon, but I can't imagine why it wouldn't work...
smac7 said:
What are the correct steps to get android pay working with systemless root. I flashed in the following order: Pure nexus(supports pay), banks GAPPS, unSU, Systemless 2.66. Now, I heard i need to delete /su/xbin_bind but i can't find that.
Click to expand...
Click to collapse
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
dmudd said:
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I looked in /system and it's not there. I did however folder called ADDON.D that has Update_SuperSU within it. If i understand correctly, this would set-off the trigger to see system as modified. Is it possible the unSU zip i used (to try to unroot pure nexus) didn't work correctly?
So, apparently i was supposed to go to terminal and enter
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Click to expand...
Click to collapse
before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
smac7 said:
So, apparently i was supposed to go to terminal and enter before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
Click to expand...
Click to collapse
If you can add a card you pass the safetynet. You should be ready to use it. Just remember if you do anything else that you can still cause your phone to fail the safetynet and prevent payment even after your cards are added.
I've posted in a Nexus 6P thread, might be helpful though, but I had to disable SuperSU (not Full unroot) in order to get AndroidPay/CapOneWallet/Safetynet to work. And that's after editing build.prop, removing /su/xbin_bind, and installing EX Kernel, using Stock 6.0.1 and SuperSU 2.66 with systemless root.
The folder is located under /su not /system
dmudd said:
The folder is under /system. That's why Android pay won't work. You need to remove it from /system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
bdivs11 said:
The folder is located under /su not /system
Click to expand...
Click to collapse
You're right. I thought it was under /system but it is under /su
Sent from my Nexus 5X using Tapatalk
smac7 said:
So, apparently i was supposed to go to terminal and enter before flashing the systemless root. I flashed it an systemless root is working. Android pay allowed me to add my card with no further steps but i have not tested it yet. I still don't see /su/xbin_bind so maybe 2.66 removed that file? Can Android Pay allow you to add a card but fail when paying?
I installed a safetynet checker app and i passed through.
Click to expand...
Click to collapse
if you didn't perform these commands, then youll have to do full unroot and do it again putting them in BEFORE flashing 2.66
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
2x4 said:
if you didn't perform these commands, then youll have to do full unroot and do it again putting them in BEFORE flashing 2.66
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Click to expand...
Click to collapse
so I flashed 2.66 without doing these commands, thus breaking my android pay. how do i "fully unroot"? flash the un-SU.zip? I thought that was only for the system-based root methods, but perhaps I am wrong. I assume once I am unrooted I can just download any terminal emulator (do you recommend one?), enter the commands, then re-flash 2.66. Thanks for your help!
BTW I don't understand why 2.66 added these steps. 2.61 didn't require any terminal emulator commands and android pay worked fine! Perhaps the easiest solution would just be to flash 2.61 over 2.66?
Android Pay is not working on my 5x. I used the MSkip Toolkit's systemless root option, as well as used that Toolkit to unlock, de-encrypt, ect. That was done with I think a temp flash of TWRP so I keep stock recovery?
The only other thing I did to my phone was the build prop edit to enable tethering on Verizon which in the thread people said doesn't break their Android Pay.
Android Pay says cannot verify yadda yadda. I disabled SU in the app, rebooted and AP still doesn't work. Now when I try to re/enable SU fails installing/fails updating binary.
Anyone have any advice? Does some file need to be deleted or a fresh install?
greves1 said:
so I flashed 2.66 without doing these commands, thus breaking my android pay. how do i "fully unroot"? flash the un-SU.zip? I thought that was only for the system-based root methods, but perhaps I am wrong. I assume once I am unrooted I can just download any terminal emulator (do you recommend one?), enter the commands, then re-flash 2.66. Thanks for your help!
BTW I don't understand why 2.66 added these steps. 2.61 didn't require any terminal emulator commands and android pay worked fine! Perhaps the easiest solution would just be to flash 2.61 over 2.66?
Click to expand...
Click to collapse
Chainfire (SuperSU dev) is not developing systemless root to be compatible with Android Pay. That was never his aim. Anything he adds is for the purpose of not using /system for root. If you would like to read on changes to SuperSU, I suggest reading the brief changelogs or following his SuperSU beta thread to keep up to date on changes in SuperSu (systemless or otherwise).
Btw, you can flash whichever version of SuperSu you desire. If it is easier to get Android Pay working for you, cool.
I just use 2.61 and it just works with Android pay. No terminal commands or anything
stu5797 said:
I just use 2.61 and it just works with Android pay. No terminal commands or anything
Click to expand...
Click to collapse
Same here. I can't see any reason to "upgrade" since the later versions seem to require additional steps, and for the user I don't seem to get any added value from the later versions.
greves1 said:
I'm using 2.61 and androidpay has always worked fine. Never deleted any files after flashing that. I'd love to hear from anyone on 2.66 to know if it's working.
Edit: upgraded to 2.66 myself and it works fine so far. Will test androidpay soon, but I can't imagine why it wouldn't work...
Click to expand...
Click to collapse
What steps did you take in order to upgrade? Just flash the zip? Do you still need to run the terminal commands before the flash?
tallgrasshawk said:
What steps did you take in order to upgrade? Just flash the zip? Do you still need to run the terminal commands before the flash?
Click to expand...
Click to collapse
Don't do this upgrade if you want androidpay to work. I thought it was working at first, but later realized it wouldn't work at the store. You can just flash the zip to upgrade, but this seems to break the android pay. It would be interesting to try it the way you suggest, with running the terminal commands before flashing. Perhaps this would preserve androidpay! Good luck, post back if you find that works.
greves1 said:
Don't do this upgrade if you want androidpay to work. I thought it was working at first, but later realized it wouldn't work at the store. You can just flash the zip to upgrade, but this seems to break the android pay. It would be interesting to try it the way you suggest, with running the terminal commands before flashing. Perhaps this would preserve androidpay! Good luck, post back if you find that works.
Click to expand...
Click to collapse
I've done it both ways and it definitely works when you run the terminal commands prior to flashing. I did it wrong (without terminal commands) first, so i had to do "full unroot" from the app itself, then in recovery ran the terminal commands and flashed 2.66 again and now it works fine for me.
You also have to avoid modifying the /system partition after the fact otherwise that will also break android pay, even if you already have a card added.
you can check with this app if android pay will work:
https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground&hl=en
for example, the aggressive doze option on the new greenify beta will break safetynet, as will Adaway (unless you flash the systemless hosts zip first)
newb question
So... is there a pointer to how to actually issue the commands *before* you flash SuperSU and get root? I can't flash SuperSU to get root until I issue the commands but when I try the commands I get an error message that I need root rights. I'm sure I'm missing something easy. Thanks! (Also, has anyone found a sticky post about what commonly works without breaking root. Obviously anything that touches system, but tutorials on installing AdAway, Greenify, cflumen, etc., or even without breaking Pay would be huge. It just seems every other post has varying information.)
Phssthpok said:
So... is there a pointer to how to actually issue the commands *before* you flash SuperSU and get root? I can't flash SuperSU to get root until I issue the commands but when I try the commands I get an error message that I need root rights. I'm sure I'm missing something easy. Thanks! (Also, has anyone found a sticky post about what commonly works without breaking root. Obviously anything that touches system, but tutorials on installing AdAway, Greenify, cflumen, etc., or even without breaking Pay would be huge. It just seems every other post has varying information.)
Click to expand...
Click to collapse
Months later but adb/fastboot is the key to for terminal commands to your mobile. Likely you've solved by now but if not, theres an easy way to get adb going: http://www.androidbeat.com/2015/11/how-to-set-up-adb-and-fastboot-on-mac/
it is possible to install xposed Frameworks on my rooted FireTV Stick and what the best Solution to how to install?
Gesendet von meinem LG-H815
Go here:
http://forum.xda-developers.com/showthread.php?t=3034811
I used SDK22 ARM on my rooted regular FireTV 1.
Trying to install Xposed on the stick without recovery is extremely dangerous.
rbox said:
Trying to install Xposed on the stick without recovery is extremely dangerous.
Click to expand...
Click to collapse
I don't think you can. You must sideload the "installer" apk but it is just a pointer to a zip matching your processor and android version that must be installed in TWRP. I installed SDK 22 ARM ver. 84 successfully on your new rooted 5.0.5.1r1 for AFTV 1 along with ver. 1.4 of your mods. The ability to hide Menu items is broken but I am able to use Nova which is all I really wanted. Thanks.
Xposed and all the info is here:
http://forum.xda-developers.com/showthread.php?t=3034811
technically you could, but dont do it youll end up with a (tiny) brick
even if you manage to install it (to protect yourself i wont go into details), xposed is very likely to cause bootloops and if you dont have recovery you might be fked up. (or have to start from scratch again)
I don't get it. Xposed runs fine on all my phones and devices. It runs on boot rather than being integrated into the ROM. It can be uninstalled from TWRP if there is a conflict. It's TRWP installer is even kind enough to quit and tell if the version you picked is not right for your hardware.
schneid said:
I don't get it. Xposed runs fine on all my phones and devices. It runs on boot rather than being integrated into the ROM. It can be uninstalled from TWRP if there is a conflict. It's TRWP installer is even kind enough to quit and tell if the version you picked is not right for your hardware.
Click to expand...
Click to collapse
And there is no TWRP for the stick yet...
rbox said:
And there is no TWRP for the stick yet...
Click to expand...
Click to collapse
Any reason it can't be installed from CWMR? Been using TWRP for so long not even sure what CWMR looks like anymore. Did see it for a bit yesterday as I overwrote it with TWRP. RIP.
Seems CWMR is okay:
http://www.androidbeat.com/2015/05/install-xposed-framework-android-5-1-lollipop/
schneid said:
Any reason it can't be installed from CWMR? Been using TWRP for so long not even sure what CWMR looks like anymore. Did see it for a bit yesterday as I overwrote it with TWRP. RIP.
Seems CWMR is okay:
http://www.androidbeat.com/2015/05/install-xposed-framework-android-5-1-lollipop/
Click to expand...
Click to collapse
there is no recovery for the sick other than the stock Amazon recovery.
ldeveraux said:
there is no recovery for the sick other than the stock Amazon recovery.
Click to expand...
Click to collapse
Well then, no Xposed until Rbox completes his magic.
schneid said:
Well then, no Xposed until Rbox completes his magic.
Click to expand...
Click to collapse
he already posted proof of concept; it shouldn't be too long now...
a another Idea is was install xposed with flashify. In the LG G4 section, for some Models they must use this to install xposed, no recovery is available then the Device have a locked Bootloader and can not unlock officially exept 2 models can (h815 and h811)
its just a idea. @rbox what to you think?
Gesendet von meinem LG-H815
MetaIIica said:
a another Idea is was install xposed with flashify. In the LG G4 section, for some Models they must use this to install xposed, no recovery is available then the Device have a locked Bootloader and can not unlock officially exept 2 models can (h815 and h811)
its just a idea. @rbox what to you think?
Gesendet von meinem LG-H815
Click to expand...
Click to collapse
if you want a tiny brick (because the stick is not heavy enough to act as a full brick) then go ahead!
Firetv stick 5.2.1.0 requires XPosed Framework because android needs adblocking
My root stick 5.2.1.0 longs for XPosed Framework. Android requires adblock as my dignity is paramount.
I did eventually find this
http://forum.xda-developers.com/android/software/mod-xposedinstaller-install-xposed-t3165211
But on advice of rbox I wasn't about to try it
simplifiedconfusion said:
My root stick 5.2.1.0 longs for XPosed Framework. Android requires adblock as my dignity is paramount.
I did eventually find this
http://forum.xda-developers.com/android/software/mod-xposedinstaller-install-xposed-t3165211
But on advice of rbox I wasn't about to try it
Click to expand...
Click to collapse
I made a guide which is tried and tested now on alot of fire sticks. Hope this is of some help.
http://forum.xda-developers.com/fire-tv/development/guide-xposed-fire-stick-t3413887
Hello everyone
Recently due to Niantic's decision to prohibit root users of playing Pokémon Go I decided to give a try to Magisk. I followed every step and even flashed my ROM again.
But when trying phh's root it wont work. Rootchecker says root was not correctly installed and trying to use any root app won't make Superuser show any prompt for root permissions.
Thank you so much for the help guys.
more info
renezada88 said:
Hello everyone
Recently due to Niantic's decision to prohibit root users of playing Pokémon Go I decided to give a try to Magisk. I followed every step and even flashed my ROM again.
But when trying phh's root it wont work. Rootchecker says root was not correctly installed and trying to use any root app won't make Superuser show any prompt for root permissions.
Thank you so much for the help guys.
Click to expand...
Click to collapse
What is your ROOT Method, That makes a difference since there might be a conflict in ROM (Preinstalled mods or apps), also, What ROM is it?
CKWTHN said:
What is your ROOT Method, That makes a difference since there might be a conflict in ROM (Preinstalled mods or apps), also, What ROM is it?
Click to expand...
Click to collapse
I flash Magisk v6 and phh's on TWRP. On the other hand I use the stock ROM MM 6.0.1 build 32.2.A.0.253
Apparently Magisk doesn't work properly on Sony devices. See topjohnwu's OP in the Magisk thread.
It partially works for me with some apps like Adaway and TiBU requesting for permissions and working properly but with most other apps not requesting root.
benengyj said:
Apparently Magisk doesn't work properly on Sony devices. See topjohnwu's OP in the Magisk thread.
It partially works for me with some apps like Adaway and TiBU requesting for permissions and working properly but with most other apps not requesting root.
Click to expand...
Click to collapse
I don't know how I could have missed that... Thanks a lot for that. I hope it gets a fix soon enough tho.
Dear all,
I have my Z1C on the latest FW with Dual Recovery and root (SuperSU) but locked bootloader. Now, some apps will not run when they detect root. Can I "unroot" the phone in a convenient way and "re-root" when needed? Without using King Root and while keeping all my data etc.?
Cheers,
Ben
If you are willing to use Xposed, you can use a module called "RootCloak" which is used for hidding root from such apps which don't work unless your phone is not rooted.
BagOfLemon said:
If you are willing to use Xposed, you can use a module called "RootCloak" which is used for hidding root from such apps which don't work unless your phone is not rooted.
Click to expand...
Click to collapse
Thanks. So Xposed works with Dual Recovery/locked bootloader?
I was hoping I could just uninstall SuperSU and re-flash it in TWRP to re-gain root.
nurunet said:
Thanks. So Xposed works with Dual Recovery/locked bootloader?
I was hoping I could just uninstall SuperSU and re-flash it in TWRP to re-gain root.
Click to expand...
Click to collapse
I think it works with Dual Recovery, I'm not entirely sure though, same for Lock/Unlock BL but it should not impact how it works.
Also there is an option in several app for Root to disable it (Completely but you can re-enable it very easily)
BagOfLemon said:
Also there is an option in several app for Root to disable it (Completely but you can re-enable it very easily)
Click to expand...
Click to collapse
There is in the version of SuperSU I am using, but it doesn't seem to work for the banking app I tried. Root cloak reportedly works for it, but I was unsure if Xposed would work with my config and did not want to risk a boot loop or similar.
nurunet said:
There is in the version of SuperSU I am using, but it doesn't seem to work for the banking app I tried. Root cloak reportedly works for it, but I was unsure if Xposed would work with my config and did not want to risk a boot loop or similar.
Click to expand...
Click to collapse
It should work independently of your recovery so no worries. You can still download the zip to uninstall in case of something gone wrong or do a Nandroid backup to be sure
BagOfLemon said:
It should work independently of your recovery so no worries. You can still download the zip to uninstall in case of something gone wrong or do a Nandroid backup to be sure
Click to expand...
Click to collapse
I guess I'll try this WE.
I tried it. In SuperSU settings I chose permanent unroot, rebooted, and voilà: The banking app worked. Then I flashed the latest SuperSU in TWRP, and root was back. Neat!
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
nujackk said:
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
Click to expand...
Click to collapse
Just dismiss the notification.
rbox said:
Just dismiss the notification.
Click to expand...
Click to collapse
I've been doing that, just wondering if i can/should update ? Will It cause problems if i flash latest version?
got the same idea: just flash super su 2.79 sr3 should work?
That's what I'm thinking, just wanting rbox to confirm it shouldn't hose anything. I know some roms on phones don't work with latest versions. And since he is using such an old version, I'm think that might be the case here
Hmm i think i will try it next time. Create a backup and flash supersu.
Spillunke said:
Hmm i think i will try it next time. Create a backup and flash supersu.
Click to expand...
Click to collapse
flashing/updating SuperSU is not working and you will lose root
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
rainman74 said:
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
Click to expand...
Click to collapse
What FW where you on & what method did u try using ?
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
rainman74 said:
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
Click to expand...
Click to collapse
Although it is much more of a pain to do fresh installs. I think when dealing with root it should be more stable to mess with it that way.
One can also do the build.prop mod to stop updates if one wants to test older FW versions.
Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
First thanks for the link to the xposed fix:good: And now that you mention it I don't know why i didn't think of that sooner, should be relatively easy to just replace the files in the zip with 7zip DUH. Only problem is I have everything all setup perfect.