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.
Related
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Njord0 said:
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Click to expand...
Click to collapse
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
kkretch said:
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
Click to expand...
Click to collapse
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Njord0 said:
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Click to expand...
Click to collapse
Without a stock 4.1.2 firmware for your device it looks like you are going to have to do a factory reset to use Kies.
I think your options are limited..........
Have you considered using a firmware from another country?
You know there is a backup program called Helium that does not need root, you may want to consider using it to backup all of your data and then do a factory reset.
I don't know if I have helped you any............
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
bjf189 said:
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
Click to expand...
Click to collapse
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
ShapesBlue said:
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Click to expand...
Click to collapse
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
ShapesBlue said:
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Its cool. Good to see safestrap works on the prepaid version also
Sent from my Nexus 5
I'm not sure what a bash terminal is unless it's the same thing as the terminal emulator. I tried using that rom that's called paulpizz or something like that. I used some other rom to. The paulpizz one always failed to install even after downloading it a third time. The other one i can't remember the name but it installed but wouldn't start at all. It would just go black and bootloop and goes into stock recovery for some reason. I came across the nf5 module when i found that paulpizz rom on the goo server they hosted it on. So i got the module and i figured if i were to flash the module over the i535 rom that it would fix the wifi an data problem but never got an answer because it always failed to start up properly and would just bootloop into stock recovery. Ugh Verizon is making things so difficult with modding lol. As of now I'm just using xposed to get at least some theming in and tweaks. I couldn't get any deodex program to work. Whenever i used the deodex files and pushed them to the system of apps and framework, it would restart and just stick on the Verizon logo. So i had to flash the firmware to fix the problem.
When i was on 4.3 with this phone safestrap worked and i got the wifi and data sim error. Now that i got it replaced I'm running the kernel of July 22 2014. Everyone was saying I'm out of luck but i came across kingroot and got the most recent version and it worked. I have root. Installed safestrap for 4.4 and it runs fine but can't get any custom roms to boot. I only managed to find one 4.4 touchwiz rom unfortunately
OpenSourcererSweg said:
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
Click to expand...
Click to collapse
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
bjf189 said:
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
OpenSourcererSweg said:
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
Click to expand...
Click to collapse
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
bjf189 said:
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
Click to expand...
Click to collapse
Safestrap 3.75 had support for AOSP roms (wifi/data didn't work for them either) and 4.0 dropped support for that (there is currently no point). Read the thread for more info http://forum.xda-developers.com/showthread.php?t=2797314
Ok i wasn't using safestrap 4.0. I had 3.75 B05 which i thought was the latest version they had. I'm updated to 4.0 now and about to test the modules on the superlite rom
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
bjf189 said:
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
Click to expand...
Click to collapse
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
OpenSourcererSweg said:
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
Click to expand...
Click to collapse
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
bjf189 said:
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
Click to expand...
Click to collapse
I'm running the stock prepaid rom, not superlightrom, sorry if there's any confusion there.
When I tried out superlightrom (quite some time ago) it appeared to work fine (excluding wifi/data and nagging about no SIM card being inserted, nothing like what you're describing) and I went back to stock.
Oh ok. Well it seems that the prepaid version or the s3 in general is dead. That's unfortunate
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)
I have signed into kies and it says
dawgdoc said:
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)
Click to expand...
Click to collapse
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?
648charlie said:
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?
Click to expand...
Click to collapse
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?
dawgdoc said:
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?
Click to expand...
Click to collapse
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk
got launcher from google apps
Droidriven said:
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Loaded launcher from google apps, talked to verizon and they put s3 inservice for 5 minutes and I made a call.
all is well
thank you thank you
John
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
Hi guys,
I'm considering rooting my G930FD. If I just root it, I should be able to disable most of Samsung crap, correct? I'm concerned about being able to use apps that might detect for root/CFW, such as:
-Google Pay
-HSBC
-MobileIron
Is there a way to hide the root from these? I think MobileIron even checks the knox status, so even if root is hidden/disabled, I might still fail that check.
If I install a CFW, what are the current status of affairs? I haven't installed a CFW since my Galaxy S4 times. As in, if I install any Lineage/AOSP, is there any way to get the camera to work with the stock app, or at least make it perform stock/like? What about Google Pay etc on these ROMs? Any stock-based ROM that keeps the camera while minimizing/rooting out all the touchwiz crap, while still working?
Thanks! I've been out of the game for a couple of years and got lost trying to catch up again...
timonoj said:
Hi guys,
I'm considering rooting my G930FD. If I just root it, I should be able to disable most of Samsung crap, correct? I'm concerned about being able to use apps that might detect for root/CFW, such as:
-Google Pay
-HSBC
-MobileIron
Is there a way to hide the root from these? I think MobileIron even checks the knox status, so even if root is hidden/disabled, I might still fail that check.
If I install a CFW, what are the current status of affairs? I haven't installed a CFW since my Galaxy S4 times. As in, if I install any Lineage/AOSP, is there any way to get the camera to work with the stock app, or at least make it perform stock/like? What about Google Pay etc on these ROMs? Any stock-based ROM that keeps the camera while minimizing/rooting out all the touchwiz crap, while still working?
Thanks! I've been out of the game for a couple of years and got lost trying to catch up again...
Click to expand...
Click to collapse
I haven't touched my S7 yet so I can't answer you but this could answer some of your questions:
https://forum.xda-developers.com/galaxy-s7/how-to/debloat-galaxy-s7-services-safe-to-t3432967
You don't necessarily have to root, you have to install TWRP as a custom firmware, then get the script, edit it if you don't want some apps to be removed, apply the script and it's debloated.
But I'm sorry I can't tell you if you can install TWRP without tripping Knox, I can't tell you if installing a custom Firmware will disable Google Pay etc... But I guess you can easily find that information by searching, or someone knowing more than me will help you
Installing TWRP will trip Knox if it's like every other Samsung phone I have owned that referenced Knox or warranty bit in download mode.