Flashed back to stock now S Health doesn't work - T-Mobile Samsung Galaxy Note5

I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?

Nightcatfisher said:
I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?
Click to expand...
Click to collapse
You need to edit the build.prop
Look for ro.config.tima and change the "1" to a "0".
You can either use a app like root explorer or BuildProp Editor.
You will have to root to fix this as it is using Knox to detect the past root/recovery flash.
Once you trip knox with twrp / root you can undo that.
Rooting alone shouldnt be giving you any trouble?
What problems were you having that made you want to go stock with no root?

DeeXii said:
You need to edit the build.prop
Look for ro.config.tima and change the "1" to a "0".
You can either use a app like root explorer or BuildProp Editor.
Click to expand...
Click to collapse
I wonder where you got this little tidbit of advice from...
https://forum.xda-developers.com/showthread.php?p=71995091

Nightcatfisher said:
I have given up on customizing Android and flashed stock firmware from sammobile, now I can't open the S health app. A pop up shows "Your device has been compromised. Because of a new security policy introduced in version 5.0, Knox is not available on compromised devices. (0x110020521) I downloaded and ran root checker and it shows the phone is not rooted. Is there any way I can get rid of this without rooting again?
Click to expand...
Click to collapse
just downgrade to 6.0.1 with odin, start s health and let the phone upgrade it`s self to 7. Worked for me

Related

[ROOT] (Kingo Root Tool) - No ODIN flash required! Knox stays cool (0x0)

Hey,
even though (literally) NOBODY answered my simple questions when I was desperate to figure out how to get my Note 3 rooted while keeping Knox 0x0 after I updated to MJ3 through odin to get rid of branding, here it is:
(what a long sentence lol)
I could not use Root de la Vega I was told, because I took the update to MJ3 with a different bootloader, so I had to find something else. (phone is just 3 days old lol, didnt want to trip knox yet - even if it won't matter for warranty here in europe)
WARNING: I'm not taking resposibility if you brick your phone or if things do not work as I described here, I just wanted to share the info and my experience with others. What you do with it is your own thing! I was worried that this tool is fake so I would have been glad about more infos before trying it myself..
Working for Snapdragon only afaik!
(This isnt my work and I'm not related in any way - so give those guys credit and like em on facebook etc..)
With this app I could root my German N3 with the latest stock firmware, and knox stayed 0x0.
There could still be problems - but so far it seems to work as root is supposed to work with full write access to system partition.
(adb remount did not work for me, but system was actually mounted writable to root already, and remounting system in shell did work as well).
---
Steps to get your Note rooted without having to touch odin and risking Knox flag to trip:
1. Download the android_root.exe from kingoapp.com (I'm still a bit suspicious since the thing does not have that much reputation, but who would program a working root tool just to distribute viruses etc? and its definitely working!)
2. Turn off OTA-Updates, Reactivation-Lock, Security-Updates (just to make sure - dont know if these are really necessary, but it wont hurt either)
3. Turn on USB-Debugging.
4. Install and start the android_root.exe from kingoapp.com and connect the phone when asked to.
5. Most likely it will install drivers (again... even though I had all drivers installed it downloaded the samsung drivers again, but in snail speed - so it takes a while to finish..) and ask you to disconnect/reconnect the phone.
6. It will then give you a nice big and red "Root" button, in addition to some infos.
7. Click root, and if I remember correctly there is one final step - to allow adb shell root access in su.
8. After that reboot the damn thing and enjoy root with knox still at 0x0.
9. Thank the guys who created this app (and like on facebook/twitter)!
10. (if you feel like). Click the thanks button below =)​
No need to "risk it" by flashing modified odin files! (absolute noob-friendly and probably also noob-proof™ tool)
(during the whole process knox was "freaking out" a few times, the usualy prevention notification, but it seems that the kingo root tries different approaches and once it succeeded my phone did a soft reboot - screen black for a second and then booting again)
----
ADDff course your system-status will show "custom" when using this, but knox and binary counter/flag stay 0x0. I heard from some other guy that you can restore to full stock with kies 3 by just flashing the firmware you are on again. This also keeps knox 0x0 I heard, but I cannot confirm yet since who wants a non-rooted phone here anyway? =) Only useful incase you need warranty repair - then I would give it a try.
I, too, successfully rooted my MJ3 Note with this tool.
I guess the reason why most, but not all apps get succesfull root or are not able to alter some files despite obtaining root permissions from SuperSU (which itself works but can't be updated) lies with SELinux. It remains on "Enforcing".
But better than nothing and hassle free so far, :good:
saintsimon said:
I, too, successfully rooted my MJ3 Note with this tool.
I guess the reason why most, but not all apps get succesfull root or are not able to alter some files despite obtaining root permissions from SuperSU (which itself works but can't be updated) lies with SELinux. It remains on "Enforcing".
But better than nothing and hassle free so far, :good:
Click to expand...
Click to collapse
Yea its this SELinux enforcing BS apparently.
Does anyone without custom kernel have it on permissive and knox still at 0x0?
"setenforce 0" does not work (permission denied) and i cannot enter the selinux directory although its set as owned by root...
I found a few lines in init.rc which give "system" access to the enforce files, maybe if we could change this to root ..? =)
Will this work on exynos?
Sent from Note 3 (The beauty & beast)
sohebq said:
Will this work on exynos?
Sent from Note 3 (The beauty & beast)
Click to expand...
Click to collapse
No clue sorry, good you ask though. Officially the app only supports N9005 and N9006
Look what I found in the init.rc:
HTML:
# Allow system UID to setenforce and set booleans.
chown system system /selinux/enforce
chown system system /sys/fs/selinux/enforce
chown -R system system /selinux/booleans
chown -R system system /sys/fs/selinux/booleans
chown system system /selinux/commit_pending_bools
chown system system /sys/fs/selinux/commit_pending_bools
I made a version where this is all commented out, but knox that lil mofo doesnt let me write to init.rc - prevention BS again.
But how are the these things circumvented in the first place to aquire "root"? In the same way you could replace init.rc and turn that crap off that way or not?
ADD: Just a lil warning - I apparently did something that ****ed up the supersu app so it only shows a blank screen and su requests arent shown anymore. I tried reapplying the kingo root, but it wants me to allow adb shell again in superuser but i cant and then it gets stuck lol.. cant tell it to just do the root process again it seems. So I will have to go back to stock and reroot, but I'm trying all sorts of other stuff first to avoid having to do that. Not sure what caused it probably "pm enable com.sec.knox.selinux" .. after i first disabled it (probably already was disabled..and i stupidly turned it on... but not 100% sure yet that is the cause because I still had root afterwards.. but at some point it stopped working)
ADD2: Loading the firmware over kies right now, goes quite fast and when it succeeds ill report if i still got 0x0 (which I expect since someone said it works like this). If so then this would be a safe method to return to stock from rooted phone. (odin always dangerous - efs or knox..)
ADD3: OMG this kies! 100% cpu load while downloading the firmware lol? At the end it kept stalling for ages at 100% even after decompress was complete - killed it and restarted pc now i have to download everything again - and it keeps utilizing 100% cpu load (on one core, and like 50% on 2nd)
AAAAAND its gone!
I mean its there again. (the root!)
Full cycle went through without any problems or knox triggering:
1. Unbranding with stock odin file for my region from sammobile.com
2. Rooting with Kingo Root
3. (optional) Messing up root somehow... (still not sure how exactly)
4. Goin back to official status (and removing the non-working root) with Kies 3
5. Rooting again with Kingo Root
and everything with knox warranty still intact
While I still wont take responsibility what you do with your phone incase something goes wrong - I can do nothing but recommend this Kingo Root to everyone worried about the knox warranty flag - it seems completely safe (as long as nothing interrupt the process at least). With RDLV (which is also good I'm sure, but I couldnt use it since I had updated too early) you run the risk of tripping knox. At least you did with the old version where you had to find the right files yourself.
Has anyone confirmed that this root method works on Verizon Galaxy Note 3?
Sent from my SM-N900V using Tapatalk
I posted this in Sprint general section tonight. Works for Sprint version for sure L900p. I actually rooted and unrooted using app.
Link to the devs facebook fan page to like his page and ask questions.
https://www.facebook.com/kingoapp
Very few feedbacks considering the tool is compatible with Note 3 since 23rd of october...
Is it for real or not ?
Have you been able to update su binary?
Yes it works. A Mod closed my sprint thread. He stated we can't link to work outside of XDA. Weird since I been a member since 2006 I never heard of that rule. Most of the development comes from outside xda. Anyways yes it does work perfectly.
Sent from my SM-N900P using Tapatalk
CSC change !
I managed to change the CSC code to CYO >> XEF (France) without triggering Knox and with MJ3 ! :good:
Root with Kingoapp (download program, switch off reactivation lock OTA upgrades etc and activate USB debug, lunch the program, connect the phone, click root, allow debuging on the phone, wait, ignore message at screen, phone reboot, done !)
Use a root file explorer (Root explorer works for me) go to system/csc and search your actual CSC, normally there is 2 folder inside "csc_contents system and" move these folders to a safe location ( ex, PC )
Again in system/csc, look the code you want to apply, enter the folder, copy the two folders "and csc_contents system" and paste in the folder of your current code.
Make a full wipe with restore save menu, the phone reboot, after restart, switch off the phone and reboot in recovery, look at the bottom line "Applied the CSC code :" if your code is here, win !
Note : Root survive after full wipe.
jerem52 said:
I managed to change the CSC code to CYO >> XEF (France) without triggering Knox and with MJ3 ! :good:
Root with Kingoapp (download program, switch off reactivation lock OTA upgrades etc and activate USB debug, lunch the program, connect the phone, click root, wait, ignore message at screen, phone reboot, done !)
Use a root file explorer (Root explorer works for me) go to system/csc and search your actual CSC, normally there is 2 folder inside "csc_contents system and" move these folders to a safe location ( ex, PC )
Again in system/csc, look the code you want to apply, enter the folder, copy the two folders "and csc_contents system" and paste in the folder of your current code.
Make a full wipe with restore save menu, the phone reboot, after restart, switch off the phone and reboot in recovery, look at the bottom line "Applied the CSC code :" if your code is here, win !
Note : Root survive after full wipe.
Click to expand...
Click to collapse
I thought it was not possible to get a recovery mode, without triggering the Knox flag ?...
Dit you got the recovery mode during the Kingo Root procedure ?
HokutoNoFred said:
I thought it was not possible to get a recovery mode, without triggering the Knox flag ?...
Dit you got the recovery mode during the Kingo Root procedure ?
Click to expand...
Click to collapse
No need recovery for kingo, just download and install the program on PC, on the phone, turn on usb debugging, turn off reactivation lock and automatic upgrade (it may not necessary, it's to avoid surprise with upgrade ) connect the phone, wait on kingo, click Root, Wait, some message pop on the phone, ignore it, phone reboot and root is okay, after you can do the steps for CSC, but when i said Recovery it's the stock recovery.
Edit : I forget one thing, when you connect the phone in usb debug,the phone show a pop up to allow or not debugging, the one must be yes, if not kingo can do nothing
Why are you changing the csc code? Your updates should work without changing the csc. If you decide to unroot everything is restored as well.
Sent from Heaven.
dallastx said:
Why are you changing the csc code? Your updates should work without changing the csc. If you decide to unroot everything is restored as well.
Sent from Heaven.
Click to expand...
Click to collapse
I also think it is not necessary, it is to be certain that there was no conflict or problem with other applications or network settings.
jerem52 said:
No need recovery for kingo, just download and install the program on PC, on the phone, turn on usb debugging, turn off reactivation lock and automatic upgrade (it may not necessary, it's to avoid surprise with upgrade ) connect the phone, wait on kingo, click Root, Wait, some message pop on the phone, ignore it, phone reboot and root is okay, after you can do the steps for CSC, but when i said Recovery it's the stock recovery.
Edit : I forget one thing, when you connect the phone in usb debug,the phone show a pop up to allow or not debugging, the one must be yes, if not kingo can do nothing
Click to expand...
Click to collapse
OK, I didn't know there was a stock recovery.
I thought recovery was always something related to root or smartphone tuning.
So if I understand well, I just have to :
- upgrade my Note 3 with the last official ROM (N9005XXUBMJ3_N9005OXXBMJ3_N9005XXUBMJ2_HOME.tar.md5)
- download and execute Kingo
And then my Note 3 should be BMJ3 with root access and knox still to 0x0.
PS: regarding your CSC issue, what was your ROM version before the BMJ3 ?
(maybe your CYO status was due to the BMJ1 ROM from SamMobile)
And how does it work with the updates? Unroot via superSU app, then enable OTA, update and after that again Kingo Tool to root again?
HokutoNoFred said:
OK, I didn't know there was a stock recovery.
I thought recovery was always something related to root or smartphone tuning.
So if I understand well, I just have to :
- upgrade my Note 3 with the last official ROM (N9005XXUBMJ3_N9005OXXBMJ3_N9005XXUBMJ2_HOME.tar.md5)
- download and execute Kingo
And then my Note 3 should be BMJ3 with root access and knox still to 0x0.
PS: regarding your CSC issue, what was your ROM version before the BMJ3 ?
(maybe your CYO status was due to the BMJ1 ROM from SamMobile)
Click to expand...
Click to collapse
Before it's branded with operator rom (BOG code > french Bouygues telecom, i dont remember version) i install latest version with kies recovery ( with french youtube video of unboxing, spot a S/N from a unlocked version and kies download the last unbranded version and install it :good: , but after, CSC code is CYO )
I use kingoo root because the MJ3 has a new bootloader and its nots possible for me to root with dela vega method, but it's not a "full root" some applications does not work, ( ex root unistaller ) maybe it's better fo you to root with de la vega, you have the root and the MJ3 but not the problematic last bootloader.
@ korny10 I dont try unroot, in download sytem is "Custom", i think a flash with stock rom and and everything was back to normal

[ROOT] How to root AT&T LG G3 - 3 Methods

ROOT FOR AT&T LG G3
Here are two ways to root the LG G3 on AT&T
AS OF NOW THERE IS NO ROOT FOR LOLLIPOP ON THE AT&T LG G3
Once a method is found thread will be updated...
First Method: TowelRoot by geohot - Does Not Work on 10F Or Later
1. Go to Phone Settings, then General Tab and click on Security
2. Scroll to Unknown sources and check the box and click on ok for the warning message
3. Use the phone browser to go to https://towelroot.com/
4. Click the Red lambda to download tl.apk
5. Install the downloaded file, click on accept when the Google popup shows
6. You will see a Google warning to not install - Click box stating "I understand and still want to install it" then click "Install Anyway"
(NOTE: remember you are installing an exploit to root the phone which is not something Google recommends.)
7.Once installation is complete click open or go to towel root icon and open app
8. Click "make it ra1n"
You now have root!!
To check,
Download root checker from play store and check for root
Click to expand...
Click to collapse
Second Method: IORoot by autoprime - Does Not Work on 10F Or Later
1. Go here and follow instructions:
http://forum.xda-developers.com/showthread.php?t=2776198
To check,
Download root checker from play store and check for root
2. Make sure to hit thanks on autoprime's thread.
Click to expand...
Click to collapse
Third Medthod: Stump Root by IOMonster - jcase - Autoprime - PlayfulGod - Team Codefire
1. Go Here
2. Download and install Stump root
3. Run Stump root - you are now rooted
4. Go to playstore and downlaod SuperSU
5. Install Super SU
6. Uninstall Stump Root
You now have root!!
To check,
Download root checker from play store and check for root
Click to expand...
Click to collapse
WARNINGS & DISCLAIMERS​
Proceed with caution and at your own risk - I am not responsible if your phone self destructs, gets bricked, or melts.
Please keep in mind that both these methods will yield ROOT only - as of know there is no way to unlock bootloader on AT&T
Rooting and any other modifications to your phone will void your warranty - do not root if you do not know what you are doing.
Rooted devices will not be able to receive OTA updates. You may have to unroot and restore stock in order to accept updates.​
How to check if you tripped the root counter
Once your device is rooted via either method - the device secret service menu will show that you are rooted.
To check:
1. Go to dialer
2. enter 3845#*850#
3. Scroll to and click on LG RCT
4. click Display Results
Here you will see that it shows the device is rooted
Once the device is unrooted - the setting will be reset to No Root
Additional Guides - After gaining root
How to Remove Bloatware on you newly rooted AT&T LG G3
How to unroot your LG G3 and return back to stock
My G3 from AT&T is on order and should be in my hands in a week or so. What firmware version comes with the phone out of the box? Should I root immediately to avoid any patches from being installed?
My reason for asking is based on my experience with the Moto X. I realized too late that accepting the standard upgrade to 4.4.2 via OTA would eliminate any chance of rooting. I want to make sure that I don't fall into that trap again.
Nucleonic said:
My G3 from AT&T is on order and should be in my hands in a week or so. What firmware version comes with the phone out of the box? Should I root immediately to avoid any patches from being installed?
My reason for asking is based on my experience with the Moto X. I realized too late that accepting the standard upgrade to 4.4.2 via OTA would eliminate any chance of rooting. I want to make sure that I don't fall into that trap again.
Click to expand...
Click to collapse
The current root-able firmware is 10D - Software Version: D85010d
Why not - better safe than sorry...
neverends said:
The current root-able firmware is 10D - Software Version: D85010d
Why not - better safe than sorry...
Click to expand...
Click to collapse
Are there any warranty software's like Samsung's Knox on this device? If so does rooting with towel root trip it?
http://forum.xda-developers.com/showthread.php?t=2819471
---------- Post added at 09:25 AM ---------- Previous post was at 09:23 AM ----------
mrhaley30705 said:
http://forum.xda-developers.com/showthread.php?t=2819471
Click to expand...
Click to collapse
According to a friend of mine, towelroot will not trip the QFuse, only the root counter. If you read post #2 on this thread that issue is addressed.
conan1600 said:
Are there any warranty software's like Samsung's Knox on this device? If so does rooting with towel root trip it?
Click to expand...
Click to collapse
QFuse will only be tripped if the recovery or rom is changed... The root counter will reset to No Root if you use the unroot method I posted
Sent from my LG-D850 using Tapatalk
Does it also remove the line about the first time you rooted? Also, when you say Rom is changed does that mean debloating/removing carrieriq/using xposed will trip it?
mrhaley30705 said:
Does it also remove the line about the first time you rooted? Also, when you say Rom is changed does that mean debloating/removing carrieriq/using xposed will trip it?
Click to expand...
Click to collapse
I rooted the phone using towel root - used Root Explorer to uninstall Bloat - installed Xposed and G3 TweakBox... then I checked to root checker in the hidden menu and it showed that it was rooted but the QFUSE was intact... then I unrooted using the method i posted.. Not only was the phone unrooted, traces of xposed installation were removed, and the root check in the hidden menu showed No Root with no additional information - also the QFUSE was still intact.
This is my experience and I have tested it twice. However... as always... Your mileage may vary...
Many thanks. I hate to sound like anoob, but this lg is new to me (coming from a gs3 where I avoided Knox counters until I sold the phone).
Working here. Thanks!
So let me ask you guys/gals is the bootloader locked than? Just need to find out before I go purchasing this phone through AT&T, thanks.
Knight-Rider said:
So let me ask you guys/gals is the bootloader locked than? Just need to find out before I go purchasing this phone through AT&T, thanks.
Click to expand...
Click to collapse
The bootloader is locked... Although you can root and install xposed, run root apps, and Debloat it's not likely that the bootloader will be unlocked anytime soon... So no custom recovery and no rooms.
Sent from my LG-D850 using Tapatalk
neverends said:
The bootloader is locked... Although you can root and install xposed, run root apps, and Debloat it's not likely that the bootloader will be unlocked anytime soon... So no custom recovery and no rooms.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I figured thanks for the quick response! I'm better off going with Korean version.
Is one of the methods better than the other? Just trying to decide which one to go with. Thanks
noticed when i run either root method SuperSU is not installed after. when i verify root under the the 2nd post, it says Rooted, Not allowed command has been excuted >su Rooting related file had been installed >su >superuser
vince2398 said:
Is one of the methods better than the other? Just trying to decide which one to go with. Thanks
Click to expand...
Click to collapse
The first method is very easy... They are both equally effective
idashx said:
noticed when i run either root method SuperSU is not installed after. when i verify root under the the 2nd post, it says Rooted, Not allowed command has been excuted >su Rooting related file had been installed >su >superuser
Click to expand...
Click to collapse
That's normal... Once you unroot the warning goes away and is cleared
Sent from my LG-D850 using Tapatalk
What about flashing recovery? Not to sure how to get twarp on this
Sent from my LG-D850 using XDA Premium 4 mobile app
I don't think twrp is ready for this.

Questions About Rooting Note Pro 12.2

Is this the most recommended method to root my Verizon Note 12.2? http://forum.xda-developers.com/showthread.php?t=2783950
Is this a permanent root? Will I be able to receive and install OTA updates from Verizon if I use this root and will the root be uninstalled as a result?
poetryrocksalot said:
Is this the most recommended method to root my Verizon Note 12.2? http://forum.xda-developers.com/showthread.php?t=2783950
Is this a permanent root? Will I be able to receive and install OTA updates from Verizon if I use this root and will the root be uninstalled as a result?
Click to expand...
Click to collapse
That's a good question . I'm looking to root without tripping Knox on my wifi version I just purchased off of ebay. I'm looking for an tar.md5 to start with.. Any help would be appreciated.
Same here. A White WiFi Note 12.2 64GB I bought off eBay, which according to Samsung's website, doesn't exist.
Hello,
Great tablet... I just got one off ebay myself and I see towelroot does not work- app not installed. I Allowed unknown sources in security. I am curious as to why you guys are concerned about tripping the knox since this I think this tablet would be out of warranty, unless you would not want to trip it for resale?
Any success on rooting so far? I am no too experienced but the first thing I'd like to do is get the apk from this enhanced s-note on all my other note tablets and phone.
oand QUOTE=LBJM;64430118]That's a good question . I'm looking to root without tripping Knox on my wifi version I just purchased off of ebay. I'm looking for an tar.md5 to start with.
Any help would be appreciated. Thanks.
tjmethod said:
Hello,
Great tablet... I just got one off ebay myself and I see towelroot does not work- app not installed. I Allowed unknown sources in security. I am curious as to why you guys are concerned about tripping the knox since this I think this tablet would be out of warranty, unless you would not want to trip it for resale?
Any success on rooting so far? I am no too experienced but the first thing I'd like to do is get the apk from this enhanced s-note on all my other note tablets and phone.
oand QUOTE=LBJM;64430118]That's a good question . I'm looking to root without tripping Knox on my wifi version I just purchased off of ebay. I'm looking for an tar.md5 to start with.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
I tried 2 different versions of Kingroot with no success.
Hi I used the cf auto root - check the 1st pic I attached. Once you plug in a windows pc it should download the samsung drivers then download that specific dl in the pic (I can't copynpaste on here)- it gives you the latest odin program download. It really easy from there. Once you reboot, supersu is there. I then dl'd root checker, titanium backup, busybox, root explorer and most important twrp manager from the play store. It was all too easy. I'm on 5.02 and I did check the knox and it started but stopped and said it couldn't be accessed at this time. I'm keeping the stock rom and just wiped dalvik and cache in recovery.
Rolldog said:
I tried 2 different versions of Kingroot with no success.
Click to expand...
Click to collapse
poetryrocksalot said:
Is this the most recommended method to root my Verizon Note 12.2? http://forum.xda-developers.com/showthread.php?t=2783950
Is this a permanent root? Will I be able to receive and install OTA updates from Verizon if I use this root and will the root be uninstalled as a result?
Click to expand...
Click to collapse
The most effective way to root this tablet is with Cf-autoroot. It will trip the Knox counter but it will permanently enable SuperSU on your device.
If you root your device you will NOT be able to take OTAs. If you run rooted stock firmware it will alert you that an update is available but most likely it will fail to install. I tried updating my firmware while rooted via Kies and it failed each time.

[Completed] I need help passing safetynet!

So I have a galaxy s4 active and I rooted a while back with kingroot I know it isn't good but I did it anyway... and unistalled king root completely and supposedly should have removed my root. So I was trying to play Pokemon Go after recently purchasing a pokemon go plus and I can't play and it is because of safetynet even though I have no root. I realized that when I boot up my s4 a screen with a padlock icon and text that says custom appears. I thought this may mean my bootloader is unlocked and that this could trigger me failing safety net. I have been looking every where on how to relock my bootloader. I just want to pass that safety net baloney.
MillaShows said:
So I have a galaxy s4 active and I rooted a while back with kingroot I know it isn't good but I did it anyway... and unistalled king root completely and supposedly should have removed my root. So I was trying to play Pokemon Go after recently purchasing a pokemon go plus and I can't play and it is because of safetynet even though I have no root. I realized that when I boot up my s4 a screen with a padlock icon and text that says custom appears. I thought this may mean my bootloader is unlocked and that this could trigger me failing safety net. I have been looking every where on how to relock my bootloader. I just want to pass that safety net baloney.
Click to expand...
Click to collapse
Greetings and welcome to assist. Try installing latest stock firmware for your device with odin or kies/smartswitch
Regards
Sawdoctor
I used smartswitch and I have the latest firmware
So I used smartswitch and it said I had the latest firmware what now?
I tried everything
So smartswitch said my device isn't compatible to initialize (sgh-i537) so I tried using Odin to return to stock but the only firmware avaliable for my device is kitkat and I have lollipop so I cant downgrade can I? Even then I get and error in download mode saying fail secure download: boot or something like that. If I hard reset through the stock recovery will I be able to pass safetynet I even tried triangle away because I thought maybe it had something to do with my system being custom and it needed to be official and triangle away didn't even work I tried rooting again just so I could rename the su files to su1 which people said would let you play that didn't work either I looking how get magisk I couldn't do it. Is there anyway I can fully go back to stock that will work and will allow me to pass safetynet I am not concerned about root currently I don't need it.

Samsung Galaxy S7 (SM-930F) displaying "security log agent" notification after root

Is this something that happens when you root a Samsung phone or my device has been compromised by shady software?
It is my first time rooting an smartphone and it seems that bank apps won't allow rooted phones. I am thinking about flashing an official rom to fix these issues.
By the way, I used this guide to successfully root my device:
dbpsychodelic said:
Is this something that happens when you root a Samsung phone or my device has been compromised by shady software?
It is my first time rooting an smartphone and it seems that bank apps won't allow rooted phones. I am thinking about flashing an official rom to fix these issues.
By the way, I used this guide to successfully root my device:
Click to expand...
Click to collapse
If you are on the stock rom then yes, it will show security log agent notif.
And you wont be able to use banking apps on rooted phones on any rom official or unofficial.
You can try using magisk hide but i've never tried it so not sure if it will work.

Categories

Resources