I tried using Google Pay yesterday, but apparently my S7 Edge doesn't pass the Safetynet tests. Running stock is not an option because my tripped Knox breaks Samsung Health and I can't use my Gear S3. Safetynet is currently failing at CTSProfile.
Is there an app, kernel or rom that can fix these issues? I don't really need Knox to work (though SPay would be nice to have), I just want my Gear and GPay to work. Im running GalaxyRom, which is TouchWiz with some modifications to fix some Knox issues. Magisk is only used for root browser. Would rather not flash another ROM, but if there is one that fixes these issues its better than nothing.
Thanks
Magisk + Custom ROM
magisk v17.1
I'm using stock ROM with Magisk v17.1, and passing all safetynet checks. have you tried safetynet bypass apps?
vinegarr said:
I tried using Google Pay yesterday, but apparently my S7 Edge doesn't pass the Safetynet tests. Running stock is not an option because my tripped Knox breaks Samsung Health and I can't use my Gear S3. Safetynet is currently failing at CTSProfile.
Is there an app, kernel or rom that can fix these issues? I don't really need Knox to work (though SPay would be nice to have), I just want my Gear and GPay to work. Im running GalaxyRom, which is TouchWiz with some modifications to fix some Knox issues. Magisk is only used for root browser. Would rather not flash another ROM, but if there is one that fixes these issues its better than nothing.
Thanks
Click to expand...
Click to collapse
painx said:
Magisk + Custom ROM
Click to expand...
Click to collapse
"Custom ROM" is pretty vague. I have a custom TouchWiz ROM that doesn't work.
Try ' SecurityLogAgent Disable' on the Google Play store. I am using a stock ROM with the latest version of Magisk and passing all safety checks. I'm also using android pay and banking apps without an issue.
I was having the same problem. Bounced from one ROM to the next, but ultimately found my solution back where I started. I got SafetyNet passing with Samsung Health working on Sac23's s9 port. Unfortunately, he took down the rom so you can't download it from his thread. If you still wanna try it though, you can PM me and I'll share more info.
Rehvix said:
I was having the same problem. Bounced from one ROM to the next, but ultimately found my solution back where I started. I got SafetyNet passing with Samsung Health working on Sac23's s9 port. Unfortunately, he took down the rom so you can't download it from his thread. If you still wanna try it though, you can PM me and I'll share more info.
Click to expand...
Click to collapse
Thanks for the suggestion. I used SacĀ“s ROM before so I think I still have the ROM on my PC. I did flash back to stock, though. If I recall correctly, it had some weird issues (since its a port). Thanks, tho.
Rehvix said:
I was having the same problem. Bounced from one ROM to the next, but ultimately found my solution back where I started. I got SafetyNet passing with Samsung Health working on Sac23's s9 port. Unfortunately, he took down the rom so you can't download it from his thread. If you still wanna try it though, you can PM me and I'll share more info.
Click to expand...
Click to collapse
Thanks for the suggestion. I ended up flashing the BlackPearl S9 Port and Safetynet passes just fine. No issues with Knox either.
Related
Hi there, I'm no new to development, but haven't played with a phone in a while.
Can someone please tell me what the disadvantages of rooting the Nexus 6p are?
My plan is to get root access only to use specific apps (eg greenify) but not to install a new ROM, i.e. I'll stay with stock.
Does this affect:
-Applicability of OTA updates from Google
-ability to use the fingerprint reader
-warranty claims
-speed/stability of the device?
Thanks in advance!
qwertyuiop89 said:
Hi there, I'm no new to development, but haven't played with a phone in a while.
Can someone please tell me what the disadvantages of rooting the Nexus 6p are?
My plan is to get root access only to use specific apps (eg greenify) but not to install a new ROM, i.e. I'll stay with stock.
Does this affect:
-Applicability of OTA updates from Google
-ability to use the fingerprint reader
-warranty claims
-speed/stability of the device?
Thanks in advance!
Click to expand...
Click to collapse
-OTA are not possible when rooted. You have to flash back stock boot.img and recovery.img to accept an OTA.
-It does not interfere with Nexus Imprint (Fingerprint reader.)
-Does not affect speed or stability
-Warranty is not affected because you can flash stock imgs and relock bootloader.
You can take OTA's if you do the systemless-root. I believe you would have to flash the recovery back to stock, though.
I think you have to flash boot as well since it's modified.
the biggest disadvantage is your device become instantly awesome, so if you are used to being annoyed about the stock OS missing features this is hard to deal with
But honestly the best thing about owning a nexus is you can root and easily go back to stock if you change your mind. The flash images are also easily available for updates (even before the OTA is out). So play with it, and worst case you can always restore back to stock.
currently my only disadvantage to me is loosing android pay...
yea i know i can make it work if i delete /su/xbin... but i feel like its there for a reason and i shouldnt be deleting it.
chaco81 said:
currently my only disadvantage to me is loosing android pay...
yea i know i can make it work if i delete /su/xbin... but i feel like its there for a reason and i shouldnt be deleting it.
Click to expand...
Click to collapse
Supersu 2.61 does systemless root ootb. No need to delete anything. Systemless root will just work and Android Pay will just work.
83097markcynt said:
Supersu 2.61 does systemless root ootb. No need to delete anything. Systemless root will just work and Android Pay will just work.
Click to expand...
Click to collapse
i have been using systemless root since v 2.61... im using 2.66 now
and android pay didnt work, and even wont pass safetynet test
delete the /su/xbin folder and it passes safetynet and android pay works...
so yes, for me it sucks that i have delete that to make AP to work... which is why for now i am giving up AP since i dont feel comfortable deleting xbin and breaking stuff
Mine passes safetynet test and is just systemless with nothing deleted. No Android Pay in the UK to test it with though.
Not being awesome.
Not living in the exciting XDA fast lane!
Can I use Xposed with systemless root?
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
dimiboy said:
Can I use Xposed with systemless root?
Click to expand...
Click to collapse
Yes mate you can works perfectly well
Sent from my Nexus 6P using Tapatalk
qwertyuiop89 said:
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
Click to expand...
Click to collapse
lol this seems to happen when you root and install Xposed or pretty much modify anything. Usually I see a decrease in stability and battery life but an increase in performance, and you get to play with new features early.
I'm contemplating rooting just to use the new launcher.
qwertyuiop89 said:
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
Click to expand...
Click to collapse
You have a couple of things going on.
First root IS as safe as you let it be. If you haven't installed any root applications it should not be any more buggy than stock.
You have installed Xposed. You have not mentioned what modules you have.
I don't have any issues you describe but I don't have a lot of modules installed.
I am stock with Xposed and root.
None
Sent from my angler using XDA Labs
Got my S7 Edge SM-935W8 Installed TWRP, CF Auto root and xposed. Before i did that i used the stock phone for a day. FASTEST PHONE IVE EVER USED. NOTHING COMES CLOSE TO THE PERFORMANCE OF THIS PHONE OUT OF THE BOX. THIS IS NOT A POsT TO BASH THE S7 EDGE
Off the go xposed did not work well. Bootlooped every other restart and added a lot of time to startup.
Modules I installed:
Boot Manager
BubnleUpNp
Clean Lockscreen
Custom Share
Dynamic AlarmIcon 2
Flatstyke bar indicator
Flatstylekeyboard
Gravitybox
Greenify
Luckypatcher
RootCloak
Smooth system progress bar
XGPM
Xinstaller
Xprivacy
Xprivacy in app info
Xtouchwhiz
Was it easy to root?what method did you follow please?only rooted once and was nexus 6p never rooted another?cheers
So does that mean you are going to flash back the stock ROM. I'm undecided on whether to root or not. I've been jailbreaking since the first iPhone, and the S7 edge is my first ever android device. I must say I can do almost everything I used to on jailbreak but with a lot less effort.
Sent from my SM-G935F using Tapatalk
I have the same config, except I obtained root with TWRP + SuperSU.
Runs better than Stock, and No Reboots.
Are you sure you got the correct Xposed version ? (Arm64, SDK 23)
Out of the box, First thing I did was Power up in bootloader, Flashed TWRP. Root is a must for me.
A little confused as to the OP? What exactly are you stating or trying to convey?
chippyuk said:
A little confused as to the OP? What exactly are you stating or trying to convey?
Click to expand...
Click to collapse
Me too, can't work out if he is saying it was better before or after root and exposed??
After i install Xposed framework, as jazonX states (Arm64, SDK 23) , my phone won't boot anymore and i am forced to
reinstall stock image. what am i doing wrong ?
Thanks!
dsbarry said:
After i install Xposed framework, as jazonX states (Arm64, SDK 23) , my phone won't boot anymore and i am forced to
reinstall stock image. what am i doing wrong ?
Thanks!
Click to expand...
Click to collapse
Use Xposed from here: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
This is specifically made for TW devices, because Samsung makes modifications to ART and other things that break the normal Xposed. I installed it on my S7e and it works like a charm
ssrij said:
Use Xposed from here: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
This is specifically made for TW devices, because Samsung makes modifications to ART and other things that break the normal Xposed. I installed it on my S7e and it works like a charm
Click to expand...
Click to collapse
you sir, are a lifesaver!
thank you so much!
Sorry half the post was removed....
Anyways I wrote this because if you go far enough to trip Knox you aren't going to want to run stock TW. With the features this phone has I can't see myself running cm or a AOSP distro if I lose out on the hardware's capabilities. For a thousand dollar phone the price tag doesn't meet the performancs running stock with root and xposed.
I used wanams custom Xposed v80 x64. The TWRP exynos version and Cf-root. This version of Touchwhiz is 8gb. There is ALOT of RAM usage on the device stock. With Xposed framework on top the device is lagging behind what it should be.
I'm dying to get a custom TW running because this device is a beast but there is to much on top of the essentials that are holding back the s7.
If you are thinking of going the mod route you should not use stock. When the time comes flash a custom TW.
JazonX said:
I have the same config, except I obtained root with TWRP + SuperSU.
Runs better than Stock, and No Reboots.
Are you sure you got the correct Xposed version ? (Arm64, SDK 23)
Out of the box, First thing I did was Power up in bootloader, Flashed TWRP. Root is a must for me.
Click to expand...
Click to collapse
did your 0x0 became 0x1 after rooting?
mindstorms54 said:
did your 0x0 became 0x1 after rooting?
Click to expand...
Click to collapse
Ofcourse its gonna trip knox
mindstorms54 said:
did your 0x0 became 0x1 after rooting?
Click to expand...
Click to collapse
Yeah, 0x1 now.
Wasn't a big deal for me, as this is probably the sixth phone I had with Fort Knox.
I wanna start playing with this thing but Sam mobile doesn't have our firmware up yet.
Any other firmware I can use to reflash stock if I run into trouble playing with this thing?
I'm also on the w8 variant and like to have everything on my laptop before I make the leap
Sent from my SM-G935W8 using Tapatalk
jlomoro said:
I wanna start playing with this thing but Sam mobile doesn't have our firmware up yet.
Any other firmware I can use to reflash stock if I run into trouble playing with this thing?
I'm also on the w8 variant and like to have everything on my laptop before I make the leap
Sent from my SM-G935W8 using Tapatalk
Click to expand...
Click to collapse
You shouldn't need another. With Odin you can flash the recovery again if it fails but after you have a recovery you can just factory reset it and it well go back to default. Go to the TWRP EXYNOS thread and follow his steps. Its a smooth process
Thanks for the reply Benny, that won't work if I want to experiment with the custom rom available tho will it.
Sent from my SM-G935W8 using Tapatalk
jlomoro said:
Thanks for the reply Benny, that won't work if I want to experiment with the custom rom available tho will it.
Sent from my SM-G935W8 using Tapatalk
Click to expand...
Click to collapse
Download Nandroid manager and online Android backup. Your gonna have to get TWRP and root
Make a backup and save it to your SD card. Copy it somewhere safe, and make sure you can flash it if anything goes wrong.
Or you can hold off and wait for Sam's mobile. In due time it will have a stock image for your provider
Hi Benny, it's awesome you got it all working. I have same model of the S7 Edge. I am rooted, however I didn't install TWRP yet, because I was confused about the instructions in the "exynos twrp" thread.
Did you glad the "dm-verity- disabler "? I'm not sure what that does, but it was part of the instructions. Also did you do a factory reset when flashing twrp? Because my phone is all setup up now, I don't want to do a factory reset to get twrp.
Please advise
before i root i need to make sure sammy can resolve all 6.0.1 issues, mainly crappy 3d gaming performance. happens on ALL 6.0.1 devices, on Note 5 running angry birds 2 for 5 minutes results in awful lag and stuttering same with s7e, however 5.1.1 Note 5 runs it perfect!!!
i mainly play ppsspp emulator and angry birds 2, and this stupid bug must be resolved!
MUTAN3F said:
Hi Benny, it's awesome you got it all working. I have same model of the S7 Edge. I am rooted, however I didn't install TWRP yet, because I was confused about the instructions in the "exynos twrp" thread.
Did you glad the "dm-verity- disabler "? I'm not sure what that does, but it was part of the instructions. Also did you do a factory reset when flashing twrp? Because my phone is all setup up now, I don't want to do a factory reset to get twrp.
Please advise
Click to expand...
Click to collapse
That file removes the encryption on internal storage. It's required if you wish to have TWRP have read write access to the internal storage. Wichita is required if you plan on using custom rom in the future.
I'm thinking what you could do (which is what I'm gonna do) is flash the auto root method. Then do a full backup with titanium to sd card. Then install TWRP and do full wipe and no diversity script and TWRP root method.
Then reload my titanium backup.
Think this will best of both worlds as I'll have read write access and won't lose all my data.
Can anybody confirm or correct me on my thinking here?
Sent from my SM-G935W8 using Tapatalk
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
I've read this:
Downgraded to 6.0.1. stock. Started SHealth, and again upgraded to Nougat.
databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70712537&postcount=16
databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
You could flash a custom ROM with Magisk installed to have everything working including AndroidPay
Magisk Bypasses Safteynet
Im currently using Superstock Rom and its great ... Playing PokemonGo, using banking apps and AndroidPay on a daily basis.
(and yes Shealth works)
EasyAndroidPro said:
You could flash a custom ROM with Magisk installed to have everything working including AndroidPay
Magisk Bypasses Safteynet
Im currently using Superstock Rom and its great ... Playing PokemonGo, using banking apps and AndroidPay on a daily basis.
(and yes Shealth works)
Click to expand...
Click to collapse
I've had exactly zero luck with Magisk in the past, albeit that was before the proper W8 firmware came out so I was also fighting through issues of using improper firmwares (which have just never worked quite right for me; it seems our Canadian W8's aren't just a CSC change from the F). I was also having problems accessing my carrier's resources, etc. Maybe it's fixed, but my goal was to go back to 100% stock (or as close to as possible). I guess I'm just finally giving up my flashing addiction for the time being.
mashardpro said:
I've read this:
Downgraded to 6.0.1. stock. Started SHealth, and again upgraded to Nougat.
Click to expand...
Click to collapse
Yep worked. Thanks; anyone looking for the updated solution this is certainly one. It did suck to not be able to use Google's app restore function though (as my Nougat backup didn't register as usable on Marshmallow). But I'm up and running and SHealth is happily purring away.
webjunky said:
https://forum.xda-developers.com/showpost.php?p=70712537&postcount=16
Click to expand...
Click to collapse
Thanks, but this had to be crossed with the recommendation above. I was mostly looking to see if there had been an update that I missed.
Hi. is there any basic step by step guides for getting f the latest also extended ROM on my stock oneplus 3t.
Use to do it may y years ago and have lost / forgot everything lol. Also wondered if possible is it able to be rooted and still have access to banking apps using that ROM.
Cheers and apologies in advance
Best guide I've found
https://www.xda-developers.com/unlock-twrp-and-root-the-oneplus-3/
Used this earlier this evening. Simplest guide I've found and works fine for op3t, even though it's written for op3. Also replaced supersu with magisk zip with no difficulties.
Thanks for that. I will look at it tomorrow and attempt it. Did you replace SuperSU during the rooting or after? Read a few ways to do it so just wondered. Is it true that magisk is the way to get android pay and back king aps to still function with root?
Cheers
luke.douthwaite said:
Thanks for that. I will look at it tomorrow and attempt it. Did you replace SuperSU during the rooting or after? Read a few ways to do it so just wondered. Is it true that magisk is the way to get android pay and back king aps to still function with root?
Cheers
Click to expand...
Click to collapse
Didn't flash SuperSU at all. Tried installing magisk at the same time as new rom (vertex - recommended!), but ended up having to uninstall then reinstall later. Magisk v12 wasn't passing safetynet for me, but the Beta v13 magisk seems to be doing the trick for now.
I've been in the rooting scheme since the Galaxy S2, but whenever i rooted a phone I would install a custom rom on it. On the s10+ though, the roms that are available atm are very slow to get updated, so I've started thinking about running stock rom rooted. I have a few uncertainties:
Updating to newer versions:
Would flashing updated through odin work? If not, how would I update my phone?
Samsung Health
I know that it can be fixed by editing some line(s) in build.prop
Other issues I might encounter
Such as "phone status: custom" and samsung pass not working, thus not being able to have my passwords remembered by samsung internet like on custom roms where samsung pay is debloated (or maybe it's another patch that's applied idk
Thanks guys for your help!
You might trip KNOX too. I wouldn't know, I have a locked bootloader snapdragon model.
StoneyJSG said:
You might trip KNOX too. I wouldn't know, I have a locked bootloader snapdragon model.
Click to expand...
Click to collapse
I am already rooted running Hades rom
I would like to know these questions to, because I really on my starling banking app so much, can I use starling bank app when rooted lol?