Database Users

[Q] How to root Note 3 with tripping Knox

I have a new Note 3 with 4.3. I'd like to do the following things:
* update to 4.4.2 (is it better to stay with 4.3 if I care about the other things I'm going to enumerate here?)
* root it, I don't care about knox
* remove most of Samsung bloatware (I like the clock and the pen stuff and would like to keep them) - does titanium backup still work for this, what do I have to care about to not brick the phone?
* install adblock and afwall
* all that without the need for a samsung online account
Are there any step-by-step instructions for these things, especially for rooting?
Phone data:
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005VFGDMJ1
SELinux: SEPF_SM-N9005_4.3_0011

dark$hadow said:
I have a new Note 3 with 4.3. I'd like to do the following things:
* update to 4.4.2 (is it better to stay with 4.3 if I care about the other things I'm going to enumerate here?)
* root it, I don't care about knox
* remove most of Samsung bloatware (I like the clock and the pen stuff and would like to keep them) - does titanium backup still work for this, what do I have to care about to not brick the phone?
* install adblock and afwall
* all that without the need for a samsung online account
Are there any step-by-step instructions for these things, especially for rooting?
Phone data:
AP: N9005XXUDMJ6
CP: N9005XXUDMJ4
CSC: N9005VFGDMJ1
SELinux: SEPF_SM-N9005_4.3_0011
Click to expand...
Click to collapse
1) Sure. Update to Kitkat. I have only positive things to say about the official kitkat ROM.
2) You can root it (tripping knox would become mandatory).
3) Titanium works perfectly.
4) You just need root for that.
5) You don't need a Samsung account for anything except using Samsung apps. I haven't used it yet.
Here is a nice guide for you. http://forum.xda-developers.com/showthread.php?t=2614787

FeralFire said:
1) Sure. Update to Kitkat. I have only positive things to say about the official kitkat ROM.
2) You can root it (tripping knox would become mandatory).
3) Titanium works perfectly.
4) You just need root for that.
5) You don't need a Samsung account for anything except using Samsung apps. I haven't used it yet.
Here is a nice guide for you. http://forum.xda-developers.com/showthread.php?t=2614787
Click to expand...
Click to collapse
Thanks for your reply, I finally got to it and are now a happy root user. However,...
1) I have not updated to kitkat yet, but decided to stay with 4.3 for the moment and only root it, to become a bit more acquainted with the device. I wonder whether that kitkat version you posted will work with my language?
2) Using cf-auto-root worked fine.
3) Restoring my apps and data using titanium backup also worked without any problems, except the phone imported the contact on the sim in a nasty way, making a mess of my address book. It will take me some time to tidy that up.
Is it safe to remove Knox using Titanium Backup uninstall? I'm using the free version only, so freezing is not available. Has anyone done it and can confirm it doesn't cause any problems? On another thread I've read that uninstalling knox could leave you with a broken device, I hope that's not true?

dark$hadow said:
Thanks for your reply, I finally got to it and are now a happy root user. However,...
1) I have not updated to kitkat yet, but decided to stay with 4.3 for the moment and only root it, to become a bit more acquainted with the device. I wonder whether that kitkat version you posted will work with my language?
2) Using cf-auto-root worked fine.
3) Restoring my apps and data using titanium backup also worked without any problems, except the phone imported the contact on the sim in a nasty way, making a mess of my address book. It will take me some time to tidy that up.
Is it safe to remove Knox using Titanium Backup uninstall? I'm using the free version only, so freezing is not available. Has anyone done it and can confirm it doesn't cause any problems? On another thread I've read that uninstalling knox could leave you with a broken device, I hope that's not true?
Click to expand...
Click to collapse
Most languages are in the stock roms....
If you do update to KK make sure re-activation lock is OFF... This applies to custom roms too as it can brick your phone otherwise...

