Related
Has anyone noticed any issue on their h815 with regards to encrypting the phone? Mine does not work; full or quick option. Has unlocking the bootloader caused this to stop working? I have got root and twrp recovery. Could the custom recovery be causing the phone to get stuck on rebooting to encrypt? The lg website says certain features no longer work after the bootloader is unlocked; maybe this is one of those? All just guess work atm, any help would be appreciated.
v1ne said:
Has anyone noticed any issue on their h815 with regards to encrypting the phone? Mine does not work; full or quick option. Has unlocking the bootloader caused this to stop working? I have got root and twrp recovery. Could the custom recovery be causing the phone to get stuck on rebooting to encrypt? The lg website says certain features no longer work after the bootloader is unlocked; maybe this is one of those? All just guess work atm, any help would be appreciated.
Click to expand...
Click to collapse
Hi,
i do not know, as I do NOT (yet?) own the device! But I would love to know! Any unlocked + encrypted phones out there? I would be interested how many of the geeks around here encrypt their phones?
For me, these days, I do not own a single device (PC, Notebook, Smartphone whatever) that is NOT encrypted. The more easy you loose the device, the more encryption should be a standard.
What is the reality? And does it work with the unlocked bootloader?
v1ne said:
I have got root and twrp recovery. Could the custom recovery be causing the phone to get stuck on rebooting to encrypt? d.
Click to expand...
Click to collapse
Exactly the same here! I would be very happy if someone could help me out, maybe by looking at some logcat files? The device is rooted after all. Just tell me what log files you would need?
I would like to try to flash the stock recovery. Delete TWRP as I think this could be the culprit. I read about bringing the device back to stock but I am unsure what files I do need exactly and how to proceed. I downloaded the LG Flash tool. Any help would be very much appreciated!
I just got this phone, rooted, unlocked BL, installed Xposed. I tried to encrypt phone, but when I started the process, it rebooted and now it's at the white T-Mobile splash screen. There's no progress indication anywhere and it has been almost an hour. I think I'll have to pull battery.
v1ne said:
Has anyone noticed any issue on their h815 with regards to encrypting the phone? Mine does not work; full or quick option. Has unlocking the bootloader caused this to stop working? I have got root and twrp recovery. Could the custom recovery be causing the phone to get stuck on rebooting to encrypt? The lg website says certain features no longer work after the bootloader is unlocked; maybe this is one of those? All just guess work atm, any help would be appreciated.
Click to expand...
Click to collapse
Did you (or fpsq) manage to do this in the end (and if yes, how)? I have the same issue I think... rooted the phone with the method here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
and now the phone gets stuck on the initial reboot after launching encryption. It works if I unplug the battery, which shows it doesn't even start the process.
Thanks for any help.
It didn't get anywhere, so I tried it again with quick encryption. Same white screen. I rooted with a huge pre-rooted system image. using dd. Did you unlock boot loader, install custom recovery, or install Xposed?
OGIGA said:
It didn't get anywhere, so I tried it again with quick encryption. Same white screen. I rooted with a huge pre-rooted system image. using dd. Did you unlock boot loader, install custom recovery, or install Xposed?
Click to expand...
Click to collapse
No to all three. I also used dd but first dumped my system partition, injected the root files, and then rewrote it (rather than the main method that you used, writing the ready-made image). See the thread I linked earlier for details.
It really seems the root is the problem here. fpsq seems to have gotten it working in a roundabout way:
http://forum.xda-developers.com/showpost.php?p=62156629&postcount=1468
but I don't understand exactly what he did, I PMed him to ask.
WARNING: Once you encrypt your phone/sdcard you can NOT cancel the process. After you encrypt your phone/sdcard, if you forget your password, you will have to factory reset (wipes /data) and/or format your sdcard (wipes /external_SD) to get a useable phone. Your data WILL be lost!
Also TWRP can not read encrypted volumes other than some Nexus devices, so make a backup BEFORE you encrypt it or the internal/external sdcard.
Overview: You have to kill the SuperSu daemon (temporarily unrooting it) and THEN start the stock encryption process.
1. Install Busybox (need the pkill utility)
2. Open Terminal Emulator and:
Code:
$ su
# pkill -KILL daemonsu
$ exit
NOTE: You'll notice that the # changed back to $. This means that you are no longer the root user and the SuperSu daemon is not running. Do NOT open any other apps, including the SuperSu app.
3. Now go to Settings ---> Security ---> Encrypt Phone.
IMPORTANT: Make sure your phone charger is plugged in. Go through the prompts to encrypt your phone and/or sdcard and the phone will reboot. It will stay at the bootscreen for about a minute and then you will see the white encryption screen. it will ask you for an encryption password. Once you set that, write it down, email it to yourself, whatever you have to do to remember it because if you forget it, there is no helping you. You will have to factory reset (wipes /data) to get a useable phone. Your data WILL be lost!
It will run until it gets to 100% and the phone will reboot. Once it comes back up with the white screen, enter your password and the boot phone will finish booting. To check that the phone/sdcard is encrypted, go to Settings ---> Security and under Encrypt Phone and Encrypt SD card storage, you should see "Encrypted".
Hope this helps.
barcodelinux said:
You have to kill the SuperSu daemon (temporarily unrooting it) and Then start the stock encryption process.
Click to expand...
Click to collapse
It works! And it's so clear why it works, now why didn't I think of this?
Thanks a lot for figuring it out and posting it here, you really helped me! Phones hold so much private data nowadays and are so easy to lose that I was really uncomfortable using it unencrypted.
OGIGA said:
I just got this phone, rooted, unlocked BL, installed Xposed. I tried to encrypt phone, but when I started the process, it rebooted and now it's at the white T-Mobile splash screen. There's no progress indication anywhere and it has been almost an hour. I think I'll have to pull battery.
Click to expand...
Click to collapse
Hey there - did you get any luck with this? My G4 updated to MM last week, and now I'm trying encryption - but it's been sitting on the initial boot screen for over an hour (not a loop, just that one screen), with no progress bar or screen.
No idea what it's doing, but hoping that pulling the battery out won't brick it completely!
PS. my phone isn't even rooted, so it can't be THAT causing a problem
Thanks,
J
jasonnm said:
Hey there - did you get any luck with this? My G4 updated to MM last week, and now I'm trying encryption - but it's been sitting on the initial boot screen for over an hour (not a loop, just that one screen), with no progress bar or screen.
No idea what it's doing, but hoping that pulling the battery out won't brick it completely!
PS. my phone isn't even rooted, so it can't be THAT causing a problem
Thanks,
J
Click to expand...
Click to collapse
I just installed Marshmallow last week and took a stab at encryption again. I installed TWRP 2.7.8.1, by the way. What I also did was flash what I think is the original boot.img. I think this would have un-rooted my device and maybe un-Xposed too, but I forgot because I was really sick last week.
Anyway, the standard device encryption actually worked. I opted for /data encryption instead of full device. Funny thing was that the first time I did it, it was stuck at the boot screen, but was actually encrypting. I didn't know that, so I took out the battery and it screwed up my /data, so the OS made me wipe /data. Fortunately, I backed up right when I did Marshmallow, so I restored my /data. I went to encrypt again and waited this time. Eventually, the screen went from boot screen to the encrypting screen starting at like 60% finished. It finished and my /data was encrypted!
I went to TWRP but TWRP could not decrypt my /data no matter what password I tried. Since my /system and /boot were not encrypted, SuperSU installation was easy. I got the password screen at boot like expected.
However, when I installed Xposed, the password screen would keep popping up with "_____ has stopped" persistently and I had to time it right hit each key of the password. When I uninstalled Xposed, the popups stopped. Installed Xposed again, popups were back. After struggling to enter the password and booting up, everything works fine.
That's how much I have experienced so far.
OGIGA said:
I just installed Marshmallow last week and took a stab at encryption again. I installed TWRP 2.7.8.1, by the way. What I also did was flash what I think is the original boot.img. I think this would have un-rooted my device and maybe un-Xposed too, but I forgot because I was really sick last week.
Anyway, the standard device encryption actually worked. I opted for /data encryption instead of full device. Funny thing was that the first time I did it, it was stuck at the boot screen, but was actually encrypting. I didn't know that, so I took out the battery and it screwed up my /data, so the OS made me wipe /data. Fortunately, I backed up right when I did Marshmallow, so I restored my /data. I went to encrypt again and waited this time. Eventually, the screen went from boot screen to the encrypting screen starting at like 60% finished. It finished and my /data was encrypted!
I went to TWRP but TWRP could not decrypt my /data no matter what password I tried. Since my /system and /boot were not encrypted, SuperSU installation was easy. I got the password screen at boot like expected.
However, when I installed Xposed, the password screen would keep popping up with "_____ has stopped" persistently and I had to time it right hit each key of the password. When I uninstalled Xposed, the popups stopped. Installed Xposed again, popups were back. After struggling to enter the password and booting up, everything works fine.
That's how much I have experienced so far.
Click to expand...
Click to collapse
Thanks for the extra info - need to try again when I get a bit more time, but I eventually pulled the battery (risky, I know!) and put it back in and everything was normal, like nothing had changed. Certainly no encryption anywhere.
Will update when I give it another try.
Thanks again!
So if I had my SD card encrypted, and my phone puked, I get another G4 and want to use my old SD card (I have the password) how can I access the files on the SD card ?
Sent from my iPhone using Tapatalk
Hey guys,
Just as I wanted to update to an Android M ROM I realized decrypting the phone somehow doesn't work. In Settings it says "Encrypted Phone Encrypted" but if I click it nothing happens. Here is a video for demostration: https://youtu.be/cOFFZuckUU0 . In Recovery I can't mount any of the encrypted partitions yet when I restart my phone it does't ask for the decryption code and Android works like always. Any way to get the phone decrypted again?
Thanks in advance!
P.S.: After hours of research I couldn't find anything remotely similar to my issue. It doesn't even make sense that the phone decrypts itself without me putting in a code...
P.S.S: Oh and the issue appeared just a few days ago. Before that I could encrypt and decrypt my phone as often as i wanted to and android always asked for the code before booting.
Anyone?
.TanTien said:
Anyone?
Click to expand...
Click to collapse
You can't decrypt. You mast make a full wipe. If You dont want lose date use Titanium Backup or TWRP Manager with live backup.
You can only turn off, not decrypt ! a sd card encryption
A friend of mine has the same phone as I have - a OnePlus 3 which we both bought at launch. When he got it, he activated the secure startup in the start up configurations - I didn't.
After a while, he changed his mind to go to CyanogenMod (I always help him with flashing stuff, getting him TWRP, try to explain everything) so I got him the (back then) latest CM. The problem was (and still is) that his secure startup still shows up. He doesen't want it anymore, so do I. I go nuts asking him every time to unlock TWRP / his phone just to change something.
Until now I was always able to answer his questions - I read this forums all the time, and google is my best friend. However it seems that no one actually has this problem, or at least isn't really aware of it. The secure startup is an option under settings, but even if we disable it, after a reboot it shows up again. It shows up even after formatting the whole phone. I deleted all of the partitons, but it still shows. I have no clue where it actually is saved, since it remembers not only the language the phone was prior set to, but also the "welcome message".
Is it in the bootloader? If so, how do I get rid of it?
Another idea was to install an old backup of the original OS, but he doesen't have it anymore. My idea was to recover the backup, then disable the settings in hope that the system thinks "well ok, the hash seems to be the same so ok, I let you through with it".
Any help would be great, since I really have no idea anymore.
__revolt__ said:
A friend of mine has the same phone as I have - a OnePlus 3 which we both bought at launch. When he got it, he activated the secure startup in the start up configurations - I didn't.
After a while, he changed his mind to go to CyanogenMod (I always help him with flashing stuff, getting him TWRP, try to explain everything) so I got him the (back then) latest CM. The problem was (and still is) that his secure startup still shows up. He doesen't want it anymore, so do I. I go nuts asking him every time to unlock TWRP / his phone just to change something.
Until now I was always able to answer his questions - I read this forums all the time, and google is my best friend. However it seems that no one actually has this problem, or at least isn't really aware of it. The secure startup is an option under settings, but even if we disable it, after a reboot it shows up again. It shows up even after formatting the whole phone. I deleted all of the partitons, but it still shows. I have no clue where it actually is saved, since it remembers not only the language the phone was prior set to, but also the "welcome message".
Is it in the bootloader? If so, how do I get rid of it?
Another idea was to install an old backup of the original OS, but he doesen't have it anymore. My idea was to recover the backup, then disable the settings in hope that the system thinks "well ok, the hash seems to be the same so ok, I let you through with it".
Any help would be great, since I really have no idea anymore.
Click to expand...
Click to collapse
Just a thought.
May be the phone picks up the settings from your Google account. Try setting it up as a new phone after wiping and flashing either with a new Google account or with no account and see if the issue returns.
__revolt__ said:
A friend of mine has the same phone as I have - a OnePlus 3 which we both bought at launch. When he got it, he activated the secure startup in the start up configurations - I didn't.
After a while, he changed his mind to go to CyanogenMod (I always help him with flashing stuff, getting him TWRP, try to explain everything) so I got him the (back then) latest CM. The problem was (and still is) that his secure startup still shows up. He doesen't want it anymore, so do I. I go nuts asking him every time to unlock TWRP / his phone just to change something.
Until now I was always able to answer his questions - I read this forums all the time, and google is my best friend. However it seems that no one actually has this problem, or at least isn't really aware of it. The secure startup is an option under settings, but even if we disable it, after a reboot it shows up again. It shows up even after formatting the whole phone. I deleted all of the partitons, but it still shows. I have no clue where it actually is saved, since it remembers not only the language the phone was prior set to, but also the "welcome message".
Is it in the bootloader? If so, how do I get rid of it?
Another idea was to install an old backup of the original OS, but he doesen't have it anymore. My idea was to recover the backup, then disable the settings in hope that the system thinks "well ok, the hash seems to be the same so ok, I let you through with it".
Any help would be great, since I really have no idea anymore.
Click to expand...
Click to collapse
Format whole device leave nothing. Use this chance to convert data to f2fs. Then the password will be gone. And you will have an empty phone to start afresh with
I had issues in the past with encrypting my M8, was using clockworkmod and Cyanogen, and could not process updates without fully wiping.
Ultimately I accepted this because I cannot live with having the phone not encrypted.
I now have a new M9, Running TWRP and Lineage 14.
All is working beautifully, no complaints, however I would like to encrypt the phone so I started doing research if this new setup would have issues.
Seems there is mixed advice on different device models having various issues with encrypted images and TWRP not being able to properly update automatically or manually.
Anyone have an M9, encrypted, TWRP and the latest Lineage.
If so known working versions of TWRP to use or avoid? Any required firmware levels, OS build dates, etc?
Just looking for yes, I am doing it and it works on x+y+x configuration, or No, this is going to end in misery.
Not instructions per se unless there are some specific points that lead to a definitive success / failure.
any advice appreciated.
Hi, I have super inactive on the forum for a very long and I signed in for the first time in a few years to answer this.
I also ran into an issue with encryption and lineage os. I found an answer online that I can confirm worked for me.
I am running the latest nightly (Nov 7) and have no issues with installing updates through the settings menu. I am not sure which time version of twrp I am on at the moment and I can't check right now.
I also have a himaul. As Markus said, the last CM13 was able to encrypt properly. That gives us a time-consuming workaround:
Do a fresh install of cm-13.0-20161218-NIGHTLY-himaul. (I got it from https://archive.org/download/cmarchive_nighlies )
Set a PIN and encrypt the phone normally through settings. (I did not try a password or pattern.)
twrp should be able to decrypt properly. Perform the default (i.e., rm -rf, non-formatting) wipe.
adb sideload lineage-14.1-20170516-nightly-himaul-signed
LOS will boot to the standard decryption prompt and should succeed with the PIN from step 2.
LOS will not have a screen lock enabled. I set the same PIN from step 2 and was able to decrypt with it on the next boot. I changed my PIN to another value and was able to decrypt with the new PIN on the next boot.
If you do not set a PIN in step 2, you will still get a PIN prompt in step 5, but there will be no correct answer and you'll have to start over.
This procedure gave me a himaul running the latest LOS nightly that believes it is properly encrypted. I uploaded a logcat from the CM13 encryption run that succeeded as encryption.cm13.log
Click to expand...
Click to collapse
Source https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-457 (click to view older comments)
I was able to change the decryption pin (using "cryptfs" from the play store) to a password required upon boot and and I was able to set a pattern lock to unlock the screen.
Edit: To clarify, I ran into a boot loop issue upon trying to encrypt the phone with lineage installed. I can use the automatic updating without issues(so far)
Thank you very much for the input!
I am on the newest twrp-3.1.1-0-hima, and the latest nightly lineage (11/7) as well.
No play store, no google app anything, just a basic subset of productivity tools, and blazing fast performance.
Trying to decide if I want to chance this, this weekend, I will report back for posterity success/fail or at least if I chicken out.
This M9 is running amazingly smooth as is, I hate to toast it, but that's how we learn and the price we pay for not being charged by ATT to be their product
Thanks again for the input, and still would love to hear other's success/fail stories if theyhave them.
Well, to anyone that wants to go there, I can tell you that if you just tell the phone to encrypt, it will not complain, however when it is complete, you will never see the OS again....
Had to reload from scratch, and restore everything I backed up before hand. I did not have time to go back and try alternative ways or methods, maybe next weekend...
The solution I linked worked for me personally, its unfortunate that you couldn't get it to work. Did you do the correct type of wiping ? There is one that deletes the files but leave encryption in tact while the other type is formatting which removes encryption. Also did you give your phone some time to rebuild the dalvik/art cache after installing lineage os?
Dear All,
I'm a happy owner aof a brand new OP9Pro. Just upgraded from an older OP3.
I already installed LineageOS on it, the latest one with Android 12.
I noticed, that in Settings-Security-Encryption and credentials the Encryption status says Encrypted. This is good, it is just like my old OP3 used to be. However, unlike in the case of the OP3, when booting up, the OP9Pro doesn't ask for a password or pin or anything, just boots fine. What is going on here? If it is not encrypted, then why does it say encrypted. If it is encrypted, then what is the password/pin and why does it auto decrypt.
More importantly, how can I correct this issue? (to be clear, I would like to create my own encryption password and want to enter it every time the system boots)
What am I missing?
viktak said:
Dear All,
I'm a happy owner aof a brand new OP9Pro. Just upgraded from an older OP3.
I already installed LineageOS on it, the latest one with Android 12.
I noticed, that in Settings-Security-Encryption and credentials the Encryption status says Encrypted. This is good, it is just like my old OP3 used to be. However, unlike in the case of the OP3, when booting up, the OP9Pro doesn't ask for a password or pin or anything, just boots fine. What is going on here? If it is not encrypted, then why does it say encrypted. If it is encrypted, then what is the password/pin and why does it auto decrypt.
More importantly, how can I correct this issue? (to be clear, I would like to create my own encryption password and want to enter it every time the system boots)
What am I missing?
Click to expand...
Click to collapse
Go into settings/security and lock screen/lock screen passcode
I have done that, but no matter which one I set up, it wouldn't ask for it when the phone boots.
viktak said:
I have done that, but no matter which one I set up, it wouldn't ask for it when the phone boots.
Click to expand...
Click to collapse
Then I don't know what the answer would be. All I know is that I see so many users having issues with custom roms. That is why I stay with stock rom.
I'm too old for cherry picking and starting fresh each round. F all that. C-63 is pretty damn righteous. And Ob1 is awesome so ob2 is gonna be a dd I feel.
viktak said:
Dear All,
I'm a happy owner aof a brand new OP9Pro. Just upgraded from an older OP3.
I already installed LineageOS on it, the latest one with Android 12.
I noticed, that in Settings-Security-Encryption and credentials the Encryption status says Encrypted. This is good, it is just like my old OP3 used to be. However, unlike in the case of the OP3, when booting up, the OP9Pro doesn't ask for a password or pin or anything, just boots fine. What is going on here? If it is not encrypted, then why does it say encrypted. If it is encrypted, then what is the password/pin and why does it auto decrypt.
More importantly, how can I correct this issue? (to be clear, I would like to create my own encryption password and want to enter it every time the system boots)
What am I missing?
Click to expand...
Click to collapse
Every time you reboot your phone, you must enter your password/PIN if you set one to get past the lock screen, it's called Before First Unlock. It doesn't ask for a password to turn on your phone, just to get past the lock screen. Also, the keys are not in memory, so this is the encryption part.
ok, thanks. Something must have changed though since Android 11. Thank you for the clarification!