I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
jtguf87 said:
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
Click to expand...
Click to collapse
I am having the same problem. Unfortunately, I have not gotten any answer. Sorry I couldn't help, but at least we're not alone.
same here, have had same issue with multiple dailies. do you think this is with twrp or cm12?
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Shakinghead said:
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Click to expand...
Click to collapse
How did you do it? I've tried to encrypt with 27/08/2015 nightly and I couldn't. It said encryption failed and I had to wipe it.
I'm using the 26/08 (UK date format) build - This is the one that broke Chrome. I just encrypted the phone using the settings. I've been trying every couple of weeks for sometime. In the past I get the CM logo and nothing happens. If I remove the battery then the phone boots OK...so clearly the encryption hadn't started. This time I left it and walked away. 30 mins later I went back to the phone and it was prompting for the encryption password after boot....So all good for me....except TWRP cannot decrypt the encrypted partitions...
I am using the D855 model.
I'm having similar issues. I was able to encrypt after installing the Resurrection Remix v5.5.5 but now TWRP shows internal storage as 0mb and throws out a bunch of mount errors. So can't backup or load anything new through TWRP now.
The only way I was able to change ROMs was to flash the stock ROM through the LG flashtool, thereby unrooting the phone and then starting the whole process from scratch. It's a big pain because everytime I do that I need to get admin approval to setup my work email and then need to encrypt again , which locks me into the existing ROM again!
Ughh!! Can't wait for a solution top this problem.
So my 5x went back from the repair, and i decided to install purenexus.
The stock rom was N 7.1.2, i tried to install twrp but it ask me for a password. i tried default_password, my pin, but it does nothing.
format userdata too.
I noticed that every time i boot to bootloader, it relocks itself, even with fastboot oem unlock, after a reboot of bootloader, it shows DEVICE STATE - locked.
Any idea to get rid of this "password "on twrp?
i tried also to roll back to marshmallow, 7.0 and 7.1 actually, but it doest nothing.
Bootloader:
Variant ; Bullhead LGH971 16gb
HW version 1.0
Bootloader version bhz11h
baseband version m8994f-2.6.36.2.20
secure boot enabled
Just follow this guide and your problems will be solved: https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
vibo2013 said:
Just follow this guide and your problems will be solved: https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
Click to expand...
Click to collapse
I finded this guide and retried the flash. Magically TWRP stopped "format" the data and i was able to flash the latest build of PureNexus.
Now all seems to run fine
Happens with Fulmics only.
I used this phone with fulmics for a year or longer.
Recently I flashed this rom https://forum.xda-developers.com/lg-g3/orig-development/rom-pixel-g3-aosp-t3571499/page70
I then encrypted the phone. I don't recall entering a pin or being asked for a password. The phone showed as encrypted.
I then attempted to flash Fulmics again but got
"enter password to unlock 30 attempts remaining" screen.
I reflashed the pixel g3 ROM again successfully. Phone shows as unencrypted and boots.
Why did this happen?
Do I need to do anything prior to flashing a different ROM?
I did format, reset, wipe, etc
I use a Linux computer so it'd be useful to use Linux tools if needed, but I could also get to a windows computer if necessary.
it was an ebay refurbished phone with stock rom unencrypted. I then flashed fulmics and used it for a long time. I never encrypted and was never asked for passwords.
Hey there,
so I am kinda confused here. I've just flashed TWRP and LineageOS onto my Motorola Moto G5S. Now when I want to install Magisk to get root access and therefore boot into TWRP it prompts me with a password entering screen. Despite entering my correct passwordd (Also tried it with a pattern lock) it only says that the decrypt fails and the password would be wrong. Unfortunately I cannot try an older version of TWRP or Android because my main phone died recently and I don't want to use my data completely.
I hope someone can help me and I'll thank y'all in advance.
Booting TWRP from fastboot was giving error so i flashed the stock recovery but now files show encrypted. I dont want to lose them what could i do??
I dont know why they are encrypted as i have read about dm verity, forceencrypt, vbmeta, android 11.. im clueless yet. I have seen a video of someone fixing the problem of encrypted files showing on different model and custom ROM but i dont know whether its the same scenario (i have stock MIUI 12 and cannot boot into it) . Worth to mention i didnt disable the unlock pin before flashing (also tried re-flash other recoveries but none asks pin).