So the thing was the secure folder app and the samsung pay app and health app is saying I have root even though i never installed root, and even checked if i have root via root checkers saying that i have no root... how do i fix this???
Did you install a different ROM?
DarkerJava said:
Did you install a different ROM?
Click to expand...
Click to collapse
i haven't installed any rom but I did retrieved the old bootloader [ I changed to s8 boot loader but came back to the original boot loader (backup) ]
It appears that any modifications you've made in the past have left behind "pieces" or corpse folders/files. I have a 930F and in order to use banking apps, payment apps, etc. I had to use Magisk (hides from newer apps quite well). NO superuser or su framework can be present (apps see it right away and su doesn't hide well on new devices / apps). So I believe that there is a remnant or file related to root triggering the warning msg you are seeing. My advice would be to flash fresh firmware (also a full wipe).
*Sometimes changes made related to root (even if you don't have root) can trigger apps/system warnings even though you didn't root.
JOHN.WAYNE said:
It appears that any modifications you've made in the past have left behind "pieces" or corpse folders/files. I have a 930F and in order to use banking apps, payment apps, etc. I had to use Magisk (hides from newer apps quite well). NO superuser or su framework can be present (apps see it right away and su doesn't hide well on new devices / apps). So I believe that there is a remnant or file related to root triggering the warning msg you are seeing. My advice would be to flash fresh firmware (also a full wipe).
*Sometimes changes made related to root (even if you don't have root) can trigger apps/system warnings even though you didn't root.
Click to expand...
Click to collapse
Would this affect major os update? and how do I remove remnant/corpse files
Related
It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.
My goal is to COMPLETELY get rid of any root files / SuperSu files that are located on my device without having to reformat. Couple months ago i managed to install SuperSu and gained root and I did my own cleanup of bloatware apps and whatnot. Since then I have deleted SuperSu by going into the settings of SuperSu and clicking on the "Clean Root" option but without doing the original boot files option. Doing so, the phone reboots, cleans up , deletes SuperSU and i no longer have root. This is great and all but just one problem reminds.....
I can no longer play Pokemon GO because of the newest update that came out yesterday since it checks for rooted devices. Is there a way to completely remove all the files that are associated with the root process / SuperSU so that I can play this game. I have tried to use the app "SafetyNet Helper" to check for Google's SafetyNet CTS tests and it fails after i tried uninstalling SuperSU. I have heard of the Magisk app but it looks like you need a unlocked bootloader to install it.
Is there a way to get my phone back to the original state without reformatting my phone through Odin. At the end of the day, yes, i would rather have a rooted device than to play Pokemon GO but say what you will but this game has gotten me out, walking around my town, being social and actually making friendships.
Thanks for any help in advance,
Just go here. http://forum.xda-developers.com/tmo...ow-to-unroot-to-stock-o-loosing-data-t3445573
I want to have fb messenger in ultra power saving mode (UPSM). for that i need to use the UPSM Manager app which requires root. I really do not like to root, because more and more apps are blocking rooted devices (Barclays banking, android pay, pokemon go). So I am asking if there exists some methods for gaining temp root (e.g. with adb). so i can install and use upsm-m once and then reboot and root is gone. It is important that the flag is not flipping.
Thank you for all your help
Shiro
Nope, and even if you could, the app would fail as soon as root was removed
*Detection* said:
Nope, and even if you could, the app would fail as soon as root was removed
Click to expand...
Click to collapse
I expected that, on my old htcs there were temp roots available.
But the failing of the app after removing root, is not a problem. The app is just a configfile creator. Since the config file has changed, the app is not needed anymore.
Earlier today I successfully rooted my phone and uninstalled a bunch of bloatware. Foolishly, I also uninstalled the Samsung keyboard (figuring I only use the Swype keyboard) which I now suspect it is used to enter my pin when turning the phone on. Now I can't get past the pin entry because the keypad does not show up. Is there anyway to reinstall the app in this situation?
trusko1 said:
Earlier today I successfully rooted my phone and uninstalled a bunch of bloatware. Foolishly, I also uninstalled the Samsung keyboard (figuring I only use the Swype keyboard) which I now suspect it is used to enter my pin when turning the phone on. Now I can't get past the pin entry because the keypad does not show up. Is there anyway to reinstall the app in this situation?
Click to expand...
Click to collapse
You can get a copy of the .apk file and then boot to TWRP, then use adb to sideload the .apk to /system/app or /system/priv-app (wherever it was at before you deleted it).
Or you can reflash your stock firmware or custom ROM if you're using one.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I flash magisk.zip but it is normal app not system app
Magisk is a 3rd-party-app. Take note that a system-app is necessary part of Android OS. And Magisk isn't.
jwoegerbauer said:
Magisk is a 3rd-party-app. Take note that a system-app is necessary part of Android OS. And Magisk isn't.
Click to expand...
Click to collapse
Not quite right, when a 3rd party user app is installed or pushed to system, it then becomes a system app. The term "system app" refers to any app that is in the system partition, it has nothing to do with whether the app is a necessary part of the OS. Stock system apps, or, at least, "some" of them can be considered to be necessary parts of the OS but this isn't completely true because a lot of devices come pre-installed with non essential bloatware apps in the system partition. These non essential bloatware apps can be removed via root or by adb on non rooted devices because they are not necessary parts of the system.
For me a "system app" is - as already mentioned - an app that comes pre-installed in Android ROM's one of the partitions /system/app or /product/app or /product/overlay or /vendor/app, is a "system app" an app that is intended for the functioning of the Android device.
Your admission to this view of mine does not change my opinion.
private app is also a system app but seems to be an add-on. and i flashed the zip but it was not set as a system app, it seems the zip is not related to install like the system in twrp, and twrp mounted the system but couldn't delete any folder in. rooted but so bad!
Hi,
Hope you can help, if I root with super su for just change build pro settings, and then full unroot, will I keep the changes?? Or there is a another way to change build prop variable without root? I'm in G930F Nougat stock rom
Thanks
Yes the changes will remain if you unroot but why would you? You have already tripped KNOX etc by rooting in the first place, and your system status will remain 'Custom', so things like banking apps will likely still fail to work
No you can't change system files without root, build.prop is a system file
*Detection* said:
Yes the changes will remain if you unroot but why would you? You have already tripped KNOX etc by rooting in the first place, and your system status will remain 'Custom', so things like banking apps will likely still fail to work
No you can't change system files without root, build.prop is a system file
Click to expand...
Click to collapse
Thanks you so much for your answer, it's exactly because some video apps and banking as you said not work with root and they are essential for me. The problem is, I'm root since a long time, s health just work editing build prop, and since a few months ago, some apps like my bank, and video apps stop working because of root, and I need both things now, and I remember that before root(with already Knox tripped) they work fine.
speechgotham3 said:
Thanks you so much for your answer, it's exactly because some video apps and banking as you said not work with root and they are essential for me. The problem is, I'm root since a long time, s health just work editing build prop, and since a few months ago, some apps like my bank, and video apps stop working because of root, and I need both things now, and I remember that before root(with already Knox tripped) they work fine.
Click to expand...
Click to collapse
AFAIK, these apps just don't open anymore because of the SafetyNet profile missmatch you get when rooted (You can download an app like "SafetyNet Helper Sample" from Play Store to view your current SafetyNet status).
Apps like Snapchat, PokemonGO, my local banking app,.. use this technology, rather than the "custom" mark or the tripped knox.
So in my opinion you have three options now:
Use Magisk
When rooted with MagiskSU, your phone will still pass the SafetyNet Profile match, which will let you use your apps and root.
Root -> make your changes -> unroot
When you're completely unrooted you will once again pass the SafetyNet
(Probably doesn't work for you)Unroot -> Prepare Apps -> root again
Apps like Snapchat just check your SafetyNet status at login. That means when you're not rooted, you can log in to Snapchat, when you root afterwards (without a wipe of course) you're still logged in, even tho your phone wouldn't pass SafetyNet atm.
jaannnis said:
AFAIK, these apps just don't open anymore because of the SafetyNet profile missmatch you get when rooted (You can download an app like "SafetyNet Helper Sample" from Play Store to view your current SafetyNet status).
Apps like Snapchat, PokemonGO, my local banking app,.. use this technology, rather than the "custom" mark or the tripped knox.
So in my opinion you have three options now:
Use Magisk
When rooted with MagiskSU, your phone will still pass the SafetyNet Profile match, which will let you use your apps and root.
Root -> make your changes -> unroot
When you're completely unrooted you will once again pass the SafetyNet
(Probably doesn't work for you)Unroot -> Prepare Apps -> root again
Apps like Snapchat just check your SafetyNet status at login. That means when you're not rooted, you can log in to Snapchat, when you root afterwards (without a wipe of course) you're still logged in, even tho your phone wouldn't pass SafetyNet atm.
Click to expand...
Click to collapse
Thanks my friend I will try, because now I'm root with Magisk and with Magisk hide and does not work even with safety net pass
speechgotham3 said:
Thanks my friend I will try, because now I'm root with Magisk and with Magisk hide and does not work even with safety net pass
Click to expand...
Click to collapse
Which version of Magisk are you using?
What is the result of the SafetyNet Sample App?
jaannnis said:
Which version of Magisk are you using?
What is the result of the SafetyNet Sample App?
Click to expand...
Click to collapse
The latest one
Attach you an image
Thanks for your help
speechgotham3 said:
The latest one
Attach you an image
Thanks for your help
Click to expand...
Click to collapse
You could try installing the newest beta, which is 13.6, but I don't really believe this resolves your problem. You can get it from here: Magisk Beta Thread