I have an anti-theft app whose importance that I put above all others. The problem is I can't root because I don't want to trip Knox. But without root, I can't hide the app in root to survive a reset/factory reset. And so all the anti-theft precautions I put on my phone means nothing if just anyone can just go into recovery and delete everything...
Can you lock recovery, or root without tripping knox?
Chocolina said:
I have an anti-theft app whose importance that I put above all others. The problem is I can't root because I don't want to trip Knox. But without root, I can't hide the app in root to survive a reset/factory reset. And so all the anti-theft precautions I put on my phone means nothing if just anyone can just go into recovery and delete everything...
Can you lock recovery, or root without tripping knox?
Click to expand...
Click to collapse
Yes. Encrypt your phone. Other than that, no.
ingenious247 said:
Yes. Encrypt your phone. Other than that, no.
Click to expand...
Click to collapse
TY!
Can't even an encrypted phone be wiped? What if you forget the password?
andrewNY said:
Can't even an encrypted phone be wiped? What if you forget the password?
Click to expand...
Click to collapse
Yes, the ENTIRE phone can be wiped, but he's talking about someone wiping a security app and then getting at his information inside the phone.
Wiping the phone entirely was not his concern.
ingenious247 said:
Yes, the ENTIRE phone can be wiped, but he's talking about someone wiping a security app and then getting at his information inside the phone.
Wiping the phone entirely was not his concern.
Click to expand...
Click to collapse
Wiping the entire phone isn't my concern, its the prevention to wipe it.
Since I cannot root the phone without tripping knox, then above-all else, I want to lock any potential theif to have no access to recovery, no access to Developer tools, but more importantly debugging, and no access to Factory reset under backup and restore. If I could root without tripping knox, all or most my problems would be solved.
When I had an HTC One M7 and had it stolen, I got lucky because I had no password on access to my device's functions, but the Anti-theft program of my choice, Cerberus was installed into root and was designed to survive all factory wipes and stay hidden as a system process. I managed to recover my phone 2-days after. The reason I prefer Cerberus over other other anti-theft apps because Cerberus has some extensive features and parameters on it's behavior. Example: you could send a command to start GPS tracking by SMS, and if by chance they remove or use their own SIM, you could set parameters to start GPS tracking or do a specific function when it detected no SIM or an unauthorized SIM.
Idealy what I want is a lock on Recovery, Factory Reset, and USB Debugging. The idea is to lock all the reset and modding options while still inviting the thief to continue using and charging the device in the regular OS so they feel comfortable keeping the device charged and always connected. If I just set a system-wide password, then all functions are locked with a password. If the thief knows they can't use or play with the device, they won't try to connect the phone, instead they'll just turn the phone off, won't charge it, or just boot into recovery and delete everything.
Cerberus can lock USB Debugging, the Power Button, and the Notification tray, but it won't/can't lock Factory Reset, but can survive any reset if rooted.
A system-wide password can protect from a Factory Reset in the OS menu, but doesn't protect in recovery, and locks the user out preventing them to trigger any "Start GPS tracking" triggers I might place.
Encryption, if it does lock Recovery, can lock recovery, and work with Cerberus to lock USB Debugging, but requires a system-password and would prevent any parameters set from being triggered.
Right now the best alternative I have is a system password with Cerberus which blocks the phone from being shut off, but would only be good for a day unless the theif decides to keep a stolen, locked phone charged. And I sometimes keep my phone in airplane mode to save energy, but if it gets stolen in airplane mode, it can't ever be taken out, and so GPS tracking couldn't be activated by Data or SMS. So really not being able to root without tripping knox is preventing me from reaching an exact configuration I'd be happy with.
There's a beta app called PingPong that uses a vulnerability to achieve root without tripping KNOX which I used to great success. You may be able to root, install the app (and then un-root if you wanted to). That's what I'd recommend.
http://www.xda-developers.com/pingpong-tool-roots-your-galaxy-s6-without-tripping-knox/
Related
My last phone (Nexus 4) was stolen. My new device, the Nexus 6, as you all know comes with enhanced security measures, requiring authentication even after a factory reset. Now, I had grown accustomed to playing around with wiping, rooting, custom roms, kernels, radios, etc with my Nexus 4. Now that I have had my Nexus 6 for a bunch of months, I am starting to think about rooting my device (so I can install an SSH server and have my phone automatically open a tunnel back to my server). My only hesitation is turning the OEM unlocking switch to on. See, I am a big fan of the new security measures that require authentication after a device reset, and would much prefer to keep that feature enabled. I've searched around on Google and XDA, and I haven't been able to find any definitive answers on how unlocking the bootloader in order to root the device will affect these security mechanisms.
My understanding is this: in order to root the Nexus 6, you need to enable OEM unlocking, which allows flashing pretty much any image onto the phone. If any image can be flashed to the phone, this security mechanism can be circumvented.
Two questions:
1. (pretty sure the answer to this is no) Can I root my phone and prevent flashing of images that would circumvent the security feature
2. Will rooting my phone make it easier for an unknown party to gain access to the device via another route
Unlocking the bootloader really only allows you to flash unsigned images, and root provides you with the option to grant administrative access to applications.
Neither one of those has anything to do with encrypted data, or in any way makes encrypted data readable without the key.
The bootloader unlock will make it easier for a thief to wipe all the data on the device without reading it, so he can use the device or sell it as functioning... Even then, you may be able to factory reset an encrypted device without the key anyways... At which point I would think they could make a new key for the freshly wiped partition?
Anything that is going to run unauthorised code at root level is likely going to use other exploits to achieve root on their own, like users do to gain root on devices that are locked down. You having root access doesn't give the right for anything to run as root unless you approve it (or if someone managed to find some exploit in the version of supersu your running, but this is not likely... and if we are assuming any code may have holes in it you're not safe no matter what you do). It does give you the possibility of being tricked into running malicious code that is disguised as some utility... But that is a risk your going to take running any software that isn't from a stable corperation you can take legal action against. Trust who wrote the code or don't use it.
If in question number 1 "the security feature" is encryption, then yes having and unlocked bootloader means if someone takes your phone they can flash a kernel that does not force encryption, they would then have to format the userdata partition to encrypt the phone. Without luck, guessing the password, or discovering some amazing undocumented flaw in the encryption algorithm they will not being able to read your data with out having the key, or guessing it.
@scryan
If you have unlocked the bootloader and have installed a custom recovery (TWRP), are you able to see the list of files in the file manager of TWRP, if the device is encrypted?
Nikos2k said:
@scryan
If you have unlocked the bootloader and have installed a custom recovery (TWRP), are you able to see the list of files in the file manager of TWRP, if the device is encrypted?
Click to expand...
Click to collapse
Yes. Otherwise couldn't pick a file to flash. It actually only encrypts user data. Apps, zips ect are not encrypted or we couldn't pull and modify them.
prdog1 said:
Yes. Otherwise couldn't pick a file to flash. It actually only encrypts user data. Apps, zips ect are not encrypted or we couldn't pull and modify them.
Click to expand...
Click to collapse
the user data that are encrypted include files on the sdcard folder? (e.g. pdfs, images in DCIM folder etc)
i am asking because in my device in Settings -> Security -> Encryption it shows that it is encrypted, in TWRP however i can see all the files
Can i make the custom recovery to ask for the pin? do I have to enable PIN as a screen lock?
What happens if i use an unlock pattern or just swipe for unlock?
Nikos2k said:
the user data that are encrypted include files on the sdcard folder? (e.g. pdfs, images in DCIM folder etc)
i am asking because in my device in Settings -> Security -> Encryption it shows that it is encrypted, in TWRP however i can see all the files
Can i make the custom recovery to ask for the pin? do I have to enable PIN as a screen lock?
What happens if i use an unlock pattern or just swipe for unlock?
Click to expand...
Click to collapse
TWRP will use same pin as Device lock. Only thing I have seen if you use pinlock have to convert 5x5 to 4x4. There's a way to convert it located in this forum somewhere. Swipe to unlock has no pin so TWRP is open. Unlock pattern works also. Either pin or swipe has to be converted don't remember which. I run wide open encrypted so have never played with it.
prdog1 said:
TWRP will use same pin as Device lock. Only thing I have seen if you use pinlock have to convert 5x5 to 4x4. There's a way to convert it located in this forum somewhere.
Click to expand...
Click to collapse
By pinlock you mean the pattern screen lock?
I think it is 3 x 3, not 4x4 or 5x5
And since I use this pattern screen lock, which cannot be input in TWRP, this means that I have to disable it b4 I need to enter recovery?
This makes me a bit uncomfortable since I may need to enter recovery because of a problem with the system
Nikos2k said:
By pinlock you mean the pattern screen lock?
I think it is 3 x 3, not 4x4 or 5x5
And since I use this pattern screen lock, which cannot be input in TWRP, this means that I have to disable it b4 I need to enter recovery?
This makes me a bit uncomfortable since I may need to enter recovery because of a problem with the system
Click to expand...
Click to collapse
Start with this thread. It explains TWRP.
http://forum.xda-developers.com/nexus-6/help/twrp-2-8-5-0-password-help-t3046630
prdog1 said:
Start with this thread. It explains TWRP.
http://forum.xda-developers.com/nexus-6/help/twrp-2-8-5-0-password-help-t3046630
Click to expand...
Click to collapse
thank you it worked!
scryan said:
Unlocking the bootloader really only allows you to flash unsigned images, and root provides you with the option to grant administrative access to applications.
Neither one of those has anything to do with encrypted data, or in any way makes encrypted data readable without the key.
The bootloader unlock will make it easier for a thief to wipe all the data on the device without reading it, so he can use the device or sell it as functioning... Even then, you may be able to factory reset an encrypted device without the key anyways... At which point I would think they could make a new key for the freshly wiped partition?
Anything that is going to run unauthorised code at root level is likely going to use other exploits to achieve root on their own, like users do to gain root on devices that are locked down. You having root access doesn't give the right for anything to run as root unless you approve it (or if someone managed to find some exploit in the version of supersu your running, but this is not likely... and if we are assuming any code may have holes in it you're not safe no matter what you do). It does give you the possibility of being tricked into running malicious code that is disguised as some utility... But that is a risk your going to take running any software that isn't from a stable corperation you can take legal action against. Trust who wrote the code or don't use it.
If in question number 1 "the security feature" is encryption, then yes having and unlocked bootloader means if someone takes your phone they can flash a kernel that does not force encryption, they would then have to format the userdata partition to encrypt the phone. Without luck, guessing the password, or discovering some amazing undocumented flaw in the encryption algorithm they will not being able to read your data with out having the key, or guessing it.
Click to expand...
Click to collapse
Ok, so for encryption, "Allow OEM Unlocking" allows flashing of unsigned images (such as the one used for root), which means if someone gets a hold of my phone, they can put whatever they want on it, including flashing a custom rom.
So my next question is, what about being required to sign into the last Google account used on the phone even after a factory reset (device protection / factory reset protection / not sure what it's called exactly)? Is that area of the bootloader / rom / memory / wherever it lives flashable? If you have an unlocked bootloader, is it possible to flash some image to the device that disables this? Hah, that sounds bad. Really, I want to root my Nexus 6, but I haven't decided if it would be worth giving up the anti-theft required login after reset.
I guess really, I'm curious about how it works, is it part of the Android image delivered by Google? Is it part of the bootloader? Is it possible to release a rom without this feature? I'm not a thief, I swear I'm just curious.
quickdry21 said:
Ok, so for encryption, "Allow OEM Unlocking"
encryption and oem unlock ar 2 entirely different things
allows flashing of unsigned images
allows you to unlock the boottloader, which allows you to flash unsigned img's. the setting itself does nothing but enable the ability. to unlock
(such as the one used for root), which means if someone gets a hold of my phone, they can put whatever they want on it, including flashing a custom rom.
yes
So my next question is, what about being required to sign into the last Google account used on the phone even after a factory reset (device protection / factory reset protection / not sure what it's called exactly)? Is that area of the bootloader / rom / memory / wherever it lives flashable? If you have an unlocked bootloader, is it possible to flash some image to the device that disables this? Hah, that sounds bad. Really, I want to root my Nexus 6, but I haven't decided if it would be worth giving up the anti-theft required login after reset.
i think if someone were to completely wipe the phone, use a different gmail and sim, the google protection would be gone, but i could be wrong. im not positive on that one.
I guess really, I'm curious about how it works, is it part of the Android image delivered by Google? Is it part of the bootloader? Is it possible to release a rom without this feature? I'm not a thief, I swear I'm just curious.
some extremely savvy person "may" be able to make a rom without the google protection, but i have never seen it tried.it may be a core feature that cant be removed.
i really wouldnt worry about that. the likelihood that someone would steal or find your device and have the skills to do all you asked above, is very remote.
Click to expand...
Click to collapse
in red above.
bweN diorD said:
in red above.
Click to expand...
Click to collapse
protection will be gone if you flash android 5.0.1. if you wipe and flash android 5.1.1, the protection will still be there and will ask for your password first.
bweN diorD said:
in red above.
Click to expand...
Click to collapse
Thanks, that does seem to make sense.
I know this comes across as overly paranoid, but I ask also because I'm a curious developer. I'm interested in understanding how android's insides work in general as well as how the new device protection fits in with rooting, custom roms, unlocking the bootloader, etc. (just how well does it prevent unauthorized use of devices)
Interesting, that says to me there is a relatively easy way to get around the reset protection if a phone has an unlocked bootloader. Albeit, relatively easy is relative.
quickdry21 said:
Interesting, that says to me there is a relatively easy way to get around the reset protection if a phone has an unlocked bootloader. Albeit, relatively easy is relative.
Click to expand...
Click to collapse
easy, yes, for one of us. but for a typical user, very hard. anyways, i dont like letting out the secret of how to bypass it, so keep it quiet please
simms22 said:
easy, yes, for one of us. but for a typical user, very hard. anyways, i dont like letting out the secret of how to bypass it, so keep it quiet please
Click to expand...
Click to collapse
Yes, agreed. I'm going to edit out that quote.
quickdry21 said:
Ok, so for encryption, "Allow OEM Unlocking" allows flashing of unsigned images (such as the one used for root), which means if someone gets a hold of my phone, they can put whatever they want on it, including flashing a custom rom.
So my next question is, what about being required to sign into the last Google account used on the phone even after a factory reset (device protection / factory reset protection / not sure what it's called exactly)? Is that area of the bootloader / rom / memory / wherever it lives flashable? If you have an unlocked bootloader, is it possible to flash some image to the device that disables this? Hah, that sounds bad. Really, I want to root my Nexus 6, but I haven't decided if it would be worth giving up the anti-theft required login after reset.
I guess really, I'm curious about how it works, is it part of the Android image delivered by Google? Is it part of the bootloader? Is it possible to release a rom without this feature? I'm not a thief, I swear I'm just curious.
Click to expand...
Click to collapse
Maybe someone could figure out something?
But if your device is wiped, and basically all the partitions are re-written.... Where do you want to store the last google account information to check against?
No one is going to plan on stealing your phone, ask you if the bootloader is unlocked, then decide not to if they say no. None of the security really prevents your phone from being stolen. Nothing just looking at your phone lets a would be thief know that its encrypted and not unlocked...
The encryption and locked bootloader will not prevent your phone from being stolen. The encryption will protect your data, and the locked booloader will make it harder to reset the device (though does factory recovery have a factory reset option? I would think this would allow the device to be wiped and encryption key to be reset anyways?)
I guess really, I'm curious about how it works, is it part of the Android image delivered by Google? Is it part of the bootloader? Is it possible to release a rom without this feature? I'm not a thief, I swear I'm just curious.
Click to expand...
Click to collapse
What? You keep talking about this single security device? What are you talking about?
Do you mean encryption?
encryption is just how the data is stored on the device.
Say you have the word "Duck"
And we want to store that word in a safe way. As a VERY VERY basic method, we will encrypt this by shifting each letter of the alphabet a certain number of letters. This number will be something YOU give, so that others do not know how many letters we have shifted over.
So lets say you give us "5" as your key.
so the alphabet
abcdefghijklmnopqrstuvwxyz we will shift 5 letters over, starting on the fifth letter and wrapping around...
fghijklmnopqrstuvwxyzabcde so each letter matches up with a new letter.
D is the 4th letter of the alphabet, so we will use the 4th letter of of shifted alphabet, i
u is the 21st letter of the alphabet so we will use the 21st letter of our shifted alphabet, z
ect, ect... so Duck becomes Izho, and with out knowing how many letters to shift over, know one will know what that means (ok, obviously due to the simplicity of our encryption algorithm, anyone who is smart and cares can likely try different numbers until the output is a coherent word. the actual method of encryption is significantly more complex, and the key is more then one characters
See here for more intellegent details: https://wiki.archlinux.org/index.php/Disk_encryption#How_the_encryption_works
quickdry21 said:
Yes, agreed. I'm going to edit out that quote.
Click to expand...
Click to collapse
na, it ok, you can leave it here. that way if someone really needs to, theyll find the answer here. just dont go around spreading it around i meant
scryan said:
Maybe someone could figure out something?
But if your device is wiped, and basically all the partitions are re-written.... Where do you want to store the last google account information to check against?
No one is going to plan on stealing your phone, ask you if the bootloader is unlocked, then decide not to if they say no. None of the security really prevents your phone from being stolen. Nothing just looking at your phone lets a would be thief know that its encrypted and not unlocked...
The encryption and locked bootloader will not prevent your phone from being stolen. The encryption will protect your data, and the locked booloader will make it harder to reset the device (though does factory recovery have a factory reset option? I would think this would allow the device to be wiped and encryption key to be reset anyways?)
Click to expand...
Click to collapse
I'm not expecting this "Device Protection" feature to prevent my phone from being stolen, I'm more interested in the **** you aspect to someone who tries, and maybe them returning it to me for some money.
scryan said:
What? You keep talking about this single security device? What are you talking about?
Do you mean encryption?
Click to expand...
Click to collapse
I'm not sure if you are aware, but with the release of 5.1, there is a new security feature (think it's called Device Protection, but that seems to encompass some other things) that requires you to login to the last Google account attached to the phone after a factory reset (whether done from the settings UI, or from recovery mode). If you are unable to login to a Google account that was attached to the phone, the phone becomes worthless (there have been some posts on xda about people "acquiring" a Nexus 6 and being unable to use it), some details here: https://support.google.com/nexus/answer/6172890
A quote from that link sums it up:
Important: You can enter information for any Google account that has been added to the device. If you can't provide this information during the setup process, you won't be able to use the device at all after the factory reset.
Click to expand...
Click to collapse
Now, this security feature is only available on new phones that are released with 5.1 (with the exception of the newest round of Nexus devices, which received it with the update to 5.1). This leads me to believe that some aspect is baked into the device. Separate encrypted partition maybe? Part of the bootloader software? I don't know, that's what I'm curious about.
scryan said:
encryption is just how the data is stored on the device.
Say you have the word "Duck"
And we want to store that word in a safe way. As a VERY VERY basic method, we will encrypt this by shifting each letter of the alphabet a certain number of letters. This number will be something YOU give, so that others do not know how many letters we have shifted over.
So lets say you give us "5" as your key.
so the alphabet
abcdefghijklmnopqrstuvwxyz we will shift 5 letters over, starting on the fifth letter and wrapping around...
fghijklmnopqrstuvwxyzabcde so each letter matches up with a new letter.
D is the 4th letter of the alphabet, so we will use the 4th letter of of shifted alphabet, i
u is the 21st letter of the alphabet so we will use the 21st letter of our shifted alphabet, z
ect, ect... so Duck becomes Izho, and with out knowing how many letters to shift over, know one will know what that means (ok, obviously due to the simplicity of our encryption algorithm, anyone who is smart and cares can likely try different numbers until the output is a coherent word. the actual method of encryption is significantly more complex, and the key is more then one characters
See here for more intellegent details: https://wiki.archlinux.org/index.php/Disk_encryption#How_the_encryption_works
Click to expand...
Click to collapse
Yes, I was not very clear in my original post about what security feature I was inquiring about. I'm aware of what encryption is. Part of the reason I am interested in rooting my phone is to reverse tunnel a SSH server on the phone, or possibly netcat, via SSH to my server, so I will be able to open up a shell on my phone from anywhere I desire.
Ahh yes, apologies, was unaware they implemented that feature. A bit dense this morning.
I would imagine unlocked bootloader/custom recovery would DEFINITELY negate this feature.
No one gonna give your phone back, particularly after you use this as a "**** you" While its just IMO, its better to enjoy your phone now. Screwing yourself out of features only to attempt to limit the phone once you don't have anything to do with it anymore does not seem to be particularly productive.
I was wondering if how to go about encrypting our phones on CM 12.1. For me all it does is restart the phone and boot to lock screen.
BEDickey said:
I was wondering if how to go about encrypting our phones on CM 12.1. For me all it does is restart the phone and boot to lock screen.
Click to expand...
Click to collapse
Settings --> Security - First thing listed should be encrypt phone.
I know that. I'm saying all that does is restart it to the lock screen, as I said. The phone is not actually encrypted in the process like it should, it just restarts.
With Mofo root, you had to encrypt on an unrooted stock ROM, then flash the rooted ROM after. Are similar also required with CM?
I'm not sure but you can temp disable root in CM by A) Disbaling it in SuperSU app - Uncheck "Enable Superuser" or B) In the settings under developer options - Change "root access" to "disabled". Try that and encrypt then re-enable after
Thanks! I will check it out and report back.
I'm having the exact same problem. I was never able to encrypt running total stock, computerfreek rom, or rremix rom. Device briefly shows the green android, then begins a soft reboot and then a full reboot. I have tried disabling root (both ways) as suggested above. It makes no difference.
Same here, I have the same situation. It seems as though either CM itself or the act of unlocking to bootloader has removed the ability to encrypt your phone. Any advice from people more in the know would be helpful.
In my case, I have never been able to encrypt... even with a totally stock, unmodified, unrooted, unmofo'd, bootloader locked device. Googling around, it seems like a problem where the disk is partitioned in such a way that there isn't the required space left for encryption to initiate. Anything looking like a solution was way over my comfort level (manual repartitioning via terminal), or in the case of some flashable scripts, was outdated.
Question: Did either of you change the format of your /data partition in TWRP to maybe ExFAT or F2FS?
I have never formatted anything.
I think it's one of things you cannot do, since the bootloader is unlocked. IIRC, it must be locked, regardless of the manufacturer. That's why we have the bootloader toggle in dev options.
Sent from my DROID Turbo using Tapatalk
Any updates on this... I have to believe there is some way to encrypt these devices, even if rooted with a custom rom. Rooting and installing a ROM in and of themselves do not diminish the added security provided by full device encryption.
P_6 said:
Any updates on this... I have to believe there is some way to encrypt these devices, even if rooted with a custom rom. Rooting and installing a ROM in and of themselves do not diminish the added security provided by full device encryption.
Click to expand...
Click to collapse
This worked for me:
1. Flash back to 100% stock.
2. Encrypt through security settings.
3. Flash whatever you want afterwards. The encryption will be preserved.
I'm currently encrypted and running CF's rom with no issues. A bootloader unlock does not prevent encryption from working.
Thanks for your response to this... I'm at Step 3, and using TWRP (Tried both 2.8 and 3.0) to flash CF 1.2.8. However, it will not successfully decrypt, regardless of what password I provide it (have tried complex & simple passwords, and the defaults listed out there, etc)
P_6 said:
Thanks for your response to this... I'm at Step 3, and using TWRP (Tried both 2.8 and 3.0) to flash CF 1.2.8. However, it will not successfully decrypt, regardless of what password I provide it (have tried complex & simple passwords, and the defaults listed out there, etc)
Click to expand...
Click to collapse
That's weird. The password should be the same as your lockscreen password. If you used a pattern lock, each dot on the pattern corresponds to a number, although I'm not sure which dot is which number. If your lockscreen password doesn't work, something went wrong and you'll probably have to wipe your phone to fix it.
TheSt33v said:
That's weird. The password should be the same as your lockscreen password. If you used a pattern lock, each dot on the pattern corresponds to a number, although I'm not sure which dot is which number. If your lockscreen password doesn't work, something went wrong and you'll probably have to wipe your phone to fix it.
Click to expand...
Click to collapse
That's what I figured. From what I've been reading, it should work just fine. I used an alphanumeric password to secure the phone, could that be part of the issue?
P_6 said:
That's what I figured. From what I've been reading, it should work just fine. I used an alphanumeric password to secure the phone, could that be part of the issue?
Click to expand...
Click to collapse
I doubt it. I used Cerberus to remotely change my pin to an alphanumeric password and then I forgot about it. When I rebooted the phone, I had to enter that password to decrypt the phone. It worked fine.
TheSt33v said:
I doubt it. I used Cerberus to remotely change my pin to an alphanumeric password and then I forgot about it. When I rebooted the phone, I had to enter that password to decrypt the phone. It worked fine.
Click to expand...
Click to collapse
So, using a simple 4 digit pin, I got TWRP to decrypt data. I installed CF 1.2.8 and changed my password to something more secure. I rebooted and got stuck in a bootloop. I've tried just about everything since, multiple wipes, reinstalls via TWRP, no dice. The encryption is still intact, but I can't get CF to boot.
P_6 said:
So, using a simple 4 digit pin, I got TWRP to decrypt data. I installed CF 1.2.8 and changed my password to something more secure. I rebooted and got stuck in a bootloop. I've tried just about everything since, multiple wipes, reinstalls via TWRP, no dice. The encryption is still intact, but I can't get CF to boot.
Click to expand...
Click to collapse
Weird. You might have to start all over again by going back to stock, and this time either keep the pin or just not deal with encryption.
Hi, I have a Mi5 and I'm not happy with the state of Global ROM so I'm thinking of switching ROMs
I also want Root access but I heard that rooting would require disabling Encryption. IF I can help it, I don't want to disable device encryption. What can I do to give root access to my apps that need it and remove preinstalled bloat but also keep it secure in case it gets lost or stolen?
I like encryption but I don't know if that helps with security if bootloader is unlocked.
I'll be honest. Bit it gets lost or stolen your encryption doesn't mean anything. It is easy to bypass all locks. So they would just unlock the device.
Encryption only really matters if your sending data over the Internet.
G'day XDA Developers.
I would love to root my Samsung Galaxy S10 then install a custom recovery (TWRP) then flash a custom rom (LinageOS) how ever I trip Knox when ever I attempt to do these things. So I was wondering how do you go about disabling Knox?
After some Googeling I found this site https://www.progeeksblog.com/how-to-disable-samsung-knox/ How ever these methods require you to first root your phone but rooting triggers Knox.
So I am at a loss here I am running stock android rom until I figure out how to bypass Knox.
OzGreatAndTerrible said:
G'day XDA Developers.
I would love to root my Samsung Galaxy S10 then install a custom recovery (TWRP) then flash a custom rom (LinageOS) how ever I trip Knox when ever I attempt to do these things. So I was wondering how do you go about disabling Knox?
After some Googeling I found this site https://www.progeeksblog.com/how-to-disable-samsung-knox/ How ever these methods require you to first root your phone but rooting triggers Knox.
So I am at a loss here I am running stock android rom until I figure out how to bypass Knox.
Click to expand...
Click to collapse
you cant completely block knox...
unlocking bl and flashing modified firmeare wil trip knox.. u cant reset knox flag either
Update: You can disable Knox by using Multidisabler: https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
OzGreatAndTerrible said:
Update: You can disable Knox by using Multidisabler: https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
Click to expand...
Click to collapse
thats always been around lolol.. but regardless ur post was more about not tripping knox which ur knox is in fact tripped so "disabling" knox doesnt change anything really.. also, that zip doesnt really disable knox.. it disables verification, defex, force encryption etc.
Actually it says that it disables vault keeper which is supposed to replace Knox but any way yea your right my post was more about flashing anything trips knox so how are you supposed to get around that.
OzGreatAndTerrible said:
Actually it says that it disables vault keeper which is supposed to replace Knox but any way yea your right my post was more about flashing anything trips knox so how are you supposed to get around that.
Click to expand...
Click to collapse
vaultkeeper is not to replace knox.. samsung bases all their security on knox.. vaultkeeper is in addition to knox..
there is no way around tripping knox.. the knox warranty bit is a physical fuse that gets blown when bl is unlocked and u flash a custom firmware and there is no way to reset it..
magiskhide can sometimes "fake" it but with safetynet improving if ur device is set to use hardware then there wont be any way around that either in the long run
elliwigy said:
vaultkeeper is not to replace knox.. samsung bases all their security on knox.. vaultkeeper is in addition to knox..
there is no way around tripping knox.. the knox warranty bit is a physical fuse that gets blown when bl is unlocked and u flash a custom firmware and there is no way to reset it..
magiskhide can sometimes "fake" it but with safetynet improving if ur device is set to use hardware then there wont be any way around that either in the long run
Click to expand...
Click to collapse
If your not worried about warranties or anything then tripping Knox doesn't matter?
ryanallaire said:
If your not worried about warranties or anything then tripping Knox doesn't matter?
Click to expand...
Click to collapse
it will likely cause most samsung apps not to work unless theres any tricks that still work also
ryanallaire said:
If your not worried about warranties or anything then tripping Knox doesn't matter?
Click to expand...
Click to collapse
I don't care about voiding warranty. What happens when I try and flash anything custom on the device Knox gets tripped and the phone refuses to boot. Thats what I am talking about trying to bypass.
I have Galaxy Tab Active3, which is locked to organization and it seems to have Knox enabled.
I want to Factory reset it so I can use it for private use.
I cannot get it into download mode, but I can get it in recovery mode. However, the Wipe data/factory reset option seems to be disabled.
Dialing *#0*# and *#*#88#*# from emergency dialer do not work either.
Any advice how to remove the Knox protection and factory reset the device, so I can set it up from scratch and remove the organization lock?
checho_85 said:
I have Galaxy Tab Active3, which is locked to organization and it seems to have Knox enabled.
I want to Factory reset it so I can use it for private use.
I cannot get it into download mode, but I can get it in recovery mode. However, the Wipe data/factory reset option seems to be disabled.
Dialing *#0*# and *#*#88#*# from emergency dialer do not work either.
Any advice how to remove the Knox protection and factory reset the device, so I can set it up from scratch and remove the organization lock?
Click to expand...
Click to collapse
I would be interested in, too.
after the one ui3.1/android11 it is sort of easier to relock the bootloader. you may want to take backups of anything you need from your device when your bootloader is still unlocked. you could use anything from google backups and samsung backups (suggested) to smart switch backups, literally copy pasting files to your pc, etc and more.
(disclsimer: i am not responsible for any damage to any of your devices/property/data etc )
why would one want to relock their bootlaoder? simple.
1) to revalidate their warranty if they have any
2) to receive automatic ota updates again
3) simply for needing something more secure due to a change of field, etc
4) regretting trying to do a failed attempt at installing any modifications and wanting to relock it to lock off and forget about your shame (oddly specific i know )
so its pretty simple. sorry for some of the prior padding out
you need to boot into recovery mode by connecting your device to a cable and using your device specific key combo and completely factory reset and wipe any data after backing up, and then again, boot into download mode and long pressing the volume up button or whatever button it specifies to go to the bootloader lock/unlock screen (ps: important, hold it till the screen changes and says or mentions the bootloader, don't just press it once!!!) and then confirm using the specified button. this will factory reset all your data, but also untrip any securities such as knox guard etc (at least it did for me) wait for some time till it finishes data wipe, system stock install and also some garbage bloatware depending on your area
ps: if i recall correctly this only works on oneui3.0+/android11+ devices, even on other models and devices supporting the above specified software
hope this helps if youre a newbie etc
Cheemsdoge said:
after the one ui3.1/android11 it is sort of easier to relock the bootloader. you may want to take backups of anything you need from your device when your bootloader is still unlocked. you could use anything from google backups and samsung backups (suggested) to smart switch backups, literally copy pasting files to your pc, etc and more.
(disclsimer: i am not responsible for any damage to any of your devices/property/data etc )
why would one want to relock their bootlaoder? simple.
1) to revalidate their warranty if they have any
2) to receive automatic ota updates again
3) simply for needing something more secure due to a change of field, etc
4) regretting trying to do a failed attempt at installing any modifications and wanting to relock it to lock off and forget about your shame (oddly specific i know )
so its pretty simple. sorry for some of the prior padding out
you need to boot into recovery mode by connecting your device to a cable and using your device specific key combo and completely factory reset and wipe any data after backing up, and then again, boot into download mode and long pressing the volume up button or whatever button it specifies to go to the bootloader lock/unlock screen (ps: important, hold it till the screen changes and says or mentions the bootloader, don't just press it once!!!) and then confirm using the specified button. this will factory reset all your data, but also untrip any securities such as knox guard etc (at least it did for me) wait for some time till it finishes data wipe, system stock install and also some garbage bloatware depending on your area
ps: if i recall correctly this only works on oneui3.0+/android11+ devices, even on other models and devices supporting the above specified software
hope this helps if youre a newbie etc
Click to expand...
Click to collapse
The Knox flag is controlled by an e-fuse. Once you blow this fuse, it's permanent. Once Knox is tripped, it cannot be reset back without a motherboard replacement.
enigmaamit said:
The Knox flag is controlled by an e-fuse. Once you blow this fuse, it's permanent. Once Knox is tripped, it cannot be reset back without a motherboard replacement.
Click to expand...
Click to collapse
ok then idk how buy i untripped it on my m30s using this method, its status is 0x0
Cheemsdoge said:
ok then idk how buy i untripped it on my m30s using this method, its status is 0x0
Click to expand...
Click to collapse
Are you sure it got tripped to 0x1 ?
DaReDeViL said:
Are you sure it got tripped to 0x1 ?
Click to expand...
Click to collapse
yep. i had once rooted it the wrong way and in download mode it said knox status 0x1 and also had tripped dm verity accidentally by forgetting to add the correct vbmeta and boot into my twrp and magisk
Cheemsdoge said:
yep. i had once rooted it the wrong way and in download mode it said knox status 0x1 and also had tripped dm verity accidentally by forgetting to add the correct vbmeta and boot into my twrp and magisk
Click to expand...
Click to collapse
Download mode will still show 0x1 regardless, if you every actually tripped it before.
If you're showing 0x0 your Knox was never tripped. Simple.
Beefheart said:
If you're showing 0x0 your Knox was never tripped. Simple.
Click to expand...
Click to collapse
oh! sorry for the wrong info then. lemme update. apologies if this caused any confusion :-(.
Thread closed due to conflicting information. Sorry for the inconvenience.