Database Users

[Q] Securing Nexus 4

Is there any way to secure android like ios7. In case if i loose my phone then no one can use it. Is it true a hard reset will remove my pattern or password? My phone is non rooted. Can someone install custom recovery too?

saudiqbal said:
Is there any way to secure android like ios7. In case if i loose my phone then no one can use it. Is it true a hard reset will remove my pattern or password? My phone is non rooted. Can someone install custom recovery too?
Click to expand...
Click to collapse
There is not fool poof way to prevent this. Even on IOS7 the security can be gotten around. Best advice is to make sure you are backing up your files.
Google does have a remote wipe option built into the Android OS. That is your best bet.

There is no full proof way to make render unusable, but you can call up your carrier and ask them to blacklist the IMEI so they can't use sim cards with it anymore.
You could however, protect your data. Do this by: encrypt your device, stock recovery, disable USB debugging, lock the bootloader. At least with this, if the device is stolen, if they don't know how to flash factory image, they'll need to enter the encrypted password to boot into the phone and can't copy over your datas.
You should also look up the app Cerberus, which with root can survive through factory reset (as long as they don't overwrite or format the "system" partition).

[Q] Sould I use reactivation lock after rooting?

Hi everyone.
I wanted to root my device and it didn't work, allways got Auth fail recovery on odin and device, until I unchecked the reactivation lock, then it rooted flawlessly.
(I know my google account and password)
I was curious is it safe to stay with reactivation lock checked in case this happens:
Lets say the soft bricks into a boot loop who knows why but recovery still works.. so if I want to factory reset from custom recovery(philz recovery, with Nandroid and efs backed up), I think it is the best to unroot before factory reset(hope I'm wrong), witch will be imposible if the root didn't worked because of the reactivation lock, the unroot won't work too?
I gues before trying any flashing etc is good to uncheck reactivation lock, but I can allways make a mistake and forget it on.
So let me make that short, is it safe to activate ractivation lock when rooted in case something bad happens with the boot start?
I want to activate it for safety but this safety could block me too?
Do you guys keep it on after rooting?
I hope the readers will understand my question and don't get any headakes, sometimes I gould it hard to express myself in english, sorry about that.

alexpu1u said:
So let me make that short, is it safe to activate ractivation lock when rooted in case something bad happens with the boot start?
Click to expand...
Click to collapse
Well reactivation lock is an anti-theft feature. Theft deterrents are good although they only have significant value when they are well implemented. Which is arguable in this case. It's hardly undefeatable. 2 strikes. And can be as annoying as hell in not liking your custom kernel. Strike thr ...
Bottom line, if you are good at making backups and believe in theft deterrents, then enable it. It makes it slightly more likely that a lost phone would make it back to you. Or at least ruin the thief's day. There should always be a way to restore your device if you have a backup and your credentials.
However if you are forgetful, bad with backups or simply have no patience for having to search XDA threads or enter something on a command line to disable reactivation lock and recover from a bootloop, etc.. then obviously don't use it. It could cause you some exasperation if you are in an unbootable state and it is interferring with an Odin flash.
Pick one. And either way try not to lose your phone.
.

That's what I wanted to hear, so it's safe to keep it on if I'm backedup and pacient in case of a problem.
Thank you for your time. I activated it .

alexpu1u said:
That's what I wanted to hear, so it's safe to keep it on if I'm backedup and pacient in case of a problem.
Thank you for your time. I activated it .
Click to expand...
Click to collapse
Well, I'm not concerned with being locked out of my phone permanently. Nor convinced that RA would really stop a stolen phone from being reactivated. But it's plausible that it would delay some thieves from using Odin to obliterate your tracking software.
So a longer window in which it might be possible to pin down your phone's location. Or perhaps spur someone to return your phone in the case of a lost, rather than stolen phone.
Whether to use RA depends mostly on your willingness to put up with some temporary frustration should your phone somehow end up unbootable and you have to jump through a few hoops to disable the reactivation lock.
.

alexpu1u said:
Hi everyone.
I wanted to root my device and it didn't work, allways got Auth fail recovery on odin and device, until I unchecked the reactivation lock, then it rooted flawlessly...
Click to expand...
Click to collapse
But you can't enable this option after root, it does not work!

knox 0x1 (2)
jgfernog said:
But you can't enable this option after root, it does not work!
Click to expand...
Click to collapse
interesting finding from me:
even if you are not root, with samsung knox 0x1 (2) the option is automatically enabled but you won't see it ticked. You can factory reset your phone when you have knox 0x1 (2) and see it will ask for reactivation account in order to by pass the phone. There is no solution. Samsung knox is funny.

MaXi32 said:
interesting finding from me:
even if you are not root, with samsung knox 0x1 (2) the option is automatically enabled but you won't see it ticked. You can factory reset your phone when you have knox 0x1 (2) and see it will ask for reactivation account in order to by pass the phone. There is no solution. Samsung knox is funny.
Click to expand...
Click to collapse
Yeah! There are some problems with it. I saw people saying that their devices had KNOX enabled even with the option unchecked in settings.

I wouldn't bother with reactivation lock for any scenario
1. Easy to bypass
2. Only causes problems for yourself if you forget to disable it before flashing
3. Anyone who knows how to flash a new ROM, which is what it's designed to prevent, can bypass it flashing a KitKat ROM anyway
4. You've lost your phone anyway, they're not gonna give it back because they can't use it

How to trace your note 4 after rooting?

Hi all, im thinking about rooting my phone and i dont mind tripping the knox counter.
I wondered if the tracing still works using the find my mobile site from samsung?
Knox is really succesful because if you enable it they cant hard reset your phone or root it do remove the tracing, right?
So is there any possibility to have the same functionality after rooting?

Wally93 said:
Hi all, im thinking about rooting my phone and i dont mind tripping the knox counter.
I wondered if the tracing still works using the find my mobile site from samsung?
Knox is really succesful because if you enable it they cant hard reset your phone or root it do remove the tracing, right?
So is there any possibility to have the same functionality after rooting?
Click to expand...
Click to collapse
You can still trace it after root via Samsung. Idk about the reactivation lock tough becouse u need to disable that before rooting

Racinghart91 said:
You can still trace it after root via Samsung. Idk about the reactivation lock tough becouse u need to disable that before rooting
Click to expand...
Click to collapse
I'd like to know the same thing, when rooted and on stock recovery: reactivation lock enabled;
Will it still ask for Samsung credentials if reset from system?
Will it still ask for Samsung credentials if reset by bootloader?
Will it still ask for Samsung credentials if flashed via PC?
Kind regards, Stefan.

I tried the tracker at the Samsung site yesterday. It didn't find my rooted phone, didn't make the phone ring etc,
I was just relying on cellular data for the connection (no WiFi or GPS).
Maybe it was a one off.

Locked phone using Android Device Manager. Forgot password without a way to unlock.

Device is a SM-N916S from Samsung (Galaxy Note 4 S-LTE Exynos 5433 ver.) for anyone that's wondering. It's current state : Completely stock with no root. USB debugging disabled. No Samsung Account linked to device. Can't change password through ADM. No more guesses left for the password anymore, any more will reset the phone.
So yeah. For the past few days I've been trying to bypass Android Device Manager's remote "Lock" feature that's meant to keep your data safe from thieves. As for why? Long story short : I tried to pull a prank on my brother by remotely locking his device through ADM. I have since forgotten the password (it was a random combination of letters and numbers that I thought I could remember, but obviously not.) and trying to set a new password through Android Device Manager just gives me the infamous "Since Google has verified that a screen lock is already set, the password you entered won't be needed." error message.
Now, if this was a phone that belonged to me, I would just install a custom recovery and remove the password with a password disable zip, but unfortunately, that is not an option here. I probably forgot to mention that I CANNOT void the warranty (as in trip the KNOX counter) under ANY circumstances and would very much like to avoid a factory reset. Am I out of luck here? Or is anyone here aware of a method that can be used to bypass the ADM lock / or a way to backup data with usb debugging disabled. Thanks.

use smart switch to go back to stock firmware

SrikarPrayaga said:
use smart switch to go back to stock firmware
Click to expand...
Click to collapse
Hi, could you explain what you mean by this? Does smart switch work even when the phone is locked? And what would going back to stock firmware do? Thanks.

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?