I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
So to clarify, if we want android pay to work we can't use xposed?
Sent from my Nexus 6P using Tapatalk
Wehdota said:
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
Click to expand...
Click to collapse
sweet, i flashed 2.62 thinking it was systemless root too and android pay stopped working. came here looking for a solution, deleted /su/xbin_bind and android pay is working again!
Giving Root Access?
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
I'd like to know this as well
leamdav said:
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
Click to expand...
Click to collapse
Some apps don't ask for root by default, and only do so when you tell them you want to enable the features that require root. ES File Explorer is one such app, and to enable root features you have to open the side menu and toggle the option.
IMO this is the way all apps should be, as I don't always need the root features of every app, as it adds a security risk. I like how BoldBeast Call Recorder does this for example.
bkkzak said:
I'd like to know this as well
Click to expand...
Click to collapse
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
It's a compatability mode that was automatically enabled for a while in older SuperSu.zips to allow developer's apps to work until they update their app to work with systemless root. It is now disabled by defult in newer SuperSu.zips, with the user having to explicitly enable it for its use.
Some apps that requires this to work (becuse they haven't updated their app to work with systemless yet) include:
- Secure Settings
- Es File Explorer.
Etc.Etc.
Hope this helps clarify things for you
Somebody help to remove system app of a6000 without root
It is not possible to remove system apps without root, as to modify data in the system partition root access is required. So its better if you root your phone, uninstall the system apps and then you can unroot your phone back
Thanks for your reply brother
Ya, its impossible to remove system apps without root, but you can disable some of them. Go to Settings>apps>all and disable the app you want. But remember disabling some system apps may cause problem.
Refer to this:
Code:
https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Guys, I'm sorry but I have an obtuse question.
There have been a handful of mods that modify your ROM using Magisk systemless root. As I understand, Magisk roots without touching the /system folder to keep from breaking SafetyNet. Is that correct?
I ask because I know Arise4Android has a Magisk compatible zip you can flash that modifies your mixer_paths_taska.xml file as part of the installation. I'm trying to implement the permanent high impedence mod by modifying the mixer_paths_tasha.xml file and I obviously can't because I have no R/W access to the /system/etc folder.
Does anyone know a way to modify this file by either flashing a zip or otherwise?
Thanks much, everyone!
Anyone tried Modding framework-res.apk ( Oreo ) ? I have tried a few methods with apktool and was able to compile back to apk. But booting it with ended up in bootloop.
If anyone has successfully done this, try compiling one with enabling navigation bar in bools.xml and see if it gives persistent on screen buttons. ( I know there is a magisk module that does enable nav bar - but it often disappears after reboots. So not a good solution. )
mahfoozceecy said:
Anyone tried Modding framework-res.apk ( Oreo ) ? I have tried a few methods with apktool and was able to compile back to apk. But booting it with ended up in bootloop.
If anyone has successfully done this, try compiling one with enabling navigation bar in bools.xml and see if it gives persistent on screen buttons. ( I know there is a magisk module that does enable nav bar - but it often disappears after reboots. So not a good solution. )
Click to expand...
Click to collapse
which version of apktool did you use (pc or mobile)? you dont need to sign the apk. just extract meta-inf from the original apk and install/push it to the modded one. hth
mahfoozceecy said:
Anyone tried Modding framework-res.apk ( Oreo ) ? I have tried a few methods with apktool and was able to compile back to apk. But booting it with ended up in bootloop.
If anyone has successfully done this, try compiling one with enabling navigation bar in bools.xml and see if it gives persistent on screen buttons. ( I know there is a magisk module that does enable nav bar - but it often disappears after reboots. So not a good solution. )
Click to expand...
Click to collapse
Since you are modding system I assume you don't care about breaking safetynet. If it is so why dont you put
Code:
qemu.hw.mainkeys=0
in your build.prop.
This gives you persistant Nav Bar which you can further customize to your heart's content with Xposed.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
mahfoozceecy said:
Anyone tried Modding framework-res.apk ( Oreo ) ? I have tried a few methods with apktool and was able to compile back to apk. But booting it with ended up in bootloop.
If anyone has successfully done this, try compiling one with enabling navigation bar in bools.xml and see if it gives persistent on screen buttons. ( I know there is a magisk module that does enable nav bar - but it often disappears after reboots. So not a good solution. )
Click to expand...
Click to collapse
Since you are modding system I assume you don't care about breaking safetynet. If it is so why dont you put
Code:
qemu.hw.mainkeys=0
in your build.prop.
This gives you persistant Nav Bar which you can further customize to your heart's content with Xposed.
I am a bit rusty due to my break from xda, but IIRC you need to deodex for customization.
mahfoozceecy said:
Anyone tried Modding framework-res.apk ( Oreo ) ? I have tried a few methods with apktool and was able to compile back to apk. But booting it with ended up in bootloop.
If anyone has successfully done this, try compiling one with enabling navigation bar in bools.xml and see if it gives persistent on screen buttons. ( I know there is a magisk module that does enable nav bar - but it often disappears after reboots. So not a good solution. )
Click to expand...
Click to collapse
You can compile your changes as an overlay and put it in /vendor/overlay/
OP status for the first time
I just found out you can snooze it just before typing this sentence lol. But is there a way to disable the notification permanently without root?
I don't expect it to survive a reboot but if there is a way I would imagine it being achieved via ADB?
Not a big deal anymore since I just found out you can snooze it for 2 hours but hey might as well finish what I started. If you were wondering my concern is burn in but I think the icons on the status bar move? I would rest better knowing it's not there anyway.
Thanks, I appreciate it.
EDIT: Nevermind I think I did it.
System/System app settings
Then disable "Show update notifications"
EDIT 2: It did not work:laugh:
- With root I used this solution:
Edit the file: system/build.prop
copy / paste the line that contains the version number.
Example: ro.build.version.incremental=V14.3.11.0.PFJMIXM
I have put a "#" for memo and changed v10 to v14 :
Code:
# ro.build.version.incremental=V10.3.11.0.PFJMIXM
ro.build.version.incremental=V14.3.11.0.PFJMIXM
- Without root It may also be possible (to check) to modify this file with XiaomiADBFastbootTools (with the small embedded file manager).
Do I need an unlocked bootloader or root access to use XiaomiADBFastbootTools?
The Flasher, Wiper and Camera2 modules require an unlocked bootloader but everything else works without rooting or unlocking.
Click to expand...
Click to collapse