I upgraded S6 Edge to G925PVPUDQC7, and rooted using CF-auto-root. Worked fine. But my GTv3.1.5 would no longer "enable the native hotspot". What seems to be wrong? Thanks!
ratneshsudha said:
I upgraded S6 Edge to G925PVPUDQC7, and rooted using CF-auto-root. Worked fine. But my GTv3.1.5 would no longer "enable the native hotspot". What seems to be wrong? Thanks!
Click to expand...
Click to collapse
having the same issue ever since the nougat update please help
I got this Sprint s6 Edge already on Nougat, rooted thru CF-Auto, And have issues with GT as well...
I dk if it's because of the "System-less" root thing, or because of the DM-Verity in the stock kernel, or what... I've been out of the Developmental Loop for quite a while.... But I verified root, binaries, use other root apps, etc.... GR8 still indicates what binary is installed YET STILL claims the device isn't rooted... here are screenshots...v
Related
hi.
i had a rooted nexus s since 2.3.2
had superuser, installed a lot of rom's, no problem.
now i have 4.1.1 that i installed through google's update, the lock on startup is still open.
but application that need rooted devices say to me that mine is not rooted!
i tried to root it again with this http://forum.xda-developers.com/showthread.php?t=1544940
it all went great, but still, apps that need a root won't work.
what should i do?
gania13 said:
hi.
i had a rooted nexus s since 2.3.2
had superuser, installed a lot of rom's, no problem.
now i have 4.1.1 that i installed through google's update, the lock on startup is still open.
but application that need rooted devices say to me that mine is not rooted!
i tried to root it again with this http://forum.xda-developers.com/showthread.php?t=1544940
it all went great, but still, apps that need a root won't work.
what should i do?
Click to expand...
Click to collapse
try using an updated superuser and don't use this section of the thread when asking questions..
you should use CWM to flash superSU.
You will need SuperSU instead of SuperUser.
Sent from my Nexus S©
Closed due to opening multiple threads on the same issue
So I have tripped KNOX already. I'm using TWRP, Xstrolite 2.3.
I've tried unchecking superSU root and retrying. I've tried using root cloaker.
Is there an easy way to not have the bootloader unlocked? Or is it once I flashed TWRP, its unlocked forever.
Has anyone else been able to successfully use Android Pay? Post your experience
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
derwreck said:
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
Click to expand...
Click to collapse
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
tlxxxsracer said:
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
Click to expand...
Click to collapse
I also changed the build prop to reflect my SM-G920F model. I really wish I could get Android Pay to function on this device, I tripped KNOX with the full understanding that I was going to lose the ability to use Samsung Pay but never did I imagine that using a custom ROM would cause me to compromise Android Pay as well. I purchased an international unlocked model of the S6 so naturally, the bootloader was unlocked from the factory, I don't know if having an unlocked bootloader necessarily causes you to lose Android Pay. It either has to be due to the fact that we're running a custom ROM, custom recovery, or because KNOX is tripped and it's preventing AP to run like it should.
Try installing the stock rom for your phone. Then under supersu simply uncheck root and see if adding the cards work
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Infekxion said:
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Click to expand...
Click to collapse
When you said you unrooted.. did you uncheck the root box in SU app or uninstalled all together and then reinstalled?
Full unroot under the Cleanup section
Sent from my SM-G920F
think its reading something in the buildprop similar to how google wallet did.
i also tried modifying a few things in build prop to show official firmware nomenclature to no avail.
Infekxion said:
Full unroot under the Cleanup section
Sent from my SM-G920F
Click to expand...
Click to collapse
After you did full unroot. did you reboot? and to reinstall root, you flashed zip again? or what
After unrooting within SU app I just activated my card then reflashed the zip in recovery.
Sent from my SM-G920F
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
rob219 said:
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
Click to expand...
Click to collapse
What rom are you on?
Sent from my SM-G920F
Infekxion said:
What rom are you on?
Sent from my SM-G920F
Click to expand...
Click to collapse
XtreStoLite 1.5 on att
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Mrzoops said:
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Click to expand...
Click to collapse
So i did a fresh install but with Tyrannus rom 5.1, it runs the same base as Xstolite (I believe)
I got android pay working on tyrannus rom 5.1
maybe try backing up your current setup, wipe and flash the rom and first thign you do is try android pay and see if it works. Thats what I did on the rom im running now
I got it working on Tyrannus as well...briefly...although I am not sure how I did it.
Currently on XtreStoLite 2.3, using Xposed + No Device Check and an app called SafetyNet Helper...it says my device is good to go, but Android Pay won't work still.
I hope someone is able to pinpoint what prevents it from working and how to spoof it. I tend to have my phone in my hands a lot more than my wallet.
K, got it working. Fresh install of Tyrannus 5.1, did NOT install Xposed. Immediately turned SU off after 1st boot, before updating Google Play Services. Was then able to activate Android Pay and add cards.
Update 20150924: tried to use it at McDonalds for tap and pay. Android Pay started when tapped but never completed the transaction and I had to use my card.
Today my apps were acting weird so i went to my superSU and it said
"there is no SU binary installed, and superSU cannot install it. This is a problem!"
Seems like I've tried everything to fix this problem. Flashed stock rom using Odin, reflash CF-root after that. Tried installation custom recovery (can't flash using recovery because my phone is encrypted unless there's a way to by pass that). Used different cords, ports, versions of odins. Still nothing. Had this problem since the morning it's now 8pm here so i decided to ask.
Anyone know how to fix this issue?
Hey, is there anyone who solved the problem ? I got the same issue with my brand new Galaxy S7, quite anoying ...
So have i with my S6. No cure so far, tried everything. Waiting for chainfire to jump in...
Verstuurd vanaf mijn SM-G920F met Tapatalk
I have also just experienced this. Everytime I try to remember root and run root checker it says not rooted.
try root with twrp and a kernel like "adam kernel" or a nearly stock one. Then try flash form recovery supersu 2.74
Ive got the same issue. I have G920i stock 6.0.1 rom and stock kernel and rooted using cf-root. However today i noticed my device is not rooted anymore. Also a week ago my phone completly froze and i had to go to download mode and reboot the device. Im not really sure if this incident was related for the device to become unrooted. Any help is appreciated
Same problem! I rooted my galaxy s7 with cf-root and odin and it worked fine for a while until I got no root privileges and had to reroot it. It worked once more and again - unrooted by itself, only this time rooting doesn't work! it says that it roots it but when I check supersu, it says no SU binary. Please someone help!
same issue
deveice is s6 and china version.
I just bought it one week
wait the solution.
Strange, same thing just happened to me today in Samsung S7. Phone restarted on its own and now no root access. I had it rooted like 2 months ago with Cf and Odin and had been working fine. What happened??
same here , S6 G920F... lost all access from rooted apps tried re-root with odin , also installing supersu again and again , deleted also all the required-rood apps ... nothing works
Hey guys this is already solved. Samsung pushed a security policy update that broke the root. So now the way to go is that you need to flash stock rom with odin. I used smart switch which is easier and worked too. Then after you have stock rom you root using the new cf-auto root by chainfire. Enjoy.
LAUNCHERMONKEY said:
Today my apps were acting weird so i went to my superSU and it said
"there is no SU binary installed, and superSU cannot install it. This is a problem!"
Seems like I've tried everything to fix this problem. Flashed stock rom using Odin, reflash CF-root after that. Tried installation custom recovery (can't flash using recovery because my phone is encrypted unless there's a way to by pass that). Used different cords, ports, versions of odins. Still nothing. Had this problem since the morning it's now 8pm here so i decided to ask.
Anyone know how to fix this issue?
Click to expand...
Click to collapse
This happened to me today, I fixed by restoring to stock using smart switch and then using cf-autoroot to re root.
I had same problem
r00tkiller said:
Hey, is there anyone who solved the problem ? I got the same issue with my brand new Galaxy S7, quite anoying ...
Click to expand...
Click to collapse
Basically I just fixed it by reflashing my ROM straight on top of my old ROM (ressurection remix) I did not wipe cache or dalvik just straight reflashed ROM and it fixed it
Nothing else I tried worked not sure if I will get the same error again but it worked for now
Plus I had error previously with su binary update think this is the cause
Hey guys!
I'm wondering if anyone else is having a problem with MirrorShare working in the latest update. I just recently tried using it and nothing is showing up for me to connect to. This is very disappointing. If anyone has gotten this to work, I appreciate any advice.
BTW: I'm rooted with TWRP custom recovery and I have xposed installed as well.
Thanks!
Here! But MirrorShare is not the only thing in B571. GPS is also f****d up after the latest update. Also some of my apps stopped working and can't be opened.
I am not rooted and have no unlocked bootloader.
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
FallenArchangel7 said:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
Click to expand...
Click to collapse
Remove s health and install like a normal app a older version.
Enviado do meu SM-G930F através de Tapatalk
Basically, what vladmir said. S-Health disables services if you're rooted starting from version 5, so any previous versions will not have this problem. Just Google S-health APK 4.9 or something like that, and install.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306 Works well thanks to CuBz90
FallenArchangel7 said:
I have the Exynos S7 Flat (G930FD) and I'm wanting to root it.
I've done this before about a year ago, but then I ended up getting a new device.
Since then, apparently SHealth now requires KNOX, which rooting will trip.
Is there any way I can bypass this? Perhaps a custom ROM or something? I know there used to be an Xposed module that restored private mode and something else, but I don't think it works anymore.
Basically I want to have root access as well as to be able to use S Health.
Click to expand...
Click to collapse
I'm running Sheath on multiple devices all with Rooted Custom Roms that are AOSP / LineageOS based....
The interesting thing is that Sheath won't run on a Stock Rooted TW Rom
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
I'm running Sheath on multiple devices all with Rooted Custom Roms that are AOSP / LineageOS based....
The interesting thing is that Sheath won't run on a Stock Rooted TW Rom
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
It works just fine on Marshmallow, but if you upgrade to Nougat then you need a custom ROM to make it work.
Removing it and installing it as a non-system app doesn't seem to change anything, and installing an older version didn't help me either.
I've downgraded to 6.0.1 so it doesn't really affect me any more though.
It is very simple to make SHealth working.
First root your device with Magisk using this thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk is able to hide itself from a lot of apps, which won't run if your phone is rooted (i.e. Pokemon go, Mario run...)
If Magisk won't help you then:
install file explorer, it can be ES file explorer,
enable root explorer option (in ES file explorer)
go to /system directory
edit file build.prop
Look for ro.config.tima=1 and change the value to 0
reboot phone and now SHealth will work perfectly