Related
help! please. I am look to root my samsung galaxy S4 Running android 4.3 with the build MK6.
PLEASE HELP?
Thank you
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
DaveRazr said:
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
Click to expand...
Click to collapse
Anything that will actually allow the install of a custom recovery?
arrush said:
Anything that will actually allow the install of a custom recovery?
Click to expand...
Click to collapse
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
jeboo said:
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Click to expand...
Click to collapse
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
azuziel said:
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Oops, didn't even realize it was i337m...:silly:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
I deleted Knox completely from my phone as well as all the AT&T Bloatware. My phone is better without it.
azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Ramsey said:
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
Click to expand...
Click to collapse
regarding knox. It is safe to allow supersu to disable knox, i avoided it thinking it may trip bc wasn't sure how it went about freezing it. I tested, had supersu disable knox, rebooted, good to go.
Did an identical handset today, and failed to root. Did some poking and found out that kies3 appears to interfere with kingo, so uninstall temporarily when running kingo if you have issues.
Once supersu disabkes knox, you can then update the binaries via normal method. Also if kingo gets to the part where it asks about using odin method, say no, or it'll trip knox.unplug, reattach and try again. Had to do it thrice for an i377m i did today.
Heres what i did:
1 - connect usb to phone, and enable developer mode, then be sure to allow the dev prompt to always accept usb from this machine, phone will prompt to allow
2 - click root. Shouldn't get to odin question, id it does, dont allow odin method, restart the process.
3 - on successful root, you will see supersu install, grant it root, and allow it to disable knox.
4 update supersu binariez via normal method (don't need to use cwm/twrp on i377m only), it will prompt, until knox disabled, u wont be able to update binaries
5 - install busybox installer
I havent installed supersu as system app yet, i imagine its also safe to do so.
6 - check knox in download mode and ensure 0x0 for *both* knox codes
7- installed xposed and some modulez, greenify in particular, and enabled, recheck knox, still 0x0
Both phones i did with this method, once kies was removed, rooted BEFORE i had to install any camera exploits, or any other crap from play. If you habe trouble, reload samsung drivers, try another cable (i had a failure using a blackberry usb cable, switched to packaged smasung usb, worked fine), anothet usb, and even another computer. Old pc's with usb 1.1 wont work (well), usb 2/3 does work just fine.
Avoid clockworkmod, twrp, safesteap etc (or any other custom recovery) if you want to keep your warranty. If you dont care, then twrp/cwm work just fine, they will blow the knox efuse tho and set you 0x1. I work in IT and happen to know knox will work with exchange 2015 upon release. It will also screw up new versions of active sync, as your system isn't able meet the security requirements (having knox intact and not blown) of the organizations' corporate knox policies. Look for a bes like sys admin tool that expands on the remote wipe /lockz/ camera images etc, in the coming months. Exchange 2015 is still a ways away, but since you cant undo a blown efuse with any software, understand implications of blowing knox fully, not just warranty. And if you use exchange email, or plan to, keep knox untripped is best advice.
Gage_Hero said:
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Click to expand...
Click to collapse
Yes. Ok, kingo is just an interface for all known exploits. The emei sniffing was actually being performed by vroot. Kingo was simply running existing vroot code. I talked to kingo support last week, who assured me that emei check was pulled during latest release, the vroot method is still present, however iz modified to remove those bad lines. When you run kingo, it opens a connection to kingo server to pull each exploit/patch as one method fails, pulls another, then another, as needed. This keeps package small, and allows for on the fly repo updatez on their end without having to re-release a package.
Kingo does not record emei at all any longer, it was vroot doing it, and kingo bc they simply ran vroot method without editing.
So you will see kingo go online to grab each exploit as required, in the new version, but no emei tracking any longer.
Besides the trojan that was used before in vroot, is picked up by avg free, so youd know if it were still doing it. I ran tcpview and tcpdump while flashing root to my device and didnt see any connections to china, any longer.
This can be verified on both odficial Facebook and Twitter account of kingo. Their intention is to at one point to charge a couple bucks for this app, having it exhibit malicious behaviour is bad for business. Youll notice vroot has no support or contact methods. Kingo does.
Sent from my SGH-I337M
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Ki Hi
Ramsey said:
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Click to expand...
Click to collapse
You cannot update ota when system is modified, there is an xposed module that changes modified to official tho. Not sure if it trips knox, likely. When updates come, unroot, apply, reroot. There are other guides that can be found here to update keepinng root with odin, you'll have to use the search provided.
Feezing with Titanium backup is fine. Supersu doesnt delete knox, it disables knox notifications. The whole point here is not tripping knox. That's why supersu asks if you want to disable knox, and not delete it, bc only disables, knox services still present. Feezing with tb is same result. Just supsrsu is free, tb is paid (for freezing anyway), though if youre on these forums, should be using tb anyway , titanium backup, greenify donation, and tasker are 3 must have root apps. Tasker is great. I use it to auto enable bluetooth and wifi based on gps location, or driving in the car. Lots of youtube vids on tasker if you areny familiat with it.
Sent from my SGH-I337M
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
If it helps any 4.3 MK6 users, I rooted using the download from this site and can confirm that it works:
http://forum.xda-developers.com/showthread.php?t=2565758
ravi_mytouch said:
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Yep it does. Ive used it on a few i377m already. Wasn't available when i did mine. Kingo is relatively safe, latest release is, cant speak for previous or future versions. Kingo is just an interface that uses all known root methods (including vroot, and this method). Just keeps trying dif method til one works. Had this been available, would have used for mine. But it wasn't so setup a segregated lab at work, to test kingo and reports of malware. I didnt see any at that time via tcp dump and tcpview, however that could change since they just rip off other root methods/code to reuse, kingo does i mean. That said if you rooted with kingo, no need to repeat. Root is root (well, full root is full root), and no daemons u dont recognize running.
Sent from my SGH-I337M
Whew! Been doing lots of reading before trying to root my Verizon Note 3 but still have a few questions that I am hoping them members here can help answer.
I have the Verizon Note 3 with the newest OTA update, running MJE
From all of the reading I have done there are currently only TWO methods of rooting?
The Kingo Method and the Vegas method using Odin.
Now to my questions.
When I got the Note 3 at launch it suffered from terrible in-call audio quality. This was fixed with the MJE update. If I root, will I loose this fix and the phone suffer from the terrible audio quality again?
The Vegas/Odin method wipes the phone and installs the MJ7 version, correct? If so, can the MJE update be applied without loosing root?
I am not terribly concerned about having to reinstall stuff I am just not sure which is the best method.
After rooting, google play, all my purchased apps, ect. will still work normally, correct?
Thanks!
At this time, there isn't a way to go back to the full MJ7 release via Odin once MJE has been installed (whether or not RDLV is involved). So, your concern about MJ7 is moot as you currently have MJE.
My understanding is that RDLV on MJ7 and MJE trips the Knox Warranty flag, & CF Autoroot is not supported on the Verizon N3 variant (SM-N900V) - somebody correct me if that is wrong. (BTW the tripping of the warranty flag has no effect on any functionality). So if that is of concern to you, you can use either Kingo or vroot for rooting.
The only functionality lost as a result of "light rooting" might be Knox container services.
good luck.
Thanks for the quick reply. So vroot or kingo would be the only options. I am mainly looking to root for the ability to remove bloatware with programs such as titanium. So as I understand it, using a root app such as these will have no impact on how I use my current apps now, playstore, ect. And will retain the MJE update?
Should I choose to root this way and want to uproot, what would be the task?
bftb0 said:
At this time, there isn't a way to go back to the full MJ7 release via Odin once MJE has been installed (whether or not RDLV is involved). So, your concern about MJ7 is moot as you currently have MJE.
My understanding is that RDLV on MJ7 and MJE trips the Knox Warranty flag, & CF Autoroot is not supported on the Verizon N3 variant (SM-N900V) - somebody correct me if that is wrong. (BTW the tripping of the warranty flag has no effect on any functionality). So if that is of concern to you, you can use either Kingo or vroot for rooting.
The only functionality lost as a result of "light rooting" might be Knox container services.
good luck.
Click to expand...
Click to collapse
ashenfang said:
Thanks for the quick reply. So vroot or kingo would be the only options. I am mainly looking to root for the ability to remove bloatware with programs such as titanium. So as I understand it, using a root app such as these will have no impact on how I use my current apps now, playstore, ect. And will retain the MJE update?
Click to expand...
Click to collapse
Yes.
But note also that in 4.3+ there is a reduced incentive to root to "remove bloatware" - preinstalled (system) apps may be disabled directly from the Applications Manager in the stock ROM. (This will be true for foreground apps like Amazon, NFL, etc, but not true for background services such as the horror which is named "Knox")
ashenfang said:
Should I choose to root this way and want to uproot, what would be the task?
Click to expand...
Click to collapse
You would perform a flash via Odin of the full stock ROM which corresponds to your current release (e.g. MJE). (This is a full factory reset which destroys all user data, BTW)
.
Ah Ok. So Odin can be used to flash an updated MJE stock ROM but can't be used to root an already updated MJE. Man that's confusing.
I do know that SOME applications can be disabled through the manager but there are still some where this option is not available. Rooting also gives the ability to run apps that block ads, which I like.
bftb0 said:
Yes.
But note also that in 4.3+ there is a reduced incentive to root to "remove bloatware" - preinstalled (system) apps may be disabled directly from the Applications Manager in the stock ROM. (This will be true for foreground apps like Amazon, NFL, etc, but not true for background services such as the horror which is named "Knox")
You would perform a flash via Odin of the full stock ROM which corresponds to your current release (e.g. MJE). (This is a full factory reset which destroys all user data, BTW)
.
Click to expand...
Click to collapse
ashenfang said:
Ah Ok. So Odin can be used to flash an updated MJE stock ROM but can't be used to root an already updated MJE. Man that's confusing.
Click to expand...
Click to collapse
Well, remember that the N3 doesn't implicitly "trust" Odin (or Heimdall), so (with the N3) Odin is limited to flashing stuff which meets the approval (signature verification) of the early-boot gearing which is already installed on the phone. This is how Samsung locks down everything and also enforces anti-rollback measures.
If you believe Samsung at their word, the anti-rollback mechanism was introduced because of Root de la Vega.
.
Ok, so basically.....
If I root my phone or were to somehow flash it with a "bad" ROM and had issues that I couldn't fix then..... Odin can be used to flash the Note 3 using a original or "verified verizon ROM" to get it back to stock?
Out of curiosity, should that happen, where does one obtain the "verified MJE ROM" to use with Odin to do the flash?
bftb0 said:
Well, remember that the N3 doesn't implicitly "trust" Odin (or Heimdall), so (with the N3) Odin is limited to flashing stuff which meets the approval (signature verification) of the early-boot gearing which is already installed on the phone. This is how Samsung locks down everything and also enforces anti-rollback measures.
If you believe Samsung at their word, the anti-rollback mechanism
.
Click to expand...
Click to collapse
by using the search function.
[Firmware][Collection] Modems, kernels, Stock Tars [Current:MJE]
[Firmware][Guide][Q&A] FIRMWARE MIRROR / OTA & ROOT GUIDE / TECHNICAL Q&A
I just rooted using towel root. Planning on staying stock just needed to make one modification. Everything is perfect including knox and flash counter. Is it okay to keep the phone rooted without having the SU app installed?
If I install supersu will it trip my flash counter? If I use it to unroot will it trip?
Thanks
Sent from my SM-G900W8 using XDA Free mobile app
Some questions are asked over and over. Which is why we can tell that you didn't do a search or take ten minutes to read a few threads - you couldn't have avoided finding the answers if you had. You'd also have gotten a quicker answer if you had tried searching.
Super SU won't increment Knox by itself. The flash counter per se can be reset. It's a widely respected and robust app and you didn't give any specific reason why you wouldn't want to use it. If you remove Super SU without manually adding more cumbersome alternatives, you won't be rooted anymore. If it is your intention to remove root, then go ahead. If you want to remain rooted, then you should do some reading as it would seem that you don't understand what Super SU does.
.
fffft said:
Some questions are asked over and over. Which is why we can tell that you didn't do a search or take ten minutes to read a few threads - you couldn't have avoided finding the answers if you had. You'd also have gotten a quicker answer if you had tried searching.
Super SU won't increment Knox by itself. The flash counter per se can be reset. It's a widely respected and robust app and you didn't give any specific reason why you wouldn't want to use it. If you remove Super SU without manually adding more cumbersome alternatives, you won't be rooted anymore. If it is your intention to remove root, then go ahead. If you want to remain rooted, then you should do some reading as it would seem that you don't understand what Super SU does.
.
Click to expand...
Click to collapse
Thanks for the quick reply. I actually Googled and read through the few rooting threads I found but couldn't find the answer for this specific question. Towelroot rooted the phone and supersu was not installed. I don't want to increase flash counter or have custom status as I want to continue to receive OTA updates. I only rooted to access a sql dB which I needed to modify.
I was never under the impression that SU will trip knox, I was wondering if it would trip my flash counter. Also, my question was based more on security. If I don't have supersu to allow root access I would assume any app can get it and would that be a security issue?
Sent from my SM-G900W8 using XDA Free mobile app
In might be a theoretical advantage to not be rooted. But you loose a lot of functionality for that security "gain". Pragmatically though there have been plenty of malware exploits that can root your device as part of their incursion. So it's hard to believe that you are gaining much security by avoiding root on your handset.
Your device will never be completely secure. Most of your risk is removed if you make a best effort to only use apps from legitimate sources and apply security updates. If you are keen you can also install a antimalware app like lookout or configure iptables.
.
fffft said:
In might be a theoretical advantage to not be rooted. But you loose a lot of functionality for that security "gain". Pragmatically though there have been plenty of malware exploits that can root your device as part of their incursion. So it's hard to believe that you are gaining much security by avoiding root on your handset.
Your device will never be completely secure. Most of your risk is removed if you make a best effort to only use apps from legitimate sources and apply security updates. If you are keen you can also install a antimalware app like lookout or configure iptables.
.
Click to expand...
Click to collapse
Agree 100%. Hence my concern about being rooted currently and not having SuperSU installed to control what apps can gain and use root access. Installation of SuperSU was a byproduct of every other root method I've used and thus I was concerned about having rooted with towelroot and not having SuperSU installed.
Sent from my SM-G900W8 using XDA Free mobile app
tawheed12 said:
Agree 100%. Hence my concern about being rooted currently and not having SuperSU installed to control what apps can gain and use root access. Installation of SuperSU was a byproduct of every other root method I've used and thus I was concerned about having rooted with towelroot and not having SuperSU installed.
Sent from my SM-G900W8 using XDA Free mobile app
Click to expand...
Click to collapse
If you choose to root your phone you should forget about OTA`s imo as this causes only issues in most cases and the loss of root. Disable/uninstall or freeze all system apps regarding OTA`s and flash an updated rom with Mobile Odin Pro and you`ll keep root BTW rooting has so much more advantages like AdAway adblocker, freezing all the unused Samsung apps/widgets, backup and restoring of apps with TB etc etc.
You dont need SuperSU for root. Its on a handler for it. It stops malware accessing root without your notice....
While searching for a root method that wouldn't trip KNOX I ran into KINGROOT. I also read that rooting using this method for the Note 4 meant only a temporary root access, that would cease to work when the phone was rebooted.
This temporary root could work for me as I'm trying to get access to the extSDcard in 4.4.4 (Lollipop didn't work out for me, horrible battery life).
So I was wondering if anyone has tested it... Here is the link to KINGROOT thread: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
I have it installed but I haven't tried it yet because I don't have time atm to reinstall everything if something goes wrong.
Have you tried it?
tried it, the phone just went to reboot then kingroot apps stated that no root available yet. so in the end, i just root the phone using chainfire root method,lol.
Framaroot doesn't work either. Cf auto root is the way to go
Sent from my SM-N910F
I have rooted with Kingroot, I've been following the SuperSuMe thread in the AT&T Note 4 General section. Kingroot works just fine if you reboot your phone after installing the apk and once the phone has rebooted then run the app to root. The root is only temporary though and WILL disappear when you reboot your phone and you will then have to rerun kingroot to root again.
Thanks for the replies
Sylntnyt said:
I have rooted with Kingroot, I've been following the SuperSuMe thread in the AT&T Note 4 General section. Kingroot works just fine if you reboot your phone after installing the apk and once the phone has rebooted then run the app to root. The root is only temporary though and WILL disappear when you reboot your phone and you will then have to rerun kingroot to root again.
Click to expand...
Click to collapse
Did your Knox stay 0x0? A temporary root works for me, what I'm really hoping for is to enable external SD access to my apps. I'm guessing that if you enable it when rooted it won't go away after you lose root...
henriquehfc said:
Thanks for the replies
Did your Knox stay 0x0? A temporary root works for me, what I'm really hoping for is to enable external SD access to my apps. I'm guessing that if you enable it when rooted it won't go away after you lose root...
Click to expand...
Click to collapse
Yes Knox remains 0x0 because the kernel, bootloader, and recovery remain untouched. As far as the external SD access, it can be enabled, but from what I gather from the other thread, is that it will revert back if the phone reboots. The reason is due to a security check Sammy put into the boot process. So put plainly, you'd have to set it up again after rerooting.
Sylntnyt said:
Yes Knox remains 0x0 because the kernel, bootloader, and recovery remain untouched. As far as the external SD access, it can be enabled, but from what I gather from the other thread, is that it will revert back if the phone reboots. The reason is due to a security check Sammy put into the boot process. So put plainly, you'd have to set it up again after rerooting.
Click to expand...
Click to collapse
I guess I'll just have to try it out... Hope it works with the 910C as well as the AT&T version.
henriquehfc said:
I guess I'll just have to try it out... Hope it works with the 910C as well as the AT&T version.
Click to expand...
Click to collapse
Apparently the new KingRoot is able to root the Galaxy Note 4 without tripping KNOX ...?
MarcoCzen said:
Apparently the new KingRoot is able to root the Galaxy Note 4 without tripping KNOX ...?
Click to expand...
Click to collapse
Not for lollipop, root strategy unavailable. Tested for both 5.0.1 and 5.1.1.
tried but kingroot failed
lucaoldb said:
Not for lollipop, root strategy unavailable. Tested for both 5.0.1 and 5.1.1.
Click to expand...
Click to collapse
That clears the air then. I have tried Kingroot v 4.5 with my sm-n910c / lollipop and to no avail.
I'm really liking the sound of a temp root. I use NFC banking and it hates root but I want a few pre-loaded apps removed. (Facebook for one) and cant without root.
BUT as I'm on 5.1.1 I guess I cant use this.
And I like to do a backup using Titanium Backup every month or so, and that also needs root. A temp root would be perfect for me.
Will kingroot be able to work on lollipop after an update or are we SOL completely?
(BTW, Note 4, 5.1.1)
Sylntnyt said:
Yes Knox remains 0x0 because the kernel, bootloader, and recovery remain untouched. As far as the external SD access, it can be enabled, but from what I gather from the other thread, is that it will revert back if the phone reboots. The reason is due to a security check Sammy put into the boot process. So put plainly, you'd have to set it up again after rerooting.
Click to expand...
Click to collapse
Hi what was your android version?? And banking apps run with no problem??
As title said, what features im going to lose besides the OTA and knox?
Sent from my SM-G950F using Tapatalk
iiD4x said:
As title said, what features im going to lose besides the OTA and knox?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Caution: This phone has dm-verity enabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
gunner007dc said:
Samsung Pay if you use it (any Knox dependant apps), Android Pay can work with Magisk but it's a cat-mouse game of passing SafetyNet. Some financial apps will refuse to work on rooted phones (some can be avoided with Magisk Hide) but if they mean anything to you it's best to check the apps to see if anyone reports problems with a rooted device. I know Netflix and other content providers sometimes block rooted phones.
Click to expand...
Click to collapse
:good: Thanks.
Fusseldieb said:
Caution: This phone has dm-verity enabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
Click to expand...
Click to collapse
Yeah, i did backup before rooting, Thanks.
Warrenty
Pokemon go
Warranty (tripping knox), Android & Samsung Pay and over-the-air updates.
Generally you have to unroot for the OTA updates to work, but sometimes that is not enough, you have to factory restore the device as well. There is the app "FlashFire" which help you keep root as you upgrade OTA, but I find this won't work on all phones.
These three reasons are why I simply do not root anymore. Now if you have a Google Pixel or OnePlus, they generally don't take away your warranty even if you unlock bootloader or root. Some manufacturer like HTC and Moto, generally you have to request a bootloader unlocking code in order to install custom recovery to root, and in requesting the unlock code you forfeit your warranty.
Is there a way to patch s Health to get it working?
Fusseldieb said:
Caution: This phone has dm-verityenabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
Click to expand...
Click to collapse
The only thing you said that is correct is that the phones have dm-verity. But given that is implemented by the boot. Img, you can either remove it with 1, an engineering boot, because you can disable dm verity with selinux in permissive. 2, flash a rom that doesn't contain the dmverity flag, seeing as the boot only checks dm verity against the partitions that contain the flag(which isn't many. And is none on a full custom rom) or 3, pull apart the boot image and remove the dmverity file.
And general root has no bearing on dmverity anyways unless an app attempts to obtain root during boot up.
But anyways. It really depends on the root method as to what you lose. If we can achieve root with a locked bootloader, you will still be able to use Samsung pay and other Knox apps with standard root hider
Hi all is there a saver root yet every one I see there was problems
cheers