Database Users

[Q] Google security updates and my privacy?

this morning i had an note from google that towelroot was on my phone and that i should remove it. my question is
1. att s5 850
2. rooted with towelroot
3. running root cloak and Xprivacy
4. updates frozen with TB att, google, knox
my question is " how did google know?" and what am i doing wrong to not allow apps or rooting to be seen?
patrick

Because Verify apps in Google settings is turned on
Sent from my LG-D802

Also, towel root tells you to Uninstall after rooting, because the app no longer has any function or use.

thanks mwedo and finndo
maybe one or both may have some advice on this question.
with device rooted how do i treat OTA updates and security updates. i installed SU as a system app. will this work to maintain root?
thanks in advance for any advice
patrick

On vast majority of phones you don't get OTA at all when device is rooted. Standard updates like flashing ROM manually or going normal through PC Suite (or whatever its name is - depends on brand) will keep your root if normal update is performed. If update is done with/after full format then root is usually gone so you need to re-root.
Sent from my LG-D802

Galaxy S5 G900F XXU1POJ1 - Need help & advice ROM/Root

Hello,
as thread title says, I need some advice from professionals here for my new Galaxy S5.
Well it's not quite new (almost 1 year) but never rooted it or flashed it, so I still got OS (original system) by Samsung.
I am a pretty amateur on such stuff. First I need some advice what to do: Rec & Root or flash custom rom?
Followng things are important to me:
The System has to be stable and fast: no lags, no crashes, no errors (I do not expect 100% stability, since not even OS is 100% stable, but it has to be at least stable as OS or even a bit more)
I need features and nice widgets (Rom must also be afordable to other apps and widgets, I 'd prefer Samsung OS widget)
I need good quality on camera (preferred OS cam software and features)
Good signal and GPS (Good and fast GPS is a MUST!!, as I use often Navigon when I travel with my car)
Good video player and galery app (Preferred Samsung OS Galery App, but video player can also be different than Samsung OS Video Player if its working fine)
What I do not do with my phone:
I do not play games
I do not read e-books
I don't understand the purpose of KNOX! Do I need it really?
Here are some details of my Smartphone:
Model no: SM-G900F
Android version: 5.0
Modem version: G900FXXU1POJ1
Kernel version: 3.4.0-6364590
Build number: LRX21T.G900FXXU1POK5
Securitysoftware version: MDF v1.1 release 4 / VPN v1.4 Release 3
I would be greatful if someone could give an advice if it is worth to flash a custom rom and if yes what rom based in what moden and kernel versions or if a simple root with recovery install is enough?.
Thanks in advance
Regards

Hi @GordonSpace.......
Most of what you said in your post leads me to believe that there are many things about the stock OS that you are happy with. That being the case, the old adage 'if it ain't broke, don't fix it' comes to mind.....meaning (for now) you might as well stay with stock. If you start flashing CM custom roms (for example) you will lose that look and feel.
On to your question about Knox.....
In a nutshell, knox is based around an 'eFuse' which will trip or blow as soon as you modify your device. This eFuse CANNOT be reset. Samsung are, in some cases, denying warranty repairs on devices where knox has been tripped.
So basically, as soon as you flash CF Root or TWRP to gain root, your warranty is void (Samsung normally provide a 2 year warranty on their devices). Tripping knox will also prevent future 'over the air' updates. So even if you unrooted your device you would be stuck with the version of the OS that you have on your device. Finally, tripping knox will prevent your device from connecting to 'business enterprise secure' servers. So if you currently use your phone on your employers network, this will no longer be possible.
If you still want to go ahead and forget about knox, this is the easiest way to gain root......
Follow exactly....
1) deactivate 'Reactivation Lock' (can be found under Security in Settings).
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
TWRP 2.8.7.0 by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
When you have root access, you can get Titanium Backup from the playstore and freeze/delete the 'bloatware' that comes pre - installed on Samsung firmwares.
That will then give you the stability of the software designed for the phone coupled with the look and feel that you like, but without the resource hogging rubbish that most people with unrooted phones have to put up with......
http://i.imgur.com/rVnFwJM.jpg

