So, my phone has had Knox tripped for about 5 months and I've been using Samsung pay the entire time. Well, I finally fully rooted my phone and all of a sudden Samsung pay on my gear S3 frontier stopped working because the app on my phone sees my phone as being rooted. If this is in the wrong forum, I apologize, but it just felt like more of a watch/app issue than a phone issue. Anyways, I'm using magisk as the root management tool and I've hid magisk from about every app in the list I can imagine. Any ideas?
Related
So turns out rooting my sprint note5 breaks stuff with the gear vr.
I'd like to unroot back to AOJ6.
Can anyone help please?
p1g1n said:
So turns out rooting my sprint note5 breaks stuff with the gear vr.
I'd like to unroot back to AOJ6.
Can anyone help please?
Click to expand...
Click to collapse
Oops, hit tnx by accident. The only way is to flash stock oi6 tar with odin and take the oj6 update.
Has anyone found a fix for this? I flashed back to stock but still no go for the VR setup
Wow that sucks. First Samsung pay and then Gear VR. Definitely not getting a VR now.
If true, I will not only get rid of this phone, I will never purchase a Samsung product again. I'm sick of Samsung emulating Apple. If you are going to punish people for modifying software within a device, that affects Samsung in NO way, then they will never see another penny. Root breaking warranty and Pay is enough, Samsung....... Bad form, Samsung, bad form.
Hi Everyone,
I remember back when I had the Note 2. You could reset the counter that gets triggered in Download Mode. Does the Galaxy S7 have a similar counter once I root the phone and install custom ROMS? And is there a way to reset it?
I'm getting the SM-G930F from my brother today. And I'm looking forward to it, but rooting the phone & using Xposed Framework & AdAway are priorities for me on any phone. It has two years warranty, so if anything happens to the phone I want to be able to return it.
Also after 1 year I can upgrade the phone to whatever I want on his plan, so I'll likely get the Galaxy S8. Would be great if someone can answer me today before I root it.
I'm going to use CF Autoroot, then install the latest TWRP. Do a full backup using TWRP. Copy that to the PC, before I start experimenting with different ROMS & mods.
Also another quick question, why do I not see any Android 7 stock Android ROMS or CM based ROMS around? That's surprising. Are the developers waiting for Google to release the source code? When is that expected?
Thanks in advance for all the replies.
Blackfyre said:
Hi Everyone,
I remember back when I had the Note 2. You could reset the counter that gets triggered in Download Mode. Does the Galaxy S7 have a similar counter once I root the phone and install custom ROMS? And is there a way to reset it?
I'm getting the SM-G930F from my brother today. And I'm looking forward to it, but rooting the phone & using Xposed Framework & AdAway are priorities for me on any phone. It has two years warranty, so if anything happens to the phone I want to be able to return it.
Also after 1 year I can upgrade the phone to whatever I want on his plan, so I'll likely get the Galaxy S8. Would be great if someone can answer me today before I root it.
I'm going to use CF Autoroot, then install the latest TWRP. Do a full backup using TWRP. Copy that to the PC, before I start experimenting with different ROMS & mods.
Also another quick question, why do I not see any Android 7 stock Android ROMS or CM based ROMS around? That's surprising. Are the developers waiting for Google to release the source code? When is that expected?
Thanks in advance for all the replies.
Click to expand...
Click to collapse
Installing other custom ROM will trigger know and you will lose warranty. I don't see any reason to install custom ROM at least at the moment. There is a root method that claims to not trigger knox but I haven't tried it.
Sent from my SM-G930F using Tapatalk
Try the root method that people relate that doesn't trigger knox..
And there's a few roms to nougat, no custom kernel for now.
Enviado do meu SM-G930F através de Tapatalk
Any root method for the G930F will trip KNOX and void warranty (Afaik it is other models that can be rooted without tripping, unless I've missed something lately)
Flashing anything custom will also trip KNOX
There is no way to reset the KNOX counter
If you trip it, that is permanent
If knox is tripped, will they also refuse to do any hardware repairs? For example, after 2 months my home button doesn't work anymore.
destz0r said:
If knox is tripped, will they also refuse to do any hardware repairs? For example, after 2 months my home button doesn't work anymore.
Click to expand...
Click to collapse
All, warranty is warranty, it will be refused
In some cases people get lucky and Samsung repair anyway, maybe because they didn't check, but if KNOX is tripped, all repairs will cost you money with no warranty
destz0r said:
If knox is tripped, will they also refuse to do any hardware repairs? For example, after 2 months my home button doesn't work anymore.
Click to expand...
Click to collapse
In Europe, Samsung has to repair the equipment even with Knox tripped, as long as it was not root that damaged the hardware.
I had to send my phone to Samsung, because i screwed up the phone with Xposed and Samsung repaired it without charging anything.
Hansoliv said:
In Europe, Samsung has to repair the equipment even with Knox tripped, as long as it was not root that damaged the hardware.
I had to send my phone to Samsung, because i screwed up the phone with Xposed and Samsung repaired it without charging anything.
Click to expand...
Click to collapse
Thanks alot!
Hansoliv said:
In Europe, Samsung has to repair the equipment even with Knox tripped, as long as it was not root that damaged the hardware.
I had to send my phone to Samsung, because i screwed up the phone with Xposed and Samsung repaired it without charging anything.
Click to expand...
Click to collapse
This has been the discussion since my S5 days, they don't often honour it even in Europe, even quoting the piece of law stating they have to
Only a lucky few get it done without a problem
*Detection* said:
This has been the discussion since my S5 days, they don't often honour it even in Europe, even quoting the piece of law stating they have to
Only a lucky few get it done without a problem
Click to expand...
Click to collapse
Oops, looks like i got lucky.
Will not try and root again so soon.
Alright, so I've done some research on this subject.
Most root or ROMs will "Fry the knox circuit." Basically, what that is, is a secure, totally private fuse that your phone has, which is like 2 nanometers small chip in you phone's mother board. It's an absolutely tiny fuse that protects the ADMIN section of you phone. Currently most, if all known methods, of root will trip it. So, as stupid as it sounds, I'd say "Buy a USB killer." Which is a USB device meant to test protection circuits. And if you phone is already dead to some point, if they can't power it up, they may just say "**** it" and do a warranty replacement.
Otherwise, unless they can tell, they'll just swap it for a preowned model if they can't tell you ****ed with it.
Honestly, if you have insurance on it, smash it with a hammer. If not, say it started smoking while charging and make sure it won't charge, Apple is scared ****less towards possible fire damage and samsung just had that Note 7 thing
I've just gotten myself onto a Galaxy S7 for my carrier with Nougat installed. I happen to like the looks of this version and have no consideration to update to Android Oreo (8.0). But this looks to be a forced update. I have merely avoided this by just not connecting to wifi, however this makes me unable to use the samsung cloud without using mobile data to backup pictures and content. The only way I could perform disabling the update was through rooting the device, which I did not like having to do at all. It only brought complications to the devices run patterns etc.
As well I have also searched everywhere to find a way to disable the update service without rooting, even as far as Package Disabler Pro however it seems the developer was forced by samsung to disable this capability during the Note 7 Era. Even trying to use an Older Version of PDP failed because of the License Verification.
So I have come here to ask, Has anyone at all ever found a way to stop the update service from forcibly downloading the update when connected to wifi and forcing the device to update whatsoever, without Rooting the Device. Your knowledge and advice would be highly appreciated
ben70190 said:
I've just gotten myself onto a Galaxy S7 for my carrier with Nougat installed. I happen to like the looks of this version and have no consideration to update to Android Oreo (8.0). But this looks to be a forced update. I have merely avoided this by just not connecting to wifi, however this makes me unable to use the samsung cloud without using mobile data to backup pictures and content. The only way I could perform disabling the update was through rooting the device, which I did not like having to do at all. It only brought complications to the devices run patterns etc.
As well I have also searched everywhere to find a way to disable the update service without rooting, even as far as Package Disabler Pro however it seems the developer was forced by samsung to disable this capability during the Note 7 Era. Even trying to use an Older Version of PDP failed because of the License Verification.
So I have come here to ask, Has anyone at all ever found a way to stop the update service from forcibly downloading the update when connected to wifi and forcing the device to update whatsoever, without Rooting the Device. Your knowledge and advice would be highly appreciated
Click to expand...
Click to collapse
Wow this is disappointing. I'm in the same position. I unintentionally tapped update vs, wait and now it asks me several times a day.
I didn't have any of these issues with my S5. Since when does samsung force their customers to update? Seems to me samsung still owns my phone after I paid for it. If I wanted this crap, I would have bought an apple. i can't believe everyone is ok with this? Not even a data toggle switch anymore. I had to use ADB to put this back. My S5 was able to multi-task and my S7 can't. Further my 5 can get on wifi faster. None of this should be possible.
Forced to Root
ADB my S7 said:
Wow this is disappointing. I'm in the same position. I unintentionally tapped update vs, wait and now it asks me several times a day.
I didn't have any of these issues with my S5. Since when does samsung force their customers to update? Seems to me samsung still owns my phone after I paid for it. If I wanted this crap, I would have bought an apple. i can't believe everyone is ok with this? Not even a data toggle switch anymore. I had to use ADB to put this back. My S5 was able to multi-task and my S7 can't. Further my 5 can get on wifi faster. None of this should be possible.
Click to expand...
Click to collapse
I guess theres no solution to this then other than rooting the device sadly. I was forced to root it and I used the root method that requires no having to tweak the kernel so its been going pretty good for now. But yes indeed even my Galaxy S4 is faster than my s7 now in some cases. But the only thing I can see the issue with is now I hate having to restart my S7 when im using it because it takes like a minute or two to fully load up everything. Feels like im using a PC and not a phone
any luck ?
Last phone I ever rooted was my old Galaxy S6. Years ago. In the end I ended up flashing back to stock. Cant remember why.
But yesterday morning after I got the android pie / one ui OTA .. I cannot use substratum and andromeda anymore!! I hate the themes from the galaxy store with a passion.
Is it worth rooting just to theme? I guess losing Knox ain't a problem. My phone isnt under warranty, it's a tmobile phone unlocked with different cell carrier.
Any opinions ?? :highfive:
bump
turbolaceup said:
Last phone I ever rooted was my old Galaxy S6. Years ago. In the end I ended up flashing back to stock. Cant remember why.
But yesterday morning after I got the android pie / one ui OTA .. I cannot use substratum and andromeda anymore!! I hate the themes from the galaxy store with a passion.
Is it worth rooting just to theme? I guess losing Knox ain't a problem. My phone isnt under warranty, it's a tmobile phone unlocked with different cell carrier.
Any opinions ?? :highfive:
Click to expand...
Click to collapse
I tried pie on my wifes phone. Its cool. I like it. But nothing compares to a rooted device even if you dont have custom roms or that good stuff. Even a 1.5 year old s8 still get better battery life than a new stock one with all my tweaks. I even kind of broke the 80% charge barrier litrelly last night. Got a 90% charge. So imo if your a smart fellar and can follow the root mwthod instructions to a t i would always pick root over updates. Im still on a revision 2 bootloader and plan to be til the death of my device
I see you say tmobile. The US devices or U models cannot trip knox. You lose samsung pay while rooted but you can always restore back stock. Secure folder and pay will work after. Since we have locked bootloaders. And no way to unlock them since they are signed with 256 bit sha keys.
I got dual speaker mods, modded touchwiz, deodexed. Completely themed out. I try all kinds. I push root to its limits for a locked bootloader.
TheMadScientist said:
I tried pie on my wifes phone. Its cool. I like it. But nothing compares to a rooted device even if you dont have custom roms or that good stuff. Even a 1.5 year old s8 still get better battery life than a new stock one with all my tweaks. I even kind of broke the 80% charge barrier litrelly last night. Got a 90% charge. So imo if your a smart fellar and can follow the root mwthod instructions to a t i would always pick root over updates. Im still on a revision 2 bootloader and plan to be til the death of my device
I see you say tmobile. The US devices or U models cannot trip knox. You lose samsung pay while rooted but you can always restore back stock. Secure folder and pay will work after. Since we have locked bootloaders. And no way to unlock them since they are signed with 256 bit sha keys.
I got dual speaker mods, modded touchwiz, deodexed. Completely themed out. I try all kinds. I push root to its limits for a locked bootloader.
Click to expand...
Click to collapse
Just the fact of losing Samsung pay, I will not root my phone. Thank you so much for reminding me of that downfall!!!
Yeah my phone is sm-g955u tmobile s8+ but unlocked and I use metro pcs.
And what is the 80% barrier? I read something earlier trying to find a rom if I were to root... I got parallels installed on my computer so I could have used Odin. (I sadly own a hackintosh, built from scratch mac in a PC tower)
I miss using substratum sense the pie update, but This equally Black & Red Samsung theme along with This awesome Samsung icon set is doing okay..
I do miss blacked out gmail, play store, etc... lol
Sent from my Samsung Galaxy S8+ using XDA Labs
turbolaceup said:
Just the fact of losing Samsung pay, I will not root my phone. Thank you so much for reminding me of that downfall!!!
Yeah my phone is sm-g955u tmobile s8+ but unlocked and I use metro pcs.
And what is the 80% barrier? I read something earlier trying to find a rom if I were to root... I got parallels installed on my computer so I could have used Odin. (I sadly own a hackintosh, built from scratch mac in a PC tower)
I miss using substratum sense the pie update, but This equally Black & Red Samsung theme along with This awesome Samsung icon set is doing okay..
I do miss blacked out gmail, play store, etc... lol
Sent from my Samsung Galaxy S8+ using XDA Labs
Click to expand...
Click to collapse
The kernel we have from Samsung the they do graciously left open to use for permissive root. Has a80% charge cap set in place from Samsung. Its a safety thing.
TheMadScientist said:
The kernel we have from Samsung the they do graciously left open to use for permissive root. Has a80% charge cap set in place from Samsung. Its a safety thing.
Click to expand...
Click to collapse
Weird. Lol.
I havent seen too many threads about the Gear S2s randomly stopping working and not being able to take updates on here, but the forums on Samsungs site is awash with them, so i figured id throw this out there for those who might stumble upon it.
For the last few months my sons Gear S2 hasnt been able to pair with any phone properly. It would initially connect, then say that a firmware updates was required in order to continue using the device and wouldnt let you just continue with the current firmware. I tried pairing it with my U1 S9, my fiancees 100% stock Cricket S9, my old A8, 2 old S5's, S7 and S7 edge both, S4 and finally a S3. All of them failed to update the firmware and there was a bevvy of Android OS versions that i tried, so that was effectively ruled out. No amount of facory resetting via the OS itself nor recovery changed it. I then went to the Samsung forums as a last hope and there were "certified Samsung tech"s replying stating that they were working on it.
Fast forward to yesterday (i have been dealing wit this since before Christmas) and th ekiddo asked if there was any progress. It had been about a week since i tried it, so i tried it with my U1 S9 again and to my UTTER SHOCK AND DELIGHT, it actually took the update this time! It installed, rebooted twice (as per normal) and paired 100% with my phone! I unpaired it and had the kiddo pair it to the A8. That worked too!
Moral of the story, if you have a Gear S2 sitting in a drawer that suffered teh same fate, try the update again. Its worth a shot!