Hello folks,
after getting more and more paranoid about the more or less unprotected files on my smartphone, I would like to encrypt it. Anyway I want to make shure that I will be able to flash Custom Roms as usual. I already read some threads about TWRP supporting encryption, but they are all relatively outdated and from a time where this was more or less an experimental feature, so here comes my question:
How are your experiences with TWRPs encryption support? Will I be able to flash custom roms? What problems did you encounter? What do I need to take into account before encrypting my phone?
I hope you can help me, if you have any other sources I should read, let me know.
Thank you
Simon
Is this such a trivial question or does nobody have any experience with this issue?
smonsays said:
Is this such a trivial question or does nobody have any experience with this issue?
Click to expand...
Click to collapse
I don't think most people use encryption. My experience on the n9 which is encrypted by default is that twrp works fine and you can flash custom roms. It takes awhile for twrp to boot up because it has to decrypt so be prepared for that.
To encrypt you will have to do a factory reset so backup first.
Sent from my Nexus 5 using XDA Free mobile app
Thanks for your reply! Kind of surprising that encryption is so unpopular.
How does TWRP get the password for the decryption? Is it as simple as a dialog box?
jd1639 said:
I don't think most people use encryption. My experience on the n9 which is encrypted by default is that twrp works fine and you can flash custom roms. It takes awhile for twrp to boot up because it has to decrypt so be prepared for that.
To encrypt you will have to do a factory reset so backup first.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
smonsays said:
Thanks for your reply! Kind of surprising that encryption is so unpopular.
How does TWRP get the password for the decryption? Is it as simple as a dialog box?
Click to expand...
Click to collapse
It is a dialogue box. I would suggest a pin. I think twrp supports a pattern now but before it was a real pita.
Sent from my Nexus 5 using XDA Free mobile app
Related
Hi,
I have rooted my S5 and want to enable the encryption.
But when I start the encryption it reboots after some seconds without encrypting.
I have unrooted the device and the encryption works well. Afterwards I have rooted again and then the deivice does not boot, so I had to reset.
Is there a way to encrypt a rooted device?
Robby69 said:
Hi,
I have rooted my S5 and want to enable the encryption.
But when I start the encryption it reboots after some seconds without encrypting.
I have unrooted the device and the encryption works well. Afterwards I have rooted again and then the deivice does not boot, so I had to reset.
Is there a way to encrypt a rooted device?
Click to expand...
Click to collapse
Are you also running custom recovery and what rom?
I think the phone might have to have all the knox files for the encryption to work properly.
tdunham said:
Are you also running custom recovery and what rom?
I think the phone might have to have all the knox files for the encryption to work properly.
Click to expand...
Click to collapse
I have only done the CF root, nothing else, no custom recovery.
Would be interesting if someone has a rooted S5 where device encryption works.
Robby69 said:
I have only done the CF root, nothing else, no custom recovery.
Would be interesting if someone has a rooted S5 where device encryption works.
Click to expand...
Click to collapse
That's odd. It must be related to root then.
I don't have any experience with encryption and I'm fairly new to Knox as well so I may not be much help. A brief search didn't yield any promising results for having both encryption AND root, sorry.
tdunham said:
That's odd. It must be related to root then.
I don't have any experience with encryption and I'm fairly new to Knox as well so I may not be much help. A brief search didn't yield any promising results for having both encryption AND root, sorry.
Click to expand...
Click to collapse
Yes I have searched quite a lot but I could not find any info. Maybe people do not use encryption that much.
Robby69 said:
Yes I have searched quite a lot but I could not find any info. Maybe people do not use encryption that much.
Click to expand...
Click to collapse
I hear about it more on the Corporate phones that require everything to be encrypted.
Hi guys,
do you still have that issue?
I encountered a problem activating encryption on a rooted SM-P900. I'm not sure, but I think it's a general problem with Samsung KitKat devices. I described, how I got it solved for my device here. Have a look at my thread and let me know, if it works for you...
Cheers!
bruzzy said:
Hi guys,
do you still have that issue?
I encountered a problem activating encryption on a rooted SM-P900. I'm not sure, but I think it's a general problem with Samsung KitKat devices. I described, how I got it solved for my device here. Have a look at my thread and let me know, if it works for you...
Cheers!
Click to expand...
Click to collapse
Nice details on your your steps. This will not work for me as I have the VZW edition and not the developer edition. But I hope this works out for others that can use a custom recovery.
Ainvar said:
Nice details on your your steps. This will not work for me as I have the VZW edition and not the developer edition. But I hope this works out for others that can use a custom recovery.
Click to expand...
Click to collapse
Sorry for my ignorance, but what is with the VZW edition different? (google says: VZW = Verizon Wireless)
I am also rooted and cannot encrypt my device. Has any progress been made on finding a way to do it? I do not want to unroot and stay unrooted just so I can encrypt my device... On the other hand I cannot receive email so no encryption is also a no go ...
..
This is what fixed this issue for me in case any of you guys were still looking for the solution
http://forum.xda-developers.com/showthread.php?t=2487018&page=3
So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.
None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.
Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?
Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!
Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.
Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.
did it flash the vendor?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk
Coming from many years with Samsung phones, I have only had to backup system, data and cache to save a rom setup. On the 6 P there are a lot of options. I'm on WEDA Audiophile rom but want to make a backup to try a different one. What do I need to select in TWRP to save everything needed to go back to this rom?
Thanks for any advice, Jack
Data, System, Boot, Vendor should do the trick.
midmadn said:
Coming from many years with Samsung phones, I have only had to backup system, data and cache to save a rom setup. On the 6 P there are a lot of options. I'm on WEDA Audiophile rom but want to make a backup to try a different one. What do I need to select in TWRP to save everything needed to go back to this rom?
Thanks for any advice, Jack
Click to expand...
Click to collapse
Make a backup of your EFS first and keep it safe in case. Make sure you are using the latest TWRP (3.0.2-3) to avoid problems. Backup system, boot and data. You don't actually need the vendor.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
Make a backup of your EFS first and keep it safe in case. Make sure you are using the latest TWRP (3.0.2-3) to avoid problems. Backup system, boot and data. You don't actually need the vendor.
Click to expand...
Click to collapse
Thank You.
ultyrunner said:
Make a backup of your EFS first and keep it safe in case. Make sure you are using the latest TWRP (3.0.2-3) to avoid problems. Backup system, boot and data. You don't actually need the vendor.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Latest version of TWRP is 3.0.2-2, no? This is like the 3rd or 4th time I've seen "3.0.2-3" mentioned, but per the official TWRP site and everywhere I've seen, 3.0.2-2 is the latest....so just figured I'd clarify
ohlin5 said:
Latest version of TWRP is 3.0.2-2, no? This is like the 3rd or 4th time I've seen "3.0.2-3" mentioned, but per the official TWRP site and everywhere I've seen, 3.0.2-2 is the latest....so just figured I'd clarify
Click to expand...
Click to collapse
I am on Tapatalk so hard to grab a URL. Search for 3.0.2-3 on XDA, should be in the TWRP fatal flaw thread. Unofficial but published by one of the devs, rid of the bugs of -1 & -2.
Edit: Here you go ... https://idlekernel.com/twrp/nexus/ (Angler version of course)
Sent from my Nexus 6P using Tapatalk
Code:
ultyrunner said:
I am on Tapatalk so hard to grab a URL. Search for 3.0.2-3 on XDA, should be in the TWRP fatal flaw thread. Unofficial but published by one of the devs, rid of the bugs of -1 & -2.
Edit: Here you go ... https://idlekernel.com/twrp/nexus/ (Angler version of course)
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Very interesting, good to know thanks!!
ohlin5 said:
Code:
Very interesting, good to know thanks!!
Click to expand...
Click to collapse
NP. The thanks button works too
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
NP. The thanks button works too
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Haha thanks for the reminder
Hello, some phone/roms let you do that (such as the galaxy phones rom as i recall), is that the case with the YT2 LP rom?
My YotaPhone is encrypted and I see no possibility to decrypt it in the Security menu.
I also seem to remember that during the encrypting it said that there's no way of decrypting it again except for a reset.
If so, i can't do it without TWRP supporting data decryption. Can you please tell me if the one that came out yesterday (v3.x) does?
goja said:
If so, i can't do it without TWRP supporting data decryption. Can you please tell me if the one that came out yesterday (v3.x) does?
Click to expand...
Click to collapse
I'm not using TWRP so can't help you there, sorry.
You don't plan to use it? Surprising.
Sent from my YD201 using Tapatalk
Nobody else tried?
Sent from my P9000
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Unless you are on the totally stock system then I wouldn't lock your bootloader.
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
mrcooter said:
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
Click to expand...
Click to collapse
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
If you relock your bootloader with anything other than a factory image you will brick your device.
vjyrdy said:
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
Click to expand...
Click to collapse
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
mrcooter said:
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
Click to expand...
Click to collapse
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
zlost1 said:
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
Click to expand...
Click to collapse
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Sent from my PH-1 using XDA Labs
swiftbones74 said:
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Click to expand...
Click to collapse
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
zlost1 said:
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
Click to expand...
Click to collapse
This ain't the rocket and thread forum or the whatever dumb other thing forum so it really doesn't matter what the answer is.
Sent from my PH-1 using XDA Labs
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
zlost1 said:
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
Click to expand...
Click to collapse
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
MOD EDIT
You are one trippy person ? if you really feel the need to post about your LG phone in the mata thread go right ahead buddy.
Sent from my PH-1 using XDA Labs
MOD EDIT
It's worth noting that the Essential PH-1 uses an A/B partition system so any advice given here would not be helpful in the slightest for devices that don't have the same file system. Quickly doing a search of your phone reveals it's not an A/B partitioned system so following advice here could potentially lead to you actually destroying your phone.
could you lock the BL once rooted if in fastboot mode it lists device tampering = false?
Wonderful reply
tech_head said:
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
Click to expand...
Click to collapse
Thanks, this reply should be pinned to the top of the thread. It is crucial information for our dear noobies
swiftbones74 said:
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
Click to expand...
Click to collapse
Just an opinion, but...there are rules for posting in forums that Dev's, no matter how over worked and underpaid/appreciated should follow as well. Teach by example not proxy. Applaud the calm gentleman who responded with eloquent grammar and poise.
NaterTots said:
Unless you are on the totally stock system then I wouldn't lock your bootloader.
Click to expand...
Click to collapse
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
rossrosh007 said:
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
Click to expand...
Click to collapse
I don't know.