thanks
keithross39 said:
Hi @GordonSpace.......
Most of what you said in your post leads me to believe that there are many things about the stock OS that you are happy with. That being the case, the old adage 'if it ain't broke, don't fix it' comes to mind.....meaning (for now) you might as well stay with stock. If you start flashing CM custom roms (for example) you will lose that look and feel.
On to your question about Knox.....
In a nutshell, knox is based around an 'eFuse' which will trip or blow as soon as you modify your device. This eFuse CANNOT be reset. Samsung are, in some cases, denying warranty repairs on devices where knox has been tripped.
So basically, as soon as you flash CF Root or TWRP to gain root, your warranty is void (Samsung normally provide a 2 year warranty on their devices). Tripping knox will also prevent future 'over the air' updates. So even if you unrooted your device you would be stuck with the version of the OS that you have on your device. Finally, tripping knox will prevent your device from connecting to 'business enterprise secure' servers. So if you currently use your phone on your employers network, this will no longer be possible.
If you still want to go ahead and forget about knox, this is the easiest way to gain root......
Follow exactly....
1) deactivate 'Reactivation Lock' (can be found under Security in Settings).
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
TWRP 2.8.7.0 by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
When you have root access, you can get Titanium Backup from the playstore and freeze/delete the 'bloatware' that comes pre - installed on Samsung firmwares.
That will then give you the stability of the software designed for the phone coupled with the look and feel that you like, but without the resource hogging rubbish that most people with unrooted phones have to put up with......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Hello keithross and thank you for your response.
I use my smartphone only in private.
However it still has 11 months warranty by Samsung. Another Idea I had was to sell my Galaxy S5 as it is (OS and Knox) and buy another smartphone.
However what would be your recommendation for a new smartphone?
I was thinking about LG or HTC. But I'm not sure about to purchase a "famous" brand device or just a cheap one like Mobistel, Huawai and such.
What is a nice smartphone to have it root / flashed?
Regards
Kiri

I have about 9 months of warranty left on my phone....but I was able to root without tripping knox.....simply because I rooted before I allowed my phone to update to Lollipop (I rooted with Towelroot while running KitKat) then debloated, and customised the stock firmware.....so I have my phone as I want it, and still have knox intact.
The S5 will probably be my final Samsung smartphone, but as of this moment, I haven't given much thought as to what I'll replace it with. I'm half tempted to keep it beyond the end of it's warranty and start trying out custom roms at that point. It does everything I want it to do, so why would I need to replace it?
On the other hand, if i did replace it, I'd probably stay with one of the well known brand names.....The chances are that they'll have more dev support than the less popular makes of device....but I won't waste my money on any more flagship devices, I'll probably look at the 'upper midrange' devices as they'll (by that time) probably have similar specs to my current device (the way technology is currently advancing, they may even be superior to the S5)......
http://i.imgur.com/rVnFwJM.jpg

CyanogenMod
I decided to flash cyanogenmod snapshot
1. However I do not understand the difference between klte and kltedv rom (kltedv = vodafone. does that mean my provider has to be vodafone?)
2. TWRP or Cyanogen Recovery?
3. Do I need to install a diff Kernel version?
4. Anything I should take care about before I flash? (something special about Samsung drivers, kernel, odin etc...?)
Thx for your support.

1....In all honesty I can't answer having never flashed custom to my S5.
2....TWRP recovery over Cyanogen recovery....Every time. Cyanogen recovery is little better (if at all) than stock recovery.
3....flashing a different kernel isn't strictly speaking necessary....unless you want to be able to change processor clock speeds and voltage and apply various other specialist 'tweaks'.....
4....after rooting (but before flashing) make a backup of your EFS folder (critically important) it contains, amongst other things, your IMEI number. If this folder becomes corrupted, you're in a whole world of hurt....
Back up any personal data that you can't afford to lose....things like photos etc.
Make sure you have a copy of your current firmware available....If it all goes pear shaped, you'll possibly need it to recover your phone.
The version of Odin that has most compatibility with the S5 is v3.10.7 though other versions *should* work.
Get hold of and install the Samsung USB drivers on your pc....They come bundled with Kies available on Samsung's website. (If you install Kies, you will need to use task manager on your pc to kill the kies processes prior to flashing anything with Odin).
Use the usb cable that came with your phone when connecting it to your pc.
Make sure you've disabled your firewall and antivirus before attempting to use Odin.
If you need any more help just let me know by commenting below.....
Luck fella
http://i.imgur.com/rVnFwJM.jpg

