Is there a problem with encryption with LOS16?
On trying to encrypt a brand new install on a 3T it goes to the black encryption screen with green android logo and then just says Android is starting. Encryption doesn't happen but Magisk is removed.
Can anyone help?
Thanks
nimicitor said:
Is there a problem with encryption with LOS16?
On trying to encrypt a brand new install on a 3T it goes to the black encryption screen with green android logo and then just says Android is starting. Encryption doesn't happen but Magisk is removed.
Can anyone help?
Thanks
Click to expand...
Click to collapse
The same happens to me in Xiaomi Mi 8.
The encryption fails.
Same on Samsung Galaxy A3 (2017) with LOS 16.0 (McFy)
Same Issue JFLTEXX
Same issue with latest nightly
nimicitor said:
Is there a problem with encryption with LOS16?
On trying to encrypt a brand new install on a 3T it goes to the black encryption screen with green android logo and then just says Android is starting. Encryption doesn't happen but Magisk is removed.
Can anyone help?
Thanks
Click to expand...
Click to collapse
Similar problem on gts210vewifi (samsung tablet s2 9.7" wifi), type in password, get green robot, black screen and back at startup screen to type password to unlock. And still not encrypted. Using latest nightly.
Related issue: 2361 (on los gitlab)
Related
Hi,
I have a problem with my A5 2017 running official nougat with magisk. I can use my fingerprint to unlock my phone easily, however when I try using my PIN/model, when I enter the right code, it just freezes until screen goes off. This was a real problem when I had to restart my phone, and it was asking me my model and I could drax it but then the screen would freeze until it went black and it was still asking me my model, and freeze etc. So i erased data/cache, but I still have that problem.
Thanks in advance
my problem is similar to this. when i try to unlock the lock screen with my pin, pw or model it takes about 5 seconds before the phone is unlocked. when i use fingerprint its unlocked instant. my A5 2017 (7.0 nougat) is rooted with magisk too. perhabs this is the problem?
in my case the problem was Magisk. I flashed my OS completely new with this instructions ( https://forum.xda-developers.com/sa...ficial-nougat-release-download-guide-t3654413 )
then i root with supersu instead of magisk and now it works !
Yesterday I tried booting android p dp4 GSI build, I got from here http://telegra.ph/Android-P-on-Whyred-07-21 . I did as instructed there, it didn't boot, just got past mi bootlogo, Google animation and then into a screen with my mi id, lockscreen owner message, and a password block for a split second and then again booting back into twrp. (For some reason I couldn't use the previous miui beta I was using earlier, even after full flash couldn't got past setup screen, booted using a later miui beta build)
If anyone successfully booted into P dpi4 GSI, please tell me da wae ?
Hi,
After some hard work I finally got TWRP and LineageOS installed on my Galaxy A5. It now works properly except that when I try to turn it off, the screen becomes black for a few seconds and then it reboots.
Did anyone encountered this problem before? Do you have an idea of a possible fix?
gustavecoste said:
Hi,
After some hard work I finally got TWRP and LineageOS installed on my Galaxy A5. It now works properly except that when I try to turn it off, the screen becomes black for a few seconds and then it reboots.
Did anyone encountered this problem before? Do you have an idea of a possible fix?
Click to expand...
Click to collapse
Same problem here. Have you found a solution?
Hi,
Yes, I finally found a solution. The problem was that I was trying to install Lineage OS 14.1 (based on Android 7) on a phone where Android 8 was installed.
At that point, you have two solutions:
Install a stock version of Android 7 before flashing LineageOS
Find a version of LineageOS 15 that works on Galaxy A5.
I chose option 1 and it did work perfectly.
Thank you. I'll try that as soon as I can. (I will also choose option 1.)
When i try to install a stock version of Android 7 with Odin, it fails with this message on the phone in download mode : "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7, BINARY: 4". Any idea ?
Hi, I have problem with my Galaxy Tab 3 7.0 (SM-T210), I think it stucks in bootloop after giving password to decrypt device. There is TWRP and i have access to recovery but don't know what to do. I tried install system from backup and there is no effects. I see Samsung logo, next is field where i can input password and next i see Android (droid image) and it returns to Samsung logo. Anybody help?
Btw. sorry but English isn't my native
I got an miui 12.0.1.0.RCOINXM update after which phone started to randomly reboot, especially when there was some drop down notification or call.
So I decided to install custom rom. I tried to install Pixel Experience Recovery but that was giving "System is destroyed press power button to shutdown". I fixed it by flashing orange fox but using orange fox pixel experience got in boot loop. So I installed Pixel Experience Recovery from orange fox recovery and the used ADB to sideload pixel experience which worked and I setting up my phone but suddenly I get a notification and the phone reboots which is similar behavior to miui 12.0.1.0.RCOINXM. is there some thing else that I can change like kernel or something which can resolve this problem.
I am using PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip
pls help
PS : the phone remains in boot loop if not plugged in charging and idk why but fastboot logo didn't change to pixel experience's
GundamSierra said:
I got an miui 12.0.1.0.RCOINXM update after which phone started to randomly reboot, especially when there was some drop down notification or call.
So I decided to install custom rom. I tried to install Pixel Experience Recovery but that was giving "System is destroyed press power button to shutdown". I fixed it by flashing orange fox but using orange fox pixel experience got in boot loop. So I installed Pixel Experience Recovery from orange fox recovery and the used ADB to sideload pixel experience which worked and I setting up my phone but suddenly I get a notification and the phone reboots which is similar behavior to miui 12.0.1.0.RCOINXM. is there some thing else that I can change like kernel or something which can resolve this problem.
I am using PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip
pls help
PS : the phone remains in boot loop if not plugged in charging and idk why but fastboot logo didn't change to pixel experience's
Click to expand...
Click to collapse
PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip is for the original Redmi Note 8 (ginkgo)
Judging by your MIUI version (if i remember correctly the new Note 8 ships with MIUI 12.5), you are in the wrong forum, the original Note 8 forum is here.
OR
You have installed a Note 8 (ginkgo) rom to a Note 8 (2021) (biloba) witch is not compatible with the new note 8.
Thanks for reply Aninuscsalas but No my redmi note 8 is 2019 edition and even after install correct roms even downgrading the same issue persists
I think as my device is A partition only devices [Non-A/B] there might have been something wrong during the update process and that might have made some problems.
Here is my partition table can anyone pls confirm if this is Ok?[in attached]
GundamSierra said:
Thanks for reply Aninuscsalas but No my redmi note 8 is 2019 edition and even after install correct roms even downgrading the same issue persists
I think as my device is A partition only devices [Non-A/B] there might have been something wrong during the update process and that might have made some problems.
Here is my partition table can anyone pls confirm if this is Ok?[in attached]
Click to expand...
Click to collapse
Sorry i can't help. (I know almost nothing about phones.)
But if your phone is the 2019 version then you are in the wrong forum.
Maybe someone in that forum can help:
https://forum.xda-developers.com/c/redmi-note-8.9200/