Search results

I'm using a rooted S8+ running Soldier's ROM

I can also confirm that after hiding SPay with Magisk, repackaging Magisk Manager, and remembering to remove BusyBox from /system/xbin and /system/bin, I can now add cards to the latest version of SPay 1.7.3006. I'm using an unofficial Magisk Build that is similar to a Canary Build. Note: If...

I can confirm that WiFi Calling works on a different ROM so it has nothing to do with carrier issues or having a feature turned on by my carrier. I'm sure you'll find the reason soon since you fix problems fast! Thanks so much!

Still having the WiFi Calling issue. Could it be due to CSC tweaks that have been added to the base ROM? Otherwise great ROM

I am also noticing that WiFi Calling is not working. I flashed the CSC for XAA and TMB in the USA as I always do and the WiFi Calling symbol is just stuck on enabling in the settings.

Haven't had the issue where it lost root. Magisk Hide is really only needed while you are setting up the cards. After that the app on the phone is mostly just yo reveiw purchases that you've made on SPay and to look at your Samsung Reward point totals.

Version 1.6.7406 asks you to update but doesn't force you. You can then change the settings on the app to never update. This version works perfectly for me.

Sorry disregard.

ROM update looks awesome. Thanks for all your hard work! Question: Still having issues with "Ok Google" not working. Any issues with the Velvet settings?

Samsung Pay gear app updated again and once again can't use it. Now the language is "Unauthorized changes were made to your phone." Oh well all my cards are already loaded in my Gear S3 and if I ever want to use Samsung Rewards I'll just downgrade.

Great ROM. My daily driver. I am wondering if the google assistant issues will be resolved with the update. I have been unable to use "Ok Google" type voice commands after some of the previous updates. Looking forward to your next update!

After installing the latest update I am unable to install modules. I get the error /data/adb/magisk_merge.img mount failed

Wow you're right. Up to this point I had been reluctant to update because up through Magisk 16.3 it didn't work so I didn't even bother trying to do it cause I kept having to reset my cards. Thanks for the heads up!

I can't open the phone Samsung Pay app because Knox has been tripped. I can, however, open the Gear Samsung Pay plugin which I've rolled back the version to 1.5.6306. Within the app I'm able to add cards, check out my Samsung reward points total, and see the transactions I have conducted using...

It will work but not with the current version of SPay on the phone. The current workaround for that is to use an old version and load the cards that you want and then update to a newer version. The 1.6 update to SPay broke the ability to add more cards and review the previous transactions done...

That could be the case but that would be a new change then as Samsung Pay on the Gear never previously was totally blocked on rooted phones even the Knox was tripped. I'm still hopeful that it could work but right now will probably just roll back again

I'm still getting access denied despite updating to Magisk 15.4, hiding Samsung Pay, and deleting BusyBox. I was using the version just prior to this one flawlessly and updated to see if it worked. Anything more I have to do? I have a rooted Exynos S8+ on Oreo. Thanks

I'm still able to use Samsung Pay on my watch with a rooted Exynos S8+ on Oreo. I had to roll back to version 1.2 then set it up, hide with magisk and remove BusyBox, then updated to the previous 1.5 version and then disable updates and it hasn't asked me once to update or forced me to upgrade...

I am using a Gear S3 with a rooted Exynos Galaxy S8+ with the Lightrom 8.0 ROM. I use MagiskHide to hide the Samsung Pay gear plugin app and deletedb BusyBox from /system/bin and /system/xbin. Recently Samsung Pay has updated and Magisk 15.3 has not caught up so the most recent version of...

Mount system in TWRP and then you can use the TWRP file manager in Advanced to navigate to that folder and delete BusyBox. This is how I took care of the same problem.

Yeah this is a big issue I'm facing as well and I'm really curious as to why certain ROMs have no issues and others are seemingly impervious to the methods used to hide root from SPay. If anyone has any insight into how to get this to work please share so that we can all benefit.

Has anyone gotten the Gear VR controller app to work to help control some of the functions from the Gear S3. When I have used the Gear VR I notice that it immediately force closes the VR controller app or sometimes doesn't work at all. This was a feature that was new since Tizen 3.

The thought about the strap is an interesting one and one I thought may be at play as well. It would be a disaster if that is what is causing it because I don't know if there is a good fix for that. Anyone recommend any straps that potentially could fix this problem?

Is that a new issue for you since Tizen 3 update? This has never happened to me prior to the update. As others have said before I'm pretty unhappy with this update. I have worse battery life, the Gear VR integration hasn't worked for me, and this PIN thing is crazy frustrating.

I have an issue since I upgraded to Tizen 3 that I can't find the answer for. I keep getting a recurrent message saying EAS requires a PIN to access email content. The dumb thing is I already have a PIN and the phone is set to Gear Lock with Payments only. I type in the PIN I have and re-enter...

I have also noticed more battery drain after upgrading and a lot of it is from Samsung Health. I'm not sure what's going on with that exactly

You should let us know on this thread. I myself have had a lot instances where Samsung Pay doesn't work on the gear. It'll work flawlessly one day on a terminal and then the next day one card works but another doesn't and then the next day no cards work. I don't really know what changes in...

I'm also getting pretty short battery life. I'm thinking about clean flashing again to see if that sorts it out.

In certain ROMs busybox seems to be in /system/xbin and removing it does the trick and SPay will work on the watch and in the app on the phone. In other ROMs busybox is absent but the phone still doesn't work despite the release-keys being also set in the build.prop. I find that when that is...

Any issues with anti-Rollback that you're aware of? Thanks

I had major problems also with Google accounts not pairing to my phone. Thing that seemed to work for me was clearing data and cache ON THE WATCH for the Google Play Services, Play Store, and Google and then trying to connect it. I wonder if it works for others.

Looks great can't wait for this to come out. Let me know if there's something you'd like me to test with this.

Not from my experience. It just boots into twrp and wipes

I hadn't set it up... :( I'm dumb

Didn't have an SD card inside at the time.

So I used the button combination to get into TWRP and ended up with a wiped device.. lost my pics :( TWRP performed the factory reset and wiped me out.

Instructions worked great. Thanks a lot everyone!

Dude you are a champ. Thanks for answering my call for TWRP and all your efforts. We all really appreciate it and thank you for your help.

Chainfire has published his pixel root. Seems like a lot of stuff has changed under the hood for Android.

http://forum.xda-developers.com/v20/how-to/ready-to-return-phone-root-t3486881/post69341194 This guy is pretty amazing. He has cracked Dirty Cow for us.

http://arstechnica.com/security/2016/10/android-phones-rooted-by-most-serious-linux-escalation-bug-ever/ Is it just me or does this article's source sound like a certain jcase...? I wonder if he would be able to help you put the finishing touches to your code. I know he hates the people that...

He already posted it on his website a few pages back. Check it out

Disregard

http://forum.xda-developers.com/v20/development/lg-v20-tmobile-variant-stock-tot-t3484982/page15 If you guys check out that thread you'll see that jcadduono has figured out a way to flash TWRP from the shell that he creates using dirty cow on the unlocked T-Mobile V20. There was some kind of...

Yeah I can help too for about 30 mins to an hour.

I can help but I have work in one hour. I can try to help in the evening though since it's 5:20 AM where I'm at.

I have the phone in hand. What do I do to install TWRP? I haven't pushed anything as of yet.

Is this a confirmation that twrp is installed? If so how do I go about testing it myself?

That's an LG thing I think. A similar message appears on the G5 running Marshmallow

You have made a new TOT file with TWRP? Have you tried flashing it first? I'd like to give my phone as a tester but I've already bricked my G5 in the past with you.. don't want that to happen again.