[SOLVED] Encryption prompt on booting - Samsung Galaxy S7 Edge Questions and Answers

I'm running the LineageOS 7.1.2 (8th February 2019) and yesterday I saw there was an upgrade to TWRP-3.3.0-0 so I downloaded the image for S7 Edge (hero2lte) and rebooted to the existing TWRP custom recovery (3.2.3-0).
On entering TWRP I was not asked to unlock my encrypted device which was strange but I went ahead and flashed the new TWRP and rebooted. On booting system I was not asked to enter my pattern to unlock the encrypted partition on my phone, which was strange as I normally am. I checked `Settings > Security > Encryption` and it stated the device was encrypted. Tried rebooting a few times and not once was I prompted to enter my unlock pattern.
Has anyone else experienced this problem and/or have advice on how to restore the encryption prompting on booting (to either TWRP or system)? Without it the device is in effect not encrypted (although unlock pattern is required to start using the phone when booting system).

Turns out secure booting had somehow been disabled, how I don't know as I didn't do it.
This can be enabled under..
Code:
Settings > Security > Pattern > Screen Lock

Knox just sucks in general

Related

TWRP install fails (EU Version)

Hi everyone,
I'm trying to install TWRP on a fresh LG G6. I before updated the G6 to the latest available version.
So its currently running Android 8.0.0
Build Number OPR1.170623.032
Software version V20a-EUR-XX
I already unlocked the bootloader. Then I bootet into fastboot and tried to install twrp-3.2.1-0-h870. But after rebooting it with Volume Down + Power Key and reseting the device. I only see the TWRP splash screen after that the phone is booting the normal way up (and is reverting the bootloader).
I then installed (also via fastboot) twrp-3.1.1-0-h870. With this version I'm able to get into TWRP but this version is asking me for the password of the partition to decrypt. I didn't set up any encryption. So i tried "0000" --> no success. I also bootet andoird normaly and then setup a display lock screen with Pin 0000. But this code TWRP also refuses to use.
So I'm a little bit stranded here because I don't know what to do next.
Does anyone have a idea?
Greeting Uwe
You need to skip the password stage then format all. Type yes then it will work fine.
When it asks for password you can skip this stage
If I do so. I get
Formatting Data using make_ext4fs...
YOu may need to reboot recovery to be able tu usw /tada again.
Updating partition details...
Failed to mount '/system' (Device or resource busy)
... done
Click to expand...
Click to collapse
Then I hit reboot and the device is rebooting into Android and starting the first startassistant (so the format finally deleted something )
Then I power off the system and reboot with "Volume Down + Power" and I again only end in Factory reset data dialog
Ok next try same procedure than above. But not reboot into system instead only reboot into recovery --> pushing lineageos and the other zips onto the /sdcard/.
Wiping system, data, cache.
Flashing twrp via twrp, flashing lineageos, flashing gapps, flashing lineageos su package.
Reboot
And I'm greeted by Lineageos. Thanks for your support.

Android not asking me to decrypt user partition on boot

Hi, normally when you restart your phone, you have to enter your password/pin/pattern to unlock the phone, then it'll continue booting to your lockscreen. Normally your phone will not boot and stay at this screen until you enter your password. For whatever reason, my phone goes directly to the lock screen, which I have to enter my password there (I can't use fingerprint, it requires password regardless on first boot). Anyone know why this is happening?
LineageOS 15.1 (8.1.0)
OPM6.171019.030.H1
ElementalX 6.08
TWRP 3.2.3.0
Magisk 16.0
Found out why. I'm using an accessibility plugin for keepass2android, for its auto fill keyboard plugin. Enabling this removes the encryption features. See attached screenshot. Mods please close thread, thanks.

Can I enable my fingerprint lockscreen whitout enabling encryption

I like to regularly backup my data partition using TWRP. I noticed once I enable my fingerprint screen lock, TWRP is unable to access my data partition because Android 8.0 encrypts it from the moment I set a screen lock password (obligated when I enable fingerprint screen lock). For the moment my device in not encrypted and I don't want it to be encrypted, "preserve force encryption" is off in Magisk. Can I take the risk and enable my fingerprint screen lock now? Or will it encrypt my data partition again? I don't want my data partition to be encrypted as I like to access it out of Android. My bootloader is unlocked and my phone is a Samsung SM-G935F (Galaxy 7 edge) with Android 8.0 (TGPKernel.S7E.6.12.6).
ps: TWRP does not ask for a password after my Android device/partition is encrypted.
So does enabling a screen lock turn on encryption automatically and can I disable this behaviour?
Use the modded version of TWRP (the one on my signature, green one) for S7 edge.

Encrypting data causes the device bricks :(

Hi developers, i have an Asus Zenfone Max Pro M1.
The stock Pie ROM is very buggy, and i installed the new OFFICIAL DotOS May 16, TWRP 3.2.3-0.
But Encryption is not enabled by default because after flash TWRP, i wiped the DATA partition.
I have some worries about whether the data in / sdcard will be stolen easily by MTP if I don't encrypt it.
So I fully charged the phone, plugged in the charger and started encrypting the data of it.
the process is faster than 1min, and it restarted.
At the "to start Android, enter your PIN" screen, it don't let me do anythings, it automatic restart to the recovery.
But when TWRP appear, it always ask for "Pattern", but my lock screen password is using "PIN".
And when i reboot to system, it automatic restart to TWRP and TWRP ask for Pattern. LOOP!. I don't want to format Data against.
PLEASE HELP! I don't want to format Data against.

[Help] Bootloop after updating, usb debugging not enabled.

Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com

Categories

Resources