Hardware Encryption fails in RR-OS but works in miui. - Xiaomi Redmi Note 5 Pro Questions & Answers

The encryption works on miui but fails on resurrection remix.
When I try to encrypt my device, it appears to start encryption but fails and it appears to have done a quick reboot. The whole process lasts about 30 seconds and the phone does not encrypt. Any idea what could be causing this? I have formatted my phone and done a clean flash. I am lost.
Any solutions to this problem?

Related

Custom roms cause bootloop upon restart

I have used custom roms in the past, mostly nameless and omni, using LVM storage, but there's one problem I'm experiencing with it and that happens for me just about every time now, and that is a bootloop. Every time I'm settled with a rom, so in the first hour I have rebooted it several times and no problems occured.
But after a few day's my battery will run out or get low and I switch batteries, that's where the bootloop happens.
The bootloop is unrecoverable, so dirty flashing the system again or factory wipe does not work, the system+data partition needs to be wiped to be able to use my phone again. I'm now on COS 2.1.5i (agianst my will) because on that rom, I don't encounter that issue..
My question is, what could cause this problem? Does anyone else experience this problem?

Force restart on any custom ROM

On any custom ROM I install as soon as I connect to a wifi network the phone will restart and will keep restarting as soon as it connects. This will happen during first setup and if I skip wifi setup and try later.
The only Roms that work are oxygen OS or Freedom OS. I am completing full wipes of everything except internal storage. I've used every package open Gapps has to offer to see if that was the issue.
Could this be a hardware issue? I don't know if there are logs anywhere that I can check to see what's happening.

Why encryption fails on this device (CM roms)?

Hello, i have tried with CM11, CM12.1 & CM13, with all of them, the encryption process fails : phone restart almost immediatly and things are same as before. Why does it fail? I'm trying to understand. Having this issue on other phone as well. Is this cause of recovery?

(klte) Samsung S5 & Encryption

Hello,
I had to reinstall LOS14.1 on my Samsung S5 recently and now I am unable to encrypt my phone without my effort resulting in a bootloop. Has anyone successfully encrypted their phone on an S5?
When I start the encryption the progress isn't shown, but I know this is a known issue. Therefore I typically force a reboot after a few hours to give my device sufficient time to fully encrypt the internal SD card. For CM this worked fine, however, Lineage fails to encrypt and breaks my system.
Any advice or throughts?
I am happy to provide log files if I know where to look for those.
I updated to the latest nightly and encryption worked like a charm this time with the progress bar showing, etc. No more bootloops or any other trouble. The entire process took about 10 minutes.
Sent from my Nexus 9 using Tapatalk

LOS Oreo 8.1 - Displaylock completely freezes phone

Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
furiify said:
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
Click to expand...
Click to collapse
Same problem
i delete /data/system/locksettings.db with twrp file manager to get rid of this problem but i can not lock because all lock types freezes.

Categories

Resources