Hey thanks mate. I rooted my device with CF autoroot via odin. I read that CM13 with Android 6 is as a stable version out now. Probably I am gonna flash it. However, I have a question with my current root of S5. Currently the wifi passwords are being save as an encrypted hex key in the wifi_supplicant.conf file. However I would like to use an app that saves and shows my wifi passwords, but unfortunately due to the encryption of S5 it's not a help for me. Any recommendations what can I do to save the real PW instead of the encrypted key?

Sorry fella....The tech aspects of your question have gone right over my head like an international Jumbo Jet....I have no idea what you're even asking about, let alone how to solve it for you. Your best bet would be to create a thread specifically for this question.....you will probably get more views for that thread than for this one.....sorry mate....
http://i.imgur.com/rVnFwJM.jpg

GordonSpace said:
Hey thanks mate. I rooted my device with CF autoroot via odin. I read that CM13 with Android 6 is as a stable version out now. Probably I am gonna flash it. However, I have a question with my current root of S5. Currently the wifi passwords are being save as an encrypted hex key in the wifi_supplicant.conf file. However I would like to use an app that saves and shows my wifi passwords, but unfortunately due to the encryption of S5 it's not a help for me. Any recommendations what can I do to save the real PW instead of the encrypted key?
Click to expand...
Click to collapse
You should already know the passwords if they are your routers/APs

I don't know my passwords. The thing is, that sometimes we go to some cafés and such where I have saved the PW of the router, but sitting with friends some of them do not have it to connect with wifi. Thats why I am asking if there is a possibility to view the passwords I saved in my wifi connections (not as a hex key but the true passwords). Anyway.. thx for help. I guess thats Samsung OS. Hope it won't be with CM13 like this.

Warning KingoRoot causes DM Verification failure, Kingroot seem to be Okay

II don't want to be an alarmist but back on 17th June 2016 I created this thread DM Verification failure , Please flash ENG binary then install DNK
At the time I wasn't sure what had caused the problem but last night with a different phone I used KingoRoot and it corrupted a second phone of mine. Now two out of three of my Verizon Note 4's have the dm-verification-failure.
The symptoms of the problem are when I am navigating some of the swipes lag. Sometimes when typing there is a lag delay before it is entered. Sometimes Wifi lags before it is turned on and the phone forgets my wifi password.
I found this thread How to solve dm-verity verification failed/need to check drk first on samsung devices but I don't have the experience to do it. Can a developer create the fix for the Verizon Note 4 , PLEASE, Thanks

doctor-cool said:
II don't want to be an alarmist but back on 17th June 2016 I created this thread DM Verification failure , Please flash ENG binary then install DNK
Now two out of three of my Verizon Note 4's have the dm-verification-failure.
Click to expand...
Click to collapse
I am at the end of consolidating all the info I can to determine if I should get a Note 4. Root is the thing that matters to me, but I have learned that regardless of 4.4.4 or 5.1.1 you have to unlock the bootloader which is the challenge.
Just as I think I have it all together and that the methods provided (on XDA only) are the only only ones available and apparently stable, I read this.
Am I COMPLETELY MISUNDERSTANDING your post? Is your post from here http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527 which I've saved as reference for rooting a device no longer accurate?
I'm overwhelmed from so much research and think I've curated the posts that matter, then I see this. Can you offer anything on this? Again, I may not be understanding. I am NOT a developer or programmer. I've rooted a few devices, but it has been a long time with the most recent not requiring the seeming complication of this one (thanks a lot, Verizon!).

