Related
After updating my dream to cyanogenmod 5.0.8 ds, I realized a few problems. I have reflashed a few times, and a major gripe I have is that I can't seem to update the su binary to the latest version, it keeps failing at "gaining root access". I have also had to use the superuser update fixer to install the latest superuser version. The reason I want to install it is so that the stericson busybox installer will work, and thus metamorph will work, as it relies on the user having a semi-recent version of busybox.
P.S. I currently want to stick to cm5, as it is otherwise stable and full features. Any suggestions for another rom had better be convincing and involve a minimum of flashing.
I have the danger spl and cyanogen+jf recovery
Not sure if it's exactly what you need, but have a look here: http://forum.xda-developers.com/showthread.php?t=682828 I've noticed someone was talking about the Dream as well...
just try and uninstall super user all together and download superuser or super su from market, then try to update busbox through market app
I was able to get the su binary to update, but I'm not sure how. However, superuser is now denying everything, even freshly installed apps. What is going on?
Magicnet2 said:
Not sure if it's exactly what you need, but have a look here: http://forum.xda-developers.com/showthread.php?t=682828 I've noticed someone was talking about the Dream as well...
Click to expand...
Click to collapse
That is from a really early version of superuser, and it doesn't seem to fully answer my question, sorry.
can you uninstall current superuser and reinstall latest from market?
That is what I've already done. I couldn't update the su binary without doing so. All that cm5 seemed to have was the "superuser permissions" app.
When you go into the app do you have permissions denied? If your in an adb shell does it allow you su?
Sent from my Nexus 4 using XDA Premium 4 mobile app
When I go into any root app, superuser gives me a toast that says { } has been denied superuser permissions. The superuser app itself seems to have root access, though.
Try to just do it again, there's no reason I can think of this will happen
Just uninstall and reinstall su app, maybe try supersu, then use a busybox app to update. If this doesn't work again than try to manually do it
Sent from my Nexus 4 using XDA Premium 4 mobile app
Now, every time I try to do it, even after freshly flashing cm5, my phone does a boot loop.
Maybe try to extract contents of ROM and swap with new superuser
Sent from my Nexus 4 using XDA Premium 4 mobile app
At this point, I'm probably just going to try to get cm6 going on this thing.
Sure, check your other thread, I'll upload tonight
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks!
I installed SuperSu v2.67 on a Nexus 5 running stock Marshmallow 6.0.1, and SuperSu works great for me so far!
The only (minor) issue I've encountered thus far is that the SuperSu icon seems to be missing from the Google Now launcher home screen and app drawer.
I can still launch SuperSu by searching for it in the Google Play store and clicking "Open", and it still pops up when an unauthorized app is requesting root access.
I've tried to do a complete unroot + reinstall, change the SuperSu icon from the app's settings etc. - without success.
Has anyone else encountered this? Is there any way to get SuperSu icon to show up?
Thanks in advance.
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Edit:
Correction! Found the icon. It was buried in the app drawer all along. What threw me off was that for some reason, when I write "SuperSu" or any prefix of the name in the search box at the top, it doesn't find SuperSu, like it does pretty much any other app. Weird.
Anyway, thanks for the help and sorry about the false alarm.
Chainfire said:
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Click to expand...
Click to collapse
I'm having a similar problem as the OP except that 2.6.7 binaries don't install on a T-Mobile Note 4 (SM-910T3) in either Lollipop or Marshmallow using either the Normal or TWRP methods. 2.6.5 and 2.6.6 binaries install properly, however.
I tried the command in recovery and got the following error:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Chainfire said:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Click to expand...
Click to collapse
You're right I didn't explain things right. My ROM comes preinstalled with SuperSU 2.6.6 and I have the same issue as the OP as the app doesn't appear in either app drawer and I can't launch it from the Play Store either. I'll try adb uninstall properly.
The 2.6.7 failed install is a separate issue. Do I start another thread here in the same forum? What info do you need?
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
thereassaad said:
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
Click to expand...
Click to collapse
Thanks. I got it to uninstall and was able to reinstall, but it still wouldn't show up in app drawer or open from the Play Store.
Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?
I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.
I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.
Many thanks in advance for any help you can provide.
Squall88uk said:
Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?
I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.
I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.
Many thanks in advance for any help you can provide.
Click to expand...
Click to collapse
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?
With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.
Many individuals don't know that.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
Ibuprophen said:
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?
With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.
Many individuals don't know that.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
Click to expand...
Click to collapse
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Squall88uk said:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I am in the same boat. I am using the the latest RR FROM which is awesome, but I'm not wanting to use magical. Have always used super SU and stick Mount for my next SD. Would like to know the process for disabling manual and cm/Los root mgmt. To use Super SU. I can't use stick Mount with root explorer without super SU. WHEN I try to update binary it fails and if I try to flash in recovery, I get stuck in boot loop and have to restore backup.
Having a similiar problem on Galaxy S2 with RR 5.8.2 - installed SeperSu and it fails to update its binary when I choose 'normal'. Tried Cwm/Twrp option on a stock rom once and the phone got softbricked. Converting SuperSu to system app doesn't help.
---------- Post added at 05:05 AM ---------- Previous post was at 04:48 AM ----------
Squall88uk said:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
No such option appears in SuperSu after disabling root access in dev options here also.
There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.
I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.
So in short, disabled means root access is left open and CyanogenMod doesn't manage it.
If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.
I've never had a problem with SuperSU and always left the Root Access disabled.
I hope i had explained it okay...
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***
Ibuprophen said:
There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.
I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.
So in short, disabled means root access is left open and CyanogenMod doesn't manage it.
If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.
I've never had a problem with SuperSU and always left the Root Access disabled.
I hope i had explained it okay...
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***
Click to expand...
Click to collapse
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.
Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?
kikot said:
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.
Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?
Click to expand...
Click to collapse
I attached an image of where in SuperSU the setting is but, I leave it unchecked...
Try flashing the SuperSU zip since flashing it also installs the binaries too.
Disclaimer: I will take no responsibility if flashing this zip somehow causes you to go deaf, scares your cat, receiving of noise complaints from your neighbors, development of anti-social behavior, getting hit by a bus, a twerking grandmother, broken windows and/or any other imaginable royally screwed possibility.
Q: Will this work on other Samsung devices?
A: Maybe, I see no reason for it not to work on the S8 or S8+. Feel free to test it out and report back.
Credits: @zhuhang for ViPER4Android FX & XHiFI.
@partcyborg, @me2151, and @elliwigy for hooking us up with root.
Features: Systemwide ViPER4Android FX 2.3.4.0 (higher audio processing than newer versions) and ViPER4Android XHiFi.
Installation steps (make sure to read these before downloading the ZIP):
1) Make sure you're rooted.
2) Download either FlashFire (Snapdragon - thank you, @Chainfire) or install TWRP (Exynos).
3) Install BusyBox, to /system/xbin (otherwise, XHiFi will not work, only FX will).
4) Get Titanium Backup, ROM Toolbox PRO, or any similar application.
6) Freeze "Adapt Sound" and "SoundAlive".
5) Flash the attached zip.
6) Grant root permissions to both FX and XHiFi (you might have to uninstall the FX driver within the in-app settings to trigger this, if so, simply reflash the ZIP after having done so and reboot).
7) Reread step six.
8) Profit & enjoy.
Paradoxumical said:
Disclaimer: I will take no responsibility if flashing this zip somehow causes you to go deaf, scares your cat, receiving of noise complaints from your neighbors, development of anti-social behavior, getting hit by a bus, a twerking grandmother, broken windows and/or any other imaginable royally screwed possibility.
Q: Will this work on other Samsung devices?
A: Maybe, I see no reason for it not to work on the S8 or S8+. Feel free to test it out and report back.
Credits: @zhuhang for ViPER4Android FX & XHiFI.
@partcyborg, @me2151, and @elliwigy for hooking us up with root.
Features: Systemwide ViPER4Android FX 2.3.4.0 (higher audio processing than newer versions) and ViPER4Android XHiFi.
Installation steps (make sure to read these before downloading the ZIP):
1) Make sure you're rooted.
2) Download either FlashFire (Snapdragon - thank you, @Chainfire) or install TWRP (Exynos).
3) Install BusyBox, to /system/xbin (otherwise, XHiFi will not work, only FX will).
4) Get Titanium Backup, ROM Toolbox PRO, or any similar application.
6) Freeze "Adapt Sound" and "SoundAlive".
5) Flash the attached zip.
6) Grant root permissions to both FX and XHiFi (you might have to uninstall the FX driver within the in-app settings to trigger this, if so, simply reflash the ZIP after having done so and reboot).
7) Reread step six.
8) Profit & enjoy.
Click to expand...
Click to collapse
Won't installing busybox to system/xbin trip up safety net flagging your device as tampered/rooted? Also, if you have magisk, can't you just install the v4a module right from within magisk? I don't see the point in going through all these extra steps and flagging your device in safety net when you can just install the v4a magisk module. Not trying to be a ****, asking honest questions.
Works perfectly on my T-Mobile N950U! Thanks!
Sent from my SM-N950U1 using Tapatalk
xxx42069 said:
Won't installing busybox to system/xbin trip up safety net flagging your device as tampered/rooted? Also, if you have magisk, can't you just install the v4a module right from within magisk? I don't see the point in going through all these extra steps and flagging your device in safety net when you can just install the v4a magisk module. Not trying to be a ****, asking honest questions.
Click to expand...
Click to collapse
If you have a Snapdragon device, SafetyNet is already tripped due to the nature of the rooting process.
But if you have an Exynos device, by all means, use the Magisk module. This ZIP was intended for the Snapdragon variant (since that's what I have), but works on Exynos variants as well.
i flashed it n nuthin,i cant even find the in-app u wrote about
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
lilviet93 said:
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
Click to expand...
Click to collapse
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
mister_propa said:
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
Click to expand...
Click to collapse
Yeah, I used the old busybody version. I just went back to stock after a few hours of messing around with no results. My main reason for root and accepting the 80% battery limit is viper but since I can't get it working I went back to stock for now. Will try again once there is more development. Let me know if you do get it working.
mister_propa said:
i flashed it n nuthin,i cant even find the in-app u wrote about
Click to expand...
Click to collapse
mister_propa said:
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
Click to expand...
Click to collapse
lilviet93 said:
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
Click to expand...
Click to collapse
When you guys flashed it with Flashfire, which options did you enable/disable? Mind taking a screenshot of the preflash stage for me? Do you see the Flashfire installation screen? You should be able to see the ZIP flash progress script.
As for those having problems with installing BusyBox, if you're using Stericson's, you have to manually grant the storage permission.
Paradoxumical said:
When you guys flashed it with Flashfire, which options did you enable/disable? Mind taking a screenshot of the preflash stage for me? Do you see the Flashfire installation screen? You should be able to see the ZIP flash progress script.
As for those having problems with installing BusyBox, if you're using Stericson's, you have to manually grant the storage permission.
Click to expand...
Click to collapse
Just select the zip and start the flashing process. It went black then the flashfire process starts then phone reboots but no sign of the viper app anywhere. How do I manually grant permission? What is the best way to install busybox?
lilviet93 said:
Just select the zip and start the flashing process. It went black then the flashfire process starts then phone reboots but no sign of the viper app anywhere. How do I manually grant permission? What is the best way to install busybox?
Click to expand...
Click to collapse
I personally used BusyBox Pro by Stericson (he's an amazing developer), but I did have to manually grant the storage permission first by going to: App info > Permissions > Storage (toggle it on).
If this doesn't work, use BusyBox Installer (warning: it's riddled with ads).
As for Flashfire, try enabling the "mount system read/write" option.
Paradoxumical said:
I personally used BusyBox Pro by Stericson (he's an amazing developer), but I did have to manually grant the storage permission first by going to: App info > Permissions > Storage (toggle it on).
If this doesn't work, use BusyBox Installer (warning:it's riddled with ads).
As for Flashfire, try enabling the "mount system read/write" option.
Click to expand...
Click to collapse
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
kidbranz01 said:
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
That is the strangest thing, I can't imagine why the ViPER apps wouldn't show up. The only thing that comes to mind is... If you ran the fsck script after rooting, did you?
kidbranz01 said:
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
I had the same issue, but then in FlashFire, under settings I disabled Emulate framebuffer.. Now Viper4android is installed and working.
Does anyone who has this installed get freezes after reboots from time to time?
kirschdog1 said:
Does anyone who has this installed get freezes after reboots from time to time?
Click to expand...
Click to collapse
It freezes up all the time, even when requesting SU.
Sent from my SM-N950U using Tapatalk
Does anyone on Snapdragon have this and FM Radio working together? Unfortunately, I'm finding I can't run both. I don't know if it's my Viper settings or what. Any input would be appreciated as I don't want to have to choose between the two features if I don't have to
For those who had trouble on snapdragon try using latest Sam fail v2 if possible it works perfect on here if you follow directions. Few key things, disable emulate framebuffer in flashfire and when flashing enable mount read and write system, also make sure you install drivers in both v4a apps to enable root as root access is need for v4a to work properly after unistalling drivers and granting root reflash zip in flashfire to restore drivers and profit
I have problem with viper4android hifi can't read root access
jomolocco said:
I have problem with viper4android hifi can't read root access
Click to expand...
Click to collapse
If I remember correctly, there was something that said if you had this trouble, open app, uninstall the driver, Grant the permission, then re-flash the app.
My banking app (NAB Mobile Banking), like most, doesn't like it if my phone doesn't pass CTS or if it's rooted when setting up tap-and-pay.
Since I've started using Magisk I've had lots of trouble getting this banking app to work properly.
This is how I have learnt to set it up .
1. Install Magisk. I'm using 15.3.
2. Wipe the app's data in Settings>Apps. But *do not* start the banking app!
3. Hide the app in Magisk.
4. Reboot the phone.
5. Set up the banking app.
At this stage it's usable but in order to be able to survive reboots and restoring from backups I do the following:
6. Hide Magisk Manager. If I don't do this the app will lose the tap-and-pay capability on reboot.
(Thanks @Didgeridoohan for the suggestion)
Old
6. Backup the app using Titanium Backup (TB).
7. Freeze the app using TB before rebooting the phone for whatever reason. If I don't do this the app will lose the tap-and-pay capability.
I take my backups in this state.
Once the phone has rebooted I then:
8. Defrost the app in TB.
9. Make the app the default for tap-and-pay as this gets lost by the freeze/defrost process.
If I have forgotten to freeze the app across reboots then tap-and-pay won't work. However I can:
10. Use TB to restore the app's data, set it as the default for tap-and-pay and I'm good to go.
End Old
The following actions will break the tap-and-pay function and require me to go through the setup process all over again:
a. Setting a new lock screen password, even it's the same as the previous one.
b. Wiping /data in TWRP because even though I restore the backup the lock screen password gets broken requiring me to do the following:
i. Run the following commands in TWRP Terminal to remove the current password before rebooting the system:
Code:
cd /data/system
rm gatekeeper.* locksettings.*
ii. Set a new lock screen password (see point (a) above).
My details:
Phone: OnePlus 3T
OS: OxygenOS 5.0.1
Root: Magisk 15.3, Magisk Manager 5.5.5
Banking app: https://play.google.com/store/apps/details?id=au.com.nab.mobile
Security: Password set and required on start up; fingerprint setup
You don't mention anything about hiding the Manager. Does that make a difference?
Didgeridoohan said:
You don't mention anything about hiding the Manager. Does that make a difference?
Click to expand...
Click to collapse
I never considered that.
I may try that to see if it makes a difference.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
I never considered that.
I may try that to see if it makes a difference.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
For some apps it makes all the difference...
If you haven't checked it out already, there's a bunch of tips like that in the troubleshooting guide.
Different but somewhat related: Since I'm on a custom ROM, Magisk Hide doesn't properly enable passing SafetyNet. The only way I could get it to work was to enable Magisk Hide for specific apps and to install the Universal SafetyNet Fix module (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431). Maybe you could try that module too and see if it helps.
Didgeridoohan said:
For some apps it makes all the difference...
If you haven't checked it out already, there's a bunch of tips like that in the troubleshooting guide.
Click to expand...
Click to collapse
So, I tried hiding Magisk Manager and now I can reboot the phone without causing issues for the banking app. Thanks very much for the suggestion!
I did read [some of ] the installation and trouble shooting guide but, even now, I wouldn't have tried hiding the manager because my app can be set up properly without issues. It's only the reboot that caused problems. And hiding the manager has fixed this.
I've updated the OP to reflect this.
Sent from my OnePlus3T using XDA Labs
I am curious if anyone has gotten Chase Pay working with Magisk installed. I have turned off xposed ( which is known to fail safetynet), turned on magisk hide, did Magisk random package regeneration, and passed safetynet, but Chase Pay still gives me the error of having root on my phone. My Android Pay is working just fine since I pass SafetyNet, but Chase Pay doesn't.
c19932 said:
I am curious if anyone has gotten Chase Pay working with Magisk installed. I have turned off xposed ( which is known to fail safetynet), turned on magisk hide, did Magisk random package regeneration, and passed safetynet, but Chase Pay still gives me the error of having root on my phone. My Android Pay is working just fine since I pass SafetyNet, but Chase Pay doesn't.
Click to expand...
Click to collapse
You may have skipped a step. At this point, try clearing the Chase Pay app data, reboot, then run and sign into Chase Pay again. That is, once it has "seen" Magisk, it remembers it until you clear its stored data.
At least, that works for me. The only thing that doesn't work is fingerprint sign-on. When I enable that in Chase Pay, it complains that the devices is rooted, and will not enable this feature. The rest of the app seems to work, however. If anyone finds a solution to that issue, please share.
I also have no issues with Android/google pay but chase pay is giving the root error.
I have done steps 1-6 without chase pay working properly. Is there any way to check the chase pay error log and see where it is getting stopped?
I don't think I have ever rooted my Galaxy S7 and I don't even know how.
But I am getting rooted/Malware error with Chase Pay ( I can login but does not let me pay)
I checked with couple applications such as root checker and safteynet and both say that I am not rooted and my phone pass the safety test. Anyone know what the problem is? and how to fix it?
Chase Pay is also saying my phone is rooted. I get beyond the intro so Magisk hide is working to some degree. After that when tapping the pay button is when I get the error.
Tuxedo.Bond said:
Chase Pay is also saying my phone is rooted. I get beyond the intro so Magisk hide is working to some degree. After that when tapping the pay button is when I get the error.
Click to expand...
Click to collapse
Did you hide Magisk Manager (in Magisk Manager>Settings) before setting up Chase Pay?
Screenshot of the settings after hiding by the Manager attached.
Sent from my OnePlus3T using XDA Labs
Yes, hiding Magisk Manager did the trick. Thanks!
BillGoss said:
Did you hide Magisk Manager (in Magisk Manager>Settings) before setting up Chase Pay?
Screenshot of the settings after hiding by the Manager attached.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Hi
So I am about to try the same path for the NAB app. From reading the thread I need to
Magisk Manager
Hide for the app
hide the manager
clean the nab app data/cache
reboot
then start the NAB app'
tried that but app keeps crashing on attempting to create nab pay
EDIT
tried removing data/cache again - seemed to work.
So what happens if I unhide magisk manager ???
KeyzerSuze said:
Hi
So I am about to try the same path for the NAB app. From reading the thread I need to
Magisk Manager
Hide for the app
hide the manager
clean the nab app data/cache
reboot
then start the NAB app'
tried that but app keeps crashing on attempting to create nab pay
EDIT
tried removing data/cache again - seemed to work.
So what happens if I unhide magisk manager ???
Click to expand...
Click to collapse
If you unhide the manager, then NAB pay will stop working if you reboot.
I've also found that even with everything hidden, NAB pay will stop working after some time (a week?).
I've switched to Google Pay which works a lot better and doesn't require hiding the manager.
Sent from my OnePlus3T using XDA Labs
Didgeridoohan said:
You don't mention anything about hiding the Manager. Does that make a difference?
Click to expand...
Click to collapse
Thank you!
This is annoying the hell out of me. I can't get Chase Pay to work. I've gone into Titanium backup and deleted the data for the app. Went into app settings and deleted the storage & cache for the app. Made sure the app is hidden in Magisk and made sure Magisk is hidden. Rebooted phone and still says the app is detecting root. What am I doing wrong?
defens23 said:
This is annoying the hell out of me. I can't get Chase Pay to work. I've gone into Titanium backup and deleted the data for the app. Went into app settings and deleted the storage & cache for the app. Made sure the app is hidden in Magisk and made sure Magisk is hidden. Rebooted phone and still says the app is detecting root. What am I doing wrong?
Click to expand...
Click to collapse
Are you on Magisk 17.1 and have your removed the Magisk folder from your user storage (/sdcard)?
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Are you on Magisk 17.1 and have your removed the Magisk folder from your user storage (/sdcard)?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Yes. I'm on 17.1. No I didn't delete the folder. I'll try that.
defens23 said:
Yes. I'm on 17.1. No I didn't delete the folder. I'll try that.
Click to expand...
Click to collapse
Delete the folder, delete the Chase app storage, reboot.
Sent from my OnePlus3T using XDA Labs