install custom rom based aosp if you don't install Disable DM Verity bootlop, if you install "Disable DM Verity" the fingerprint is gone and if the pattern lock is successful the pattern is successful but the pattern is tried continuously, why is that, bro? the data format is also done
Never had the problem with orangefox recovery.
Related
i am trying to flash twrp 3.0 on a samsung j500fn in odin, but when i press start, i get a msg on the phone:
custom recovery blocked by frp lock
At this time i havent anabled OEM unlock yet, is that the problem?
What can i do? I read stories of people flashing twrp and after that it won't boot anymore, with the same message?
sander815 said:
i am trying to flash twrp 3.0 on a samsung j500fn in odin, but when i press start, i get a msg on the phone:
custom recovery blocked by frp lock
At this time i havent anabled OEM unlock yet, is that the problem?
What can i do? I read stories of people flashing twrp and after that it won't boot anymore, with the same message?
Click to expand...
Click to collapse
You forgot to enable OEM unlock, now you have to flash stock rom using odin, and do it again, this time don't forget to enable OEM unlock, how are you going to mess around with your system, when you forgot to unlock bootloader when rooting?
no, i am still in download mode on the samsung. Flashing twrp just didn't work. Phone is still working ok. I am just getting this msg when i am trying to flash twrp with Odin.
/
You need to enable OEM unlock and than reflash TWRP in Odin disable auto rebot in option after finishing insert your baterry.
Phone is stuck at "encrypted for security password" screen even after full Data wipe
My s8 is with custom rom and kernel, I never touch/enable any storage encryption setting, no passcode lock setup on the phone, It happen after I wipe /data in twrp. It stuck at this screen after booted up, I don't have passcode setup on the phone. It still stuck at this screen even after I do Format Data, wipe /system /data /cache and clean re flash Rom, kernel, that used to work, the phone boot and build up dalvik cache but still end up at the password screen,
I google about this and find " the default password of AOSP defined as default_password in the cryptfs.c source file" enter default_password don't work as well
Any help is greatly appreciated!!!
I have resolve this by flash stock recovery via odin to do a factory wipe. It can boot up normally now, haha
or you can just "format data" in twrp
All,
I had flashed Elite ROM v4 and it was successful except messing up on MagiskSu where one application still detected the phone is rooted. To solve the problem, decided to flash it again without realizing OEM lock is off - forgotten to activate before start flash. Now, after wipe everything using TWRP,reboot to continue the flashing procedure, the phone is unable to boot into TWRP recovery and only able to boot to stock recovery and fastboot. Unfortunately the FRP is lock and I could not not flash TWRP again. Any advice?
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.
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