dark$hadow said:
Thanks for your reply, I finally got to it and are now a happy root user. However,...
1) I have not updated to kitkat yet, but decided to stay with 4.3 for the moment and only root it, to become a bit more acquainted with the device. I wonder whether that kitkat version you posted will work with my language?
2) Using cf-auto-root worked fine.
3) Restoring my apps and data using titanium backup also worked without any problems, except the phone imported the contact on the sim in a nasty way, making a mess of my address book. It will take me some time to tidy that up.
Is it safe to remove Knox using Titanium Backup uninstall? I'm using the free version only, so freezing is not available. Has anyone done it and can confirm it doesn't cause any problems? On another thread I've read that uninstalling knox could leave you with a broken device, I hope that's not true?
Click to expand...
Click to collapse
To remove Knox, goto Settings, General, Applications, All.
Disable all Knox apps.
That's what I have done. No issues with it. And it is completely reversible if you run into any problems.

Most things work fine, and I like the handwriting recognition. Apart from that, I did not find much use for the pen, except it is a nice gimmick.
I have one problem which seems related to adaway and supersu: Applying the new hosts file sometimes takes very long. And I suspect it to cause battery drain thereafter. Has anyone experienced similar difficulties? My solution at the moment is to apply the hosts file and then restart the phone immediately.

You can remove knox with titanium 'couse if rooted then knox will not work anymore, so there is no point in keeping it!
Sent from Note 3 Superphone!

dark$hadow said:
I have one problem which seems related to adaway and supersu: Applying the new hosts file sometimes takes very long. And I suspect it to cause battery drain thereafter. Has anyone experienced similar difficulties? My solution at the moment is to apply the hosts file and then restart the phone immediately.
Click to expand...
Click to collapse
I'm not sure it had anything to do with adaway and supersu. I've greenified adaway, and the issue still persisted. Now I've removed many Samsung pre-installed system apps (samsung account, camera test, bluetooth test, factory test, scrapbook etc.) and do no longer experience the battery drain. Let's see in a week or so.

Just rooting disables some apps?

I am all ready to root/flash custom roms ignoring knox counter for my note 3. I have read that just rooting the this device disables or breaks functions like screen mirroring etc. I have used previously Note 2 and S3 and rooted flashed them n number of times but never heard this.
If yes what are the other functions that may get disabled or broken? I like and use allshare (Samsung link) all the time. Does it also gets disabled?
Regards,

Screen mirroring gets broken from custom kernel, not Root AFAIK, as for other things, well KNOX doesn't work that's about it.

semantsen said:
I am all ready to root/flash custom roms ignoring knox counter for my note 3. I have read that just rooting the this device disables or breaks functions like screen mirroring etc. I have used previously Note 2 and S3 and rooted flashed them n number of times but never heard this.
If yes what are the other functions that may get disabled or broken? I like and use allshare (Samsung link) all the time. Does it also gets disabled?
Regards,
Click to expand...
Click to collapse
I think screen mirroring gets disabled pretty much when knox flag gets disabled (non-stock kernel/recovery mostly).
Just rooting should not disable that (unless maybe if you trigger knox), but might disable programs that check for root (like some banking apps) - but now there is an xposed module even for that

[Q] How to enable Fingerprint Scanner with full device encryption??

