Project

General

Profile

Actions

Issue #1995

open

Boot in loop during encryption

Added by Christophe Moille about 4 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
01/29/2020
Due date:
% Done:

0%

Estimated time:
Resolution:
Device:
Galaxy S 3 (I9300)
Grant:
Type of work:
Bug tracker editions, Unknown

Description

I used to have replicant 6 on Galaxy SIII. I had problems a few months ago, stalled on replicant logo when booting
I reinstalled replicant, 2 times because of same bug after installed same applications than before. Always encrypted one.

The last time, i didn't encrypt installation and installed only a few application, that I thought that didn't bug.
Works like a charme since a few weeks
But I made the error to ask to encrypt the phone and since, it boot in loop =(

Do you know a workaround to be able to use it without reset it ?

Actions #1

Updated by _I3^ RELATIVISM almost 3 years ago

  • Type of work Bug tracker editions, Unknown added
Actions #2

Updated by Denis 'GNUtoo' Carikli almost 3 years ago

  • Which Replicant image was used? Some very old images had crash like that
  • It could also be related to issues with system application signatures somehow as there is 0 check on that when installing images when the device is encrypted (the issue is also present in LineageOS). So for instance when keeping around the data from Replicant 4.2 to Replicant 6, the installation of Replicant 6 will not abort and the device will not manage to boot after that without erasing the application data.
Actions

Also available in: Atom PDF