Database Info

Can I uninstall super user app if it is built in to my ROM?

I'm using a cm nightly with the new super user built into the ROM. So, can I uninstall the app or what?
Free your mind!

50cr473s said:
I'm using a cm nightly with the new super user built into the ROM. So, can I uninstall the app or what?
Free your mind!
Click to expand...
Click to collapse
Uninstalling it would remove root. You can replace it with another superuser app.

I'd be careful with this. I did it by accident (switched ROMs, had a had SuperSU installed on my old ROM, but new ROM came with its own SU program. When I reinstalled everything I included SuperSU) and it messed everything up - no programs could successfully get root access. I ended up just wiping and re-installing the ROM, this time not re-installing SuperSU on top of it and sticking with the built-in one on Viper.
Is there really any difference between SU apps? Hardly seems worth the hassle.

I'm using cm's app which is open source and built to be compatible with android platform, thus the ability to be integrated into the ROM. I've noticed that when I switch ROMs(e.g. carbon's unofficial port) Supersu is there in the app tray(instead of cm's) and cm's is in the settings. I had supersu installed before, but removed it when I installed cm's app. Oh my I've gone crosseyed. I've decided that it works as is and my only need is to clean up a little. I was just wondering if any one knew about specifically CM's super user?
Free your mind!

50cr473s said:
I'm using cm's app which is open source and built to be compatible with android platform, thus the ability to be integrated into the ROM. I've noticed that when I switch ROMs(e.g. carbon's unofficial port) Supersu is there in the app tray(instead of cm's) and cm's is in the settings. I had supersu installed before, but removed it when I installed cm's app. Oh my I've gone crosseyed. I've decided that it works as is and my only need is to clean up a little. I was just wondering if any one knew about specifically CM's super user?
Free your mind!
Click to expand...
Click to collapse
Well here's two cents for what its worth. When I moved from Rooted Stock (with SuperSU) to CM10 based Rom (LiquidSmooth), the CM10 app superseded from under Settings. SuperSU had to ask that app for permission before opening its own shop. From then on SuperSU ruled.
You don't necessarily have to do this. I did it because I like and support Chainfire's work. You can uninstall SuperSU if you are getting a CM based ROM with their app. It does not matter either way. They both are good.
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.

Perseus71 said:
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Click to expand...
Click to collapse
You could have flashed root back just the root zip

a box of kittens said:
You could have flashed root back just the root zip
Click to expand...
Click to collapse
I tried and failed. Recovery Flash had error unable to obtain Root.

Perseus71 said:
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Click to expand...
Click to collapse
The SuperUser in CM now is not the same as it used to be, this is a new, open source SuperUser built by Koush and designed to be integrated into the system. Also this new version has two ways of updating the binary should one fail you.
Sent from my One X using Tapatalk 2

bliind said:
The SuperUser in CM now is not the same as it used to be, this is a new, open source SuperUser built by Koush and designed to be integrated into the system. Also this new version has two ways of updating the binary should one fail you.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes I am aware of CM's inbuilt app. My comment that you quoted, pertains to the SuperUser App by ChainsDD as against SuperSU by Chainfire. This for the part 2 of OP.

Do either of the devs have a thread pertaining to switching su apps? I couldn't find anything?
Free your mind!

50cr473s said:
Do either of the devs have a thread pertaining to switching su apps? I couldn't find anything?
Free your mind!
Click to expand...
Click to collapse
Here's SuperSU. Best to download the App from Google Play. The thread can be confusing.
The CWM Superuser app on Google Play.
The original Superuser App by Chainsdd. As before best get it on Google Play.

i always download the supersu cwm flashable from the supersu thread, then after you flash it you can disable the original one.

[Q] Can't uninstall system apps with Titanium Backup in CM11

Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.

Cloonix said:
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Click to expand...
Click to collapse
What happens if you delete the file with a file manager and reboot?

Aerowinder said:
What happens if you delete the file with a file manager and reboot?
Click to expand...
Click to collapse
I used Solid Explorer as a file manager and tried to delete /system/app/Browser.apk. The root-confirmation (CM11 superuser) pops up, asks for superuser (i grant) and Solid Explorer deletes the file without error. But the file is still there (without reboot).
Issue with superuser?
Edit: Stop... I noticed /system is mounted as read-only.

I tried to analyze the problem... and the only conclusion is, that my superuser is not working. Also Super SU ist not working. I also flashed Omni ROM instead of CM11 with no success. I used an older version of TWRP without success. Does anybody has an idea?
Edit: Before with Stock ROM and Super SU it was working.

I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?

Me to, cm11 for a850L build on crdroid nexus4

Cloonix said:
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Click to expand...
Click to collapse
Did you leave out Franco kernel this time?

This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456

es0tericcha0s said:
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
Click to expand...
Click to collapse
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
Aerowinder said:
Did you leave out Franco kernel this time?
Click to expand...
Click to collapse
No I flashed Franco after CM.

Cloonix said:
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
No I flashed Franco after CM.
Click to expand...
Click to collapse
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?

es0tericcha0s said:
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.

Cloonix said:
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Click to expand...
Click to collapse
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.

es0tericcha0s said:
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
Click to expand...
Click to collapse
I tried this. And it was successfully changing selinux to permissive with every reboot. But doing this I noticed that even permissive doesn't solve the problem. CM11 built-in superuser just don't work for me. Only "Super SU" by Chainfire works well. And permissive solves a few other problems besides TiBa.

Personally I've always eventually had issues with Superuser unmounting the system as rw causing issues with apps like Titanium. Had it happen many many times on my old phone as well as the Nexus 5 across multiple ROMs. I just stick with SuperSU now.

Haven't had too many issues with that part it seems, but glad you narrowed down the problems.

I find this issue sometimes on varous flashes of CM 11 on different devices.
I use ROM toolbox fo manage apps, and sometimes it just wont delete. The solution is strange: I install adaway - somehow, that "unlocks" something that lets you delete apps. You can uninstall adaway once you have run it!

Galaxy Nexus
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!

es0tericcha0s said:
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel

daniu said:
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
Click to expand...
Click to collapse
If you are already using CM11, then yes, you can install SuperSu from the Play Store. Once you do and open the app, it will prompt you to update the SuperUser binary. You should be able to do the "normal" method, and then once that updates, reboot, then try the SELinux app again and then everything should start to work like you would expect. If the normal method doesn't work, then you can let it download the newest zip for you if you choose the CWM/TWRP method, and then boot to recovery and install the zip it downloads for you.

SeEsAw12 said:
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
Click to expand...
Click to collapse
No clue why, but this worked for me. Permissive didn't do it (was already permissive using CM 11 for tf201) and AdAway didn't do it. Didn't matter that Wanam Xposed is for Samsung devices, once given root to this app, Titanium got its head out of its rump.
UPD: So, if i uninstall Wanam Xposed then TB sticks its head back up its rump. Whatever giving root to that app does, its fixing usage issues with TB.

Hide root for play store app "vipps"

Hello,
I'm trying to use an app from the playstore called "vipps".
It's from a bank in norway called DNB, and it let's you transfer money near instantly from one to another.
This app refuses to run on my phone because it's rooted and have a custom rom etc.
I'm running Xtrestolite Deodexed with the included alliance firmware.
I have read somewhere about Rootcloak Plus with Cydia (no idea what this really is, but i understood cydia is like app store for iOS jailbreaked phones?)
I'm wondering if this exsists on 5.0.2 lollipop (and how to get it / install it if it does), or if there is any other known way of bypassing this applications refusal to run on my device.
I'm on a SM-G920F (international version) if that helps.
Any tips / questions / help regarding this is most welcome and much appreciated!
- Renolz

Try searching for a Xposed Module that does this
I remember there was one for kitkat but i dont know whether or not its currently available for lollipop

itsbighead said:
Try searching for a Xposed Module that does this
I remember there was one for kitkat but i dont know whether or not its currently available for lollipop
Click to expand...
Click to collapse
I tried to get xposed, but it's not yet compatible with the S6 as far as i know.
Something about SDK version 21 and arm 64 (no idea what this is, but that was the error when trying to install it)

renolz said:
I tried to get xposed, but it's not yet compatible with the S6 as far as i know.
Something about SDK version 21 and arm 64 (no idea what this is, but that was the error when trying to install it)
Click to expand...
Click to collapse
Cydia is for ios based devices and if s6 had xposed that module called root cloak will work for what you need it for. but since theres no xposed. You cant run it.

I second that!
I have the exact same problem! Please let me know if you find a way to bypass the app restrictions!

Same here:
Cyanogen OS 12.0, android 5.0.2, OnePlus One
Tried RootCloak plus app, add no.dnb.vipps app but still does not open.

I have the same issue with a Huawei running 4.4.4 Vipps by DNB does not work.. Xposed says that there is a known issue with the room installed. I deactivated the Resource hoocks, but it did not solve the issue.. BALLS!!
Mr.P

parrafin23 said:
I have the same issue with a Huawei running 4.4.4 Vipps by DNB does not work.. Xposed says that there is a known issue with the room installed. I deactivated the Resource hoocks, but it did not solve the issue.. BALLS!!
Mr.P
Click to expand...
Click to collapse
Hi,
I was able to fix the Vipps issue by using Rootcloak version 1.4 (not the newest one), and adding no.dnb.vipps to the list.
Works like a charm on SGS6
Hope this helps!

OPO CyanogenOS 12.1.1 Android 5.1.1 rootcloak vipps
I have a oneplus one With CyanogenOS 12.1.1-YOG7DAS2K1 and android version 5.1.1. The phone is rooted and I have twrp installed.
I used twrp to install Xposed framework 85 trough the link provided in this post: http://forum.xda-developers.com/showthread.php?t=3034811
Within the xposed installer app I downloaded the module RootCloak version 2.1.0
In rootCloak I added no.dnb.vipps (add/remove apps -> three dots -> add custom app -> write "no.dnb.vipps")
Now I can run vipps without any problems.

Vipps on OPO running cm14.1
Sorry to bring up an old thread.
I've been using this Norwegian bank app on cm12/cm13 with rootcloak for a while now without any trouble. Lately the app just crashed on login when using rootcloak so i decided to flash cm14.1 nightly and see if systemless root and magisk would do the trick instead. I flashed cm14.1, fully unrooted the phone, flashed magisk and phhs systemless root. I downloaded SafetyNet playground, and my phone passes all SafetyNet checks. I also downloaded pokémon GO to verify, and that works flawlessly. Vipps however, does not work... The app does not crash anymore, but i get the message "vipps doesn't support rooted devices".
It seems to me like the app detects that i'm running cyanogenmod. When my oneplus one was new, the app wouldn't work even though i had a locked bootloader and no root. I actually had to unlock bootloader, root, flash xposed and install rootcloak to get it working.
Is there any workaround for this problem? It seems to me that rootcloak did something more than just hide the root from the app. Is this correct? I can upload the .apk file for Vipps if that would be of any help. The app force closes before login with the message "Vipps doesn't support rooted devices", so i dont think region will be a problem.

I too am curious of this.
Is there a way to "fool" an app from checking if there is a custom ROM or original ROM?
I assume the app only checks ROM info, and perhaps that can be easily edited?

Magish Hide, checkmark:
com.android.phone
no.dnb.vipps
not sure if these are needed as well
com.slash.batterychargelimit
com.grarak.kerneladiutor
com.dp.logcatapp

Android Pay Working (Tested on TruPure 2.6)

Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:

Just so you're aware the link you included is broken and depending on which version of SU is installed Step 2 might not be necessary as version 2.62-3 automatically installs systemless.

Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.

Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk

Fixed the broken link, and clarified that this is only tested on the latest supersu.

SR3TLAW said:
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Click to expand...
Click to collapse
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.

drewksparks said:
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
Click to expand...
Click to collapse
Spasticdroid said:
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Sounds like regardless there is no still no way with Exposed or Google Dialer

SR3TLAW said:
Sounds like regardless there is no still no way with Exposed or Google Dialer
Click to expand...
Click to collapse
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.

drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
Whats all the fuss about Google Dialer, does it make dreams come true?

drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk

Spasticdroid said:
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
My mistake. I thought I remembered something about it working. So, at the moment, there seems to be no way to make Android Pay work with Xposed or Google Dialer. I personally get by very well without both.

Has anyone tried it with multirom and have the second rom without any root or xposed? I'm gonna give it a go and see how it pans out.
Sent from my XT1575 using Tapatalk

Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...

bsilver2988 said:
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
Click to expand...
Click to collapse
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
/system/app
Android System WebView (WebViewGoogle)
Chrome Browser - Google (Chrome)
Clock (DeskClockGoogle)
Cloud Print (CloudPrint2)
Exchange Services (Exchange3Google)
Gmail (Gmail2)
Google Calendar (CalendarGoogle)
Google Docs (EditorsDocs)
Google Drive (Drive)
Google Keyboard (LatinImeGoogle)
Google Now Launcher (GoogleHome)
Google Photos (Photos)
Google Play Movies & TV (Videos)
Google Play Music (Music2)
Google Sheets (EditorsSheets)
Google Slides (EditorsSlides)
Google Talkback (talkback)
Google Text-to-Speech (GoogleTTS)
Google Translate (Translate)
Hangouts (Hangouts)
Maps (Maps)
YouTube (YouTube)
/system/priv-app
Google Play Services (GmsCore)
Google Play Store (Phonesky)
Google App (Velvet)
Click to expand...
Click to collapse

Spasticdroid said:
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
Click to expand...
Click to collapse
Thanks for this! It makes perfect sense. Unfortunately I'm still getting a Fail when I run the test. Any other thoughts?
EDIT: Figured it out! I guess OpenGapps itself was incompatible with this setup. Installing TruPure without it solved the problem. Thanks for the help!

Thanks @drewksparks, followed your detailed instructions and confirmed by buying me a beer with my phone running True Pure 2.6.2. Now to decide if it's worth giving up Xposed, Gravity Box, Amplify, etc. Hmmm I want it all.

drewksparks said:
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Click to expand...
Click to collapse
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.

cerobles1 said:
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
Click to expand...
Click to collapse
Won't work unfortunately. Too many files and apps and such are needed in CM and CM-based ROMs (example: Bliss) for them to work properly, and in turn breaks Android Pay.
If we can ever get an AOSP-based ROM, which is bare (meaning not built with AOSP apps included) working on this device, we may have a chance, just like how some ROMs on Nexus devices, such as Chroma and PureNexus, works with Android Pay.
The last thing needed would be a proper GApps package containing only the default GApps found in a stock Pure/Style ROM to install (can be updated versions of those apps too.)
Sent from my XT1575 using Tapatalk

Unable to install Youtube Vanced on rooted Moto G 4 Plus

I have a Motorola G 4 Plus, rooted SU 2.82, latest TWRP, Havoc 2.9, Android 9 Pie. Arm v7I.
Upon trying to install Youtube Vanced through the Vanced Manager, the app crashes and the install fails with the message "failed for unknown reason blah blah blah please go to the Telegraph Discord group" I can post a log file if needed.
After that ordeal, the Youtube app appears in my app drawer, when I try to open it it says "you don't have Google Play Services" and closes.
I tried this with micro-g installed, I disabled apk signature verification with Lucky Patcher, doesn't make a difference.
I even made sure to allow unknown sources and checked the permissions. No go.
I also tried the apks installer through the SIS installer or whatever its called, SAS, SAI or whatever, no luck.
Feels like my phone can go as far as to root and custom recovery and custom rom and busybox and such but continue to find myself in these annoying situations with no resolution. Other people seem to be able to get it to work though. Perhaps its the phone?
Any help is appreciated, thanks!

Do you have magisk installed or are you using another solution for root? I saw your post about brave not working , may I suggest a rom reinstall? Try it with the microg gapps package.
Edit: grammar.

ThatLatinGuy said:
Do you have magisk installed or are you using another solution for root? I saw your post abou brave not working , may I suggest a rom reinstall? Try it with the microg gapps package
Click to expand...
Click to collapse
Rooted with SU 2.82 flashed via TWRP and use SU app. Not magisk. Perhaps I'll try another ROM. Too bad Havoc seems really good customizable.
I originally forgot to wipe cache and dalvik/art cache after flashing the Havoc ROM so maybe that screwed things up, I'll try re-flashing.

I'd remove SU and use magisk 21.4 (not higher, and never update it ever).
when was 2.82 released ? it must be a long time ago now and I don't think it's recommended for anything anymore.
even without any root Vanced manager would install your microg and vanced just fine.

3mel said:
I'd remove SU and use magisk 21.4 (not higher, and never update it ever).
when was 2.82 released ? it must be a long time ago now and I don't think it's recommended for anything anymore.
even without any root Vanced manager would install your microg and vanced just fine.
Click to expand...
Click to collapse
Super SU was last updated 2020 from my understanding.

big bad brad 31 said:
Super SU was last updated 2020 from my understanding.
Click to expand...
Click to collapse
the last post in chainfire's superSU thread here is from 2018, it says just use magisk

big bad brad 31 said:
Super SU was last updated 2020 from my understanding.
Click to expand...
Click to collapse
this is the last and latest version of SuperSU
SuperSU Download
it was released back in 2017 all other website that has SuperSU for downloads except that site are Unofficial Released

big bad brad 31 said:
I have a Motorola G 4 Plus, rooted SU 2.82, latest TWRP, Havoc 2.9, Android 9 Pie. Arm v7I.
Upon trying to install Youtube Vanced through the Vanced Manager, the app crashes and the install fails with the message "failed for unknown reason blah blah blah please go to the Telegraph Discord group" I can post a log file if needed.
After that ordeal, the Youtube app appears in my app drawer, when I try to open it it says "you don't have Google Play Services" and closes.
I tried this with micro-g installed, I disabled apk signature verification with Lucky Patcher, doesn't make a difference.
I even made sure to allow unknown sources and checked the permissions. No go.
I also tried the apks installer through the SIS installer or whatever its called, SAS, SAI or whatever, no luck.
Feels like my phone can go as far as to root and custom recovery and custom rom and busybox and such but continue to find myself in these annoying situations with no resolution. Other people seem to be able to get it to work though. Perhaps its the phone?
Any help is appreciated, thanks!
Click to expand...
Click to collapse
Try installing a custom rom based on A10 n see if this works out for u, it works perfectly on my g4+ on A10 ...