Hi,
I bought the Samsung Galaxy S5 and the fingerprint reader works reasonably well (as in it works, nothing in comparison to apple though, so don't buy it for the fingerprint reader ) for unlocking the screen...
However its a work requirement that my phone has full device encryption, as phones are regularly stolen where I travel.... it seems when I enable encryption I lose the ability to use the fingerprint reader to unlock the phone .... I bought this hoping that I could avoid having to type in my complex password just to unlock the screen, as I got so tired of doing that with my S2
Is there any mods to enable finger print reader screen unlock + full device encryption at boot time for the Galaxy S5 yet? ... I saw some references to pattern unlock / pin with device encryption... but I would think the fingerprint reader is different...
Thanks!

S5 Full disk encryption with fingerprint unlock
I also have this question. I believe on the Nexus 5 it at leasts lets you use face unlock with full device encryption. And I read on one article that you should be able to do this but i do not think the author actually tried this. I will say from my own personal experience that you can infact decrypt the device after encrypting it without doing a complete wipe of the device and you can restore the use of fingerprints to unlock your phone. It seems like for security minded people this would be a great feature but if it is unable to be used with full device encryption it seems a little pointless to me. Being forced to use a PIN or password to use encryption is a big pain point for android users who want some type of security.

Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined

androidpleb said:
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
Click to expand...
Click to collapse
I am having the same pain, as I use my S5 for BYOD.
It makes no sense when you can use fingerprint to make payments with paypal but not unlocking the phone when it is encrypted.
Hope Samsung can enable this feature in next update.

I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!

sorphin said:
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
Click to expand...
Click to collapse
I can't believe that the fingerprint sensor can't be used if encryption is enabled whatsoever. I could understand the iPhone model, requiring a pin before a fingerprint can be used, but by disabling fingerprint lockscreen, boot unlock, and SD unlock, the fingerprint sensor is now wholly useless for convenience.
It's too trivial to extract data from an unencrypted Android. By not supporting encryption with a measure of covenieve, I don't see the point in including a fingerprint sensor whatsoever given the current software limitations.
Please, someone, figure out what sqlite/settings need to be changed so we can make decent use of our phones fingerprint sensor.

After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption

Boot Loop
fabiokino said:
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Click to expand...
Click to collapse
I get samsung boot loop using the above instructions

Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
Hi guys! Did someone try this solution? I unfortunately have the same issue and unlock my device each time make me crazy!
Thanks in advance.

Same problem
I purchased a Galaxy S5 and I have the same problem, unfortunately I cannot root my phone due to security policies in my company. :crying:
I hope Samsung will solve the issue. :fingers-crossed:
Have anyone contacted to Samsung Support Center?

Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
What is the consequence of boot loop if you are using stock boot loader? Odin mode required to recover? Something less drastic? What device model are you using?
I found a possible solution that involves deactivating SuperSU and running encryption from there. Still investigating. I am thinking that the solution from @fabiokino will work in this case too.

I'm curious about this aswell.

Doesn't anyone know a working solution?...
It is really frustrating the very least. I can't believe there isn't a way (or if there is, a guide) to do this (with or without root access).
I have also heard it is doable on the Note 4. See this post for example http://forum.xda-developers.com/showpost.php?p=57103664&postcount=7.

I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.

How?
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!

healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Nice to see this, hope it will work on my Galaxy tab S too
Did you see this?
https://www.jethrocarr.com/2013/12/29/encrypting-disk-on-android-4/

GermanDoerksen said:
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
Click to expand...
Click to collapse
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD

Joker87 said:
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Click to expand...
Click to collapse
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..

GermanDoerksen said:
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
Click to expand...
Click to collapse
You could root then unroot it after you have encrypted it

Joker87 said:
You could root then unroot it after you have encrypted it
Click to expand...
Click to collapse
you're right... plus it's not really the "rooting" process that makes it slow, it's installing another ROM. Having a rooted phone doesn't necessarily have any performance impact... just opens up a few things for me. Interesting. Thanks! Unfortunately I've already encrypted so now I have to find that thread about how to decrypt lol.
Thanks!

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.

Help bypassing lockscreen; unfamiliar with device

Hello,
I am trying to work around/bypass the password lockscreen for a friend that accidentally set it (I think her kid did) and doesn't know what the actual password is. I've already tried ADM and Samsung's "Find My Mobile" service but neither were helpful.
So I'm pretty sure my only two options now are to backup the existing data to my PC (though I'm not sure how given that I don't have access to important functions like ADB, custom recovery, etc.) and then factory reset the phone, OR just deal with the KNOX/warranty flag being tripped and delete the necessary files from /data/system using a custom recovery. If there's another alternative I'm missing, I would love to hear it.
Excuse me for already jumping ahead, but assuming I go the latter route, what would be the easiest way to flash a custom recovery? I've already looked at various other posts on this phone's board regarding rooting and everything looked quite involved.
The phone says it's a G935PVPS4BQE1, if that helps.
Thanks in advance.
P. S. I currently come from a OnePlus One, though I previously had a Galaxy S3 and remember quite vividly how much of a huge pain it was to properly root the device and deal with KNOX. I imagine the rooting process is even more of a pain with more recent Samsung phones.