jecilop said:
I am at the end of consolidating all the info I can to determine if I should get a Note 4. Root is the thing that matters to me, but I have learned that regardless of 4.4.4 or 5.1.1 you have to unlock the bootloader which is the challenge.
Just as I think I have it all together and that the methods provided (on XDA only) are the only only ones available and apparently stable, I read this.
Am I COMPLETELY MISUNDERSTANDING your post? Is your post from here http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527 which I've saved as reference for rooting a device no longer accurate?
I'm overwhelmed from so much research and think I've curated the posts that matter, then I see this. Can you offer anything on this? Again, I may not be understanding. I am NOT a developer or programmer. I've rooted a few devices, but it has been a long time with the most recent not requiring the seeming complication of this one (thanks a lot, Verizon!).
Click to expand...
Click to collapse
The stabilized-process-to-unlock-bootloader I posted is still valid. I recommended using Kingroot. I found the dm-verity problem with KingORoot. We need more feedback to be sure. I never had the problem with Kingroot. I removed the link to KingORoot from my guide today.

doctor-cool said:
The stabilized-process-to-unlock-bootloader I posted is still valid. I recommended using Kingroot. I found the dm-verity problem with KingORoot. We need more feedback to be sure. I never had the problem with Kingroot. I removed the link to KingORoot from my guide today.
Click to expand...
Click to collapse
Hmmm..ok..thanks for the reply.
That's interesting as I've read so many posts that say KingRoot is not the way to go but rather KingOroot is the correct on to use. Specifically, a lot of people seemed to have tried it unsuccessfully in the process.
I was also hoping to avoid KR as I've read it is a bit sketchy. I've used it twice before doing that and found a Nextbook tablet it worked great on with seemingly no apparent problems since. Another Samsung phone was rooted with it (I was actually searching for KOR, but didn't remember the name exactly and ended up with KR on a search). Unfortunately, the security pop-up keeps coming up trying to remove it. The user who didn't know what they were doing inadvertently gave it the OK to remove it, and now I haven't been able to re-root with it...arrggh..
I recently thought to install their Purify app (which they push when doing KingRoot) separately, but the permissions in the app say that you give it the ability to analyze the content on the screen in an window...I can't figure how THAT is needed to block startup programs or background one to save battery!
So, I was hoping this meant the KOR was good to go with the process after the bootloader is unlocked and stable per your post. I wonder if anyone else is running into problems. I know this is all very new still.
I don't suppose you could tell me:
1) Is permaroot available (with these new methods) only on 5.1.1 , or is it also available on 4.4.4 ? I haven't been able to decipher that.
I kind of prefer KitKat over the material design changes that are just wasting space on my screen in JellyBean. The Note 4 I got to purchased recently (unfortunately, it was a sketchy phone now being returned), had notifications on constant screen overflow because they waste SO MUCH SPACE with them and with unnecessary notifications that I cannot stop from showing (Power Saving, Wif connected, Blocking on). I know a good bit of that is Samsung, but the non-compact use of the notifications is Android ( Google's changes). It was better on my SG3 with 4.4.4 even though they still has persistent notifications.
I'm hoping to root and find a mod to stop showing those. I'm aware enough to check my connections via the settings when needed.
Thanks Again.

jecilop said:
Hmmm..ok..thanks for the reply.
That's interesting as I've read so many posts that say KingRoot is not the way to go but rather KingOroot is the correct on to use. Specifically, a lot of people seemed to have tried it unsuccessfully in the process.
I was also hoping to avoid KR as I've read it is a bit sketchy. I've used it twice before doing that and found a Nextbook tablet it worked great on with seemingly no apparent problems since. Another Samsung phone was rooted with it (I was actually searching for KOR, but didn't remember the name exactly and ended up with KR on a search). Unfortunately, the security pop-up keeps coming up trying to remove it. The user who didn't know what they were doing inadvertently gave it the OK to remove it, and now I haven't been able to re-root with it...arrggh..
I recently thought to install their Purify app (which they push when doing KingRoot) separately, but the permissions in the app say that you give it the ability to analyze the content on the screen in an window...I can't figure how THAT is needed to block startup programs or background one to save battery!
So, I was hoping this meant the KOR was good to go with the process after the bootloader is unlocked and stable per your post. I wonder if anyone else is running into problems. I know this is all very new still.
I don't suppose you could tell me:
1) Is permaroot available (with these new methods) only on 5.1.1 , or is it also available on 4.4.4 ? I haven't been able to decipher that.
I kind of prefer KitKat over the material design changes that are just wasting space on my screen in JellyBean. The Note 4 I got to purchased recently (unfortunately, it was a sketchy phone now being returned), had notifications on constant screen overflow because they waste SO MUCH SPACE with them and with unnecessary notifications that I cannot stop from showing (Power Saving, Wif connected, Blocking on). I know a good bit of that is Samsung, but the non-compact use of the notifications is Android ( Google's changes). It was better on my SG3 with 4.4.4 even though they still has persistent notifications.
I'm hoping to root and find a mod to stop showing those. I'm aware enough to check my connections via the settings when needed.
Thanks Again.
Click to expand...
Click to collapse
I can only report my findings. We need more feedback.

The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.

blindmanpb said:
The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.
Click to expand...
Click to collapse
Thanks, I like the way you think.
Is there some file I can take from a good working Note 4 and repair the DM verification issue ? Do you think I could do it with efs Profestional. Just wondering.

I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.

raduque said:
I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.
Click to expand...
Click to collapse
I think, You would only see the DM Verity" messages when you are in stock recovery. Once you log into your google account, it remembers your passwords. But on my phoneS, I still get the other lagging problems. What ROM are you on?

blindmanpb said:
The only real negative I've noticed with KingRoot is that it's erased the serial numbers from both of the phones I've used it on. Thankfully it didn't affect the IMEI, but whenever I try to check the serial number on those two devices, it just shows a bunch of zeros. Back up your EFS partition first (if you can without being rooted, I'm not sure), or at least make a note of the serial number. You can manually edit /efs/FactoryApp/serial_no to restore your serial number as long as you know what it is. I don't believe the serial number is used for anything (except maybe warranty-related things), just annoys me that KingRoot erased it.
As far as removing KingRoot, after you unlock the bootloader you can flash a modified stock firmware file for the phone (one that has had aboot.mbn removed) and still retain an unlocked bootloader. Flashing anything with an aboot.mbn will re-lock your bootloader, so be sure you remove that from any Odin tars before flashing. I had access to the full factory firmware for the device (containing the PIT file and a couple of other partitions not found in the home firmware files hosted by sites like SamMobile) so I stripped aboot.mbn from it and flashed that to make sure I started with a clean, KingRoot free device.
Click to expand...
Click to collapse
That why I kept the original box with the serial numbers on it lpl
Sent from my SM-N910V using Tapatalk

raduque said:
I initially used KingRoot, and it failed 20 out of 20 times to root my phone. I used KingOroot on my laptop (in a VM) and it rooted my phone first try. I don't have any Wifi issues and I don't see any "DM Verity" messages anywhere on my phone.
Click to expand...
Click to collapse
Same here, only I used the Kingoroot APK, no issues on either the retail or DE. On JasmineROM (6.0 on the DE and 7.0 on the retail)

fz798 said:
Same here, only I used the Kingoroot APK, no issues on either the retail or DE. On JasmineROM (6.0 on the DE and 7.0 on the retail)
Click to expand...
Click to collapse
The lag is most apparent on stock rom that I rooted with KingOroot apk. On CyanogenMod it is more like a hesitation. The damage is so far as I know irreversible.
The other phone that has only been rooted with KingRoot is a a factory DE it does not have the DM Verification issue and it runs as smooth as silk on every ROM I have tried. So I say the problemS came from KingOroot. But we need more data points/ feedback to be sure.

pfcland said:
That why I kept the original box with the serial numbers on it lpl
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Verizon Note 4 does not list serial number on the box, unfortunately.

Can you post a short video detailing the issues and is there something I can do to immediately verify if there is a dm verification problem with my device? I also used Kingoroot on my Note 4 due to KingRoot not working after several tries, but I don't notice anything out of the ordinary, just the usual ocassional lag that is on every Android device.
Only noticeable issues I've experienced have been the "Unauthorized Actions Detected" issue and Wifi passwords not saving using PaulPizz 6.0.1/OscarKernel, but that was corrected with the freezing of a couple Samsung security apps and a build.prop edit.

NeoandGeo said:
Can you post a short video detailing the issues and is there something I can do to immediately verify if there is a dm verification problem with my device? I also used Kingoroot on my Note 4 due to KingRoot not working after several tries, but I don't notice anything out of the ordinary, just the usual ocassional lag that is on every Android device.
Only noticeable issues I've experienced have been the "Unauthorized Actions Detected" issue and Wifi passwords not saving using PaulPizz 6.0.1/OscarKernel, but that was corrected with the freezing of a couple Samsung security apps and a build.prop edit.
Click to expand...
Click to collapse
I'm working this now FIx DRK/dm-verity, Factory CSC and Serial Number So far I have been able to restore my serial#. after I turned on the hidden menu.You have to be in stock recovery to see the dm-verity verification failed message. You would have to Odin back to stock to see it.
Lag is not normal unless you have a ton of apps running. ., Wifi passwords not saving is not normal not even once , I bet you got the bug.

Maybe, but I don't have the wifi passwords issue unless I flash OacarKernel over either Jasmine or Paulpizz, stock kernels are OK in that regard.
How bad of a lag are we talking about? Slight hesitation or full on freezes for more than a second at a time?
After a few weeks of using the device with custom ROMs, no lag spikes have been out of the ordinary for me, feels more responsive than my Note 3 and noticeably better than both the Nexus 6/Moto X I've previously used.
The only truly frustrating lag spikes I've noticed are trying to use this site without any form of adblock on Chrome.

NeoandGeo said:
Maybe, but I don't have the wifi passwords issue unless I flash OacarKernel over either Jasmine or Paulpizz, stock kernels are OK in that regard.
How bad of a lag are we talking about? Slight hesitation or full on freezes for more than a second at a time?
After a few weeks of using the device with custom ROMs, no lag spikes have been out of the ordinary for me, feels more responsive than my Note 3 and noticeably better than both the Nexus 6/Moto X I've previously used.
The only truly frustrating lag spikes I've noticed are trying to use this site without any form of adblock on Chrome.
Click to expand...
Click to collapse
The Best example is scrolling lagging on this site with Chrome. My phone without the issue is as smooth as silk. No hesitation. The phones with the bug maybe two swipes work then the third swipe lags then the page jumps to catch up. It is uncomfortable to use.

XDA forums have been fine for me in Chrome since I installed an ad blocker not too long ago. Before that I would get annoying pauses and skips, like you're talking about. Though this also happened on my Note 3/Moto X/Nexus 6 as well on this site.
Is there any way to see if any running processes have large latency spikes when these lags/pauses occur?
Also is there another kernel I can try on PP 6.0.1 ROM or a way to easily flash the stock kernel on it without restoring a backup? Seems like the minor issue with Wifi only crops up with OscarKernel.

doctor-cool said:
I'm working this now FIx DRK/dm-verity, Factory CSC and Serial Number So far I have been able to restore my serial#. after I turned on the hidden menu.You have to be in stock recovery to see the dm-verity verification failed message. You would have to Odin back to stock to see it.
Lag in not normal unless you have a ton of apps running. ., Wifi passwords not saving is not normal not even once , I bet you got the bug.
Click to expand...
Click to collapse
Verizon devices do not have the typical Samsung serial number. The only serial number your device uses in the last 32 bits of your eMMC CID. The EFS serial number is supposed to be 00000000, and will not affect any functionality of your device. You had your DRK (Device Root Key) erased. It could have been from damage to the EFS partition or something else benign. You'll want to flash complete stock Odin, reboot to recovery and wipe data, and reboot. This should fix your issue, but if it doesn't, let me know and we'll cross that bridge.
In response to OscarKernel not saving WiFi passwords, it's an issue related to ROMs and not my kernel. It does not use secure_storage, so setting ro.secure_storage=false is necessary, and once done, everything will go back to normal and save fine.

ryanbg said:
Verizon devices do not have the typical Samsung serial number. The only serial number your device uses in the last 32 bits of your eMMC CID. The EFS serial number is supposed to be 00000000, and will not affect any functionality of your device. You had your DRK (Device Root Key) erased. It could have been from damage to the EFS partition or something else benign. You'll want to flash complete stock Odin, reboot to recovery and wipe data, and reboot. This should fix your issue, but if it doesn't, let me know and we'll cross that bridge.
Click to expand...
Click to collapse
The tutorial I was following was for the SM-N910C not the SM-N910V . For that device, magix01 has a tutorial to fix DRK. I was working on the premise that if I could repair the serial number, I could then use emergency software recovery. Thanks for straightening me out about the serial number. Put that aside for now.
I did Odin N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar several times downloaded directly from SamMobile and did the data wipe and rebooted every way possible I think. I still get the dm-verity failure and more importantly, It still has the lag bug. I have in my possession another SM-N910V that does not have any issues. I was wondering if I could take a file from the good phone and use it to fix the defective phone. Thanks, for your help, I am ready to cross that bridge.

Accidentally deleted Knox app

Hi everyone!
Today I did a stupid thing- I'm going to factory reset my phone and was looking for a way to backup my Knox data. Sadly, I found an outdated link to a Samsung site that said I will get a prompt to backup when I uninstall the app. Without much thinking, I hit "Uninstall". To my terrified surprise- I didn't get a backup prompt. I quickly installed Knox again, but the data was gone.
Is there any way to retrieve it? The phone isn't rooted or anything, running stock FW.
Many thanks for your help, I greatly appreciate it

I don't know.. but maybe Smart Switch? Try that.. also I don't understand how the Uninstall can backup something.. when it's basic uninstall

The whole purpose of Knox is that you cant recover anything from it of you uninstalled it or tampered your device. Ever.

Heeeeeellllppp!!!
I rooted my Samsung Galaxy S3 with kingroot. I wanted to replace it with SuperSU using SuperSU me. So I deleted a few things from Knox including Knox migration agent trying delete Knox completely to make it easier for SuperSU. Well I didn't have any problems until I did the final reset to install super su. Now when I boot up I continuously you get the air Knox migration agent has stopped. It won't even get to my password screen. Anyway I can download a Knox migration agent zip to my SD card and install it via recovery? Please helplll£

Flash stock rom?

Features availability without root

Hello, I'm trying to figure out if I understand everything correctly
1. Root always means knox counter goes >0
1.1. That always means Samsung Pay won't work even with magisk and stuff?
1.2 What else won't work? I've read Samsung Health might be not working, but I'm not sure why as it's perfectly working on unhidden root devices.
2. Adblocking w/o is possible? Disconnect Pro is only option?
3. bixby button is mappable to anything except actions like "imediately take picture"?
4. removing bloatware is possible with Package Disabler, right?
5. What is optimal non-root backup solution that would backup both app and data? I know Helium does that with USB Debugging, but I think Samsung should have something on it's own, right? Also How good is Samsung solution for non-Samsung phones?
6. Is USB debugging working fine? I'm concerned as heard using Secure Folders disabled it. That's the only thing to be aware of?
Thx

Ryotsuke said:
Hello, I'm trying to figure out if I understand everything correctly
1. Root always means knox counter goes >0
1.1. That always means Samsung Pay won't work even with magisk and stuff?
1.2 What else won't work? I've read Samsung Health might be not working, but I'm not sure why as it's perfectly working on unhidden root devices.
2. Adblocking w/o is possible? Disconnect Pro is only option?
3. bixby button is mappable to anything except actions like "imediately take picture"?
4. removing bloatware is possible with Package Disabler, right?
5. What is optimal non-root backup solution that would backup both app and data? I know Helium does that with USB Debugging, but I think Samsung should have something on it's own, right? Also How good is Samsung solution for non-Samsung phones?
6. Is USB debugging working fine? I'm concerned as heard using Secure Folders disabled it. That's the only thing to be aware of?
Thx
Click to expand...
Click to collapse
1.1 About Samsung pay, AFAIK, it won't work. At least for now.
1.2 Secure folder won't work as well.
2. There are many options for root adblocking.. In fact, very few available for non-root devices.
3. AFAIK, no. Need to open the camera app and press the capture button.
4. Hadn't info for that since never attempted one.. Sorry..
5. There is a PC option.. I heard it is named Samsung switch or something else? Never tried it so can't say much.. The last time I'm using backup un-rooted is using helium, and I think it is good one already..
6. Never tried using USB debugging, so can't say much..
Hope this partially helps..

Ryotsuke said:
Hello, I'm trying to figure out if I understand everything correctly
1. Root always means knox counter goes >0
1.1. That always means Samsung Pay won't work even with magisk and stuff?
1.2 What else won't work? I've read Samsung Health might be not working, but I'm not sure why as it's perfectly working on unhidden root devices.
2. Adblocking w/o is possible? Disconnect Pro is only option?
3. bixby button is mappable to anything except actions like "imediately take picture"?
4. removing bloatware is possible with Package Disabler, right?
5. What is optimal non-root backup solution that would backup both app and data? I know Helium does that with USB Debugging, but I think Samsung should have something on it's own, right? Also How good is Samsung solution for non-Samsung phones?
6. Is USB debugging working fine? I'm concerned as heard using Secure Folders disabled it. That's the only thing to be aware of?
Thx
Click to expand...
Click to collapse
2 - https://forum.xda-developers.com/galaxy-s8/themes/adhell-2-rootless-ad-blocking-t3663559
4 - https://forum.xda-developers.com/galaxy-s8/how-to/how-to-remove-oem-bloatware-s8-s8-t3654687
3 -bxactions, click to open and then click again to take pic

Ryotsuke said:
Hello, I'm trying to figure out if I understand everything correctly
1. Root always means knox counter goes >0
1.1. That always means Samsung Pay won't work even with magisk and stuff?
1.2 What else won't work? I've read Samsung Health might be not working, but I'm not sure why as it's perfectly working on unhidden root devices.
2. Adblocking w/o is possible? Disconnect Pro is only option?
3. bixby button is mappable to anything except actions like "imediately take picture"?
4. removing bloatware is possible with Package Disabler, right?
5. What is optimal non-root backup solution that would backup both app and data? I know Helium does that with USB Debugging, but I think Samsung should have something on it's own, right? Also How good is Samsung solution for non-Samsung phones?
6. Is USB debugging working fine? I'm concerned as heard using Secure Folders disabled it. That's the only thing to be aware of?
Thx
Click to expand...
Click to collapse
#1 is not true and a common falsehood repeated here often.

partcyborg said:
#1 is not true and a common falsehood repeated here often.
Click to expand...
Click to collapse
I would appreciate if that was supported by some kind of links. 100% of information I've seen so far is "knox counter is not revertible" and "with knox>0 Samsung Pay, Samsung Health and Secure Folder won't work"

Ryotsuke said:
I would appreciate if that was supported by some kind of links. 100% of information I've seen so far is "knox counter is not revertible" and "with knox>0 Samsung Pay, Samsung Health and Secure Folder won't work"
Click to expand...
Click to collapse
Knox the efuse backed device in your phone which turns 0x1 and is not reversable has absolutely nothing to do with whether your device is rooted or not. It is concerned with only one thing, and that is has your device had unsigned boot images written to it. That's it, full stop. In fact, it is currently 100% for a snapdragon (n America) device to *ever* be 0x1 because the bootloader is locked and therefore it is impossible to flash any unsigned code in the first place.
I can provide you with links saying that a thing is not affected by another thing because, well, they aren't related. I would be hard pressed to find proof that monkeys don't fly out of my ass either, but I can assure you they don't.
The reason for the pervasiveness of this incorrect information is that the installation methods of some root management systems involve the writing of a custom boot image, usually to get around things like selinux without compromising safetynet. However it is that boot image patch&flash that causes 0x1, it would happen whether you also rooted or not, and if you choose a traditional systemroot (and have a signed kernel that is permissive, but all Samsung's do), then you can be rooted all day and knox isn't even capable of knowing much less changing your unsigned flash count

partcyborg said:
The reason for the pervasiveness of this incorrect information is that the installation methods of some root management systems involve the writing of a custom boot image, usually to get around things like selinux without compromising safetynet. However it is that boot image patch&flash that causes 0x1, it would happen whether you also rooted or not, and if you choose a traditional systemroot (and have a signed kernel that is permissive, but all Samsung's do), then you can be rooted all day and knox isn't even capable of knowing much less changing your unsigned flash count
Click to expand...
Click to collapse
But is there a root for S8 (Exynoss one G950FD to be specific) that is not triggering knox->1? I kinda assumed such thing does not exists, would be happy to know I'm wrong. If there is zero-knox root, is it still hideable like magisk to be still able to pass SafetyNet?