I have a problem with the new upgrade versions of e on the Galaxy S8. After upgrading, I need to format the storage. After that, the system starts in "factory condition. When I want to set up a PIN and fingerprint, the device says that a PN is already set up, I should restart the device and identify myself with the PIN. Then the game starts all over again. If I want to encrypt the device, it crashes into a boot loop.
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
seems to be the same as Cannot set unlock pattern or pin on samsung S8 after fresh install ?
Well, I wonder why the upgrade ensures that the device is basically rendered unusable (except for a detour via original Samsung software). That you can fix everything somehow -nice, but a clean upgrade looks different, doesn’t it? Since you can’t even open the bootloader in the settings under /e/, I couldn’t even flash TWRP, because with that I could have recreated the filesystem of all partitions and achieved the same effect as via the stockrom. Absolutely unsatisfactory!
yes, to put it midly.
To go back to your initial post - being prompted to factory reset after an upgrade can come up with repeatingly failed boot attempts. There can be multiple reasons, but one often posted to the forum is a lack of space: did you have any warnings or know you had little space left on the device?
As to “screen lock has already changed” there are a few more posts, one being:
Did you have a fingerprint registered?
What was the source and target version in the Update? (I’d guess target was e-2.7-s-20250109460371-official-dreamlte)
There was enough space on the device.
I gave up trying to install the upgrade.
Now using Lineage OS.
I did this following step …
Hmm, I don’t really see what’s supposed to make the difference.
In TWRP I would have the option of recreating the file system of the system partition. I suspect the error is there.
Simply formatting does nothing.
I have tried this several times.
And I can no longer get TWRP on the device because I can’t find an option to unlock the bootloader in /e/ OS version 2.21, which is still running on the device.
Translated with DeepL.com (free version)
Well, the difference between LineageOS and /e/OS is well known.
Whether LineageOS or /e/OS 2.21 is running on your Galaxy S8 is not clear to me.
Whether LineageOS or /e/OS 2.21 is running on your Galaxy S8 is not clear to me.
I expressed myself in a misleading way.
The S8 was and is a test device.
Always with the option that /e/ will become the system I use most often.
With the version jump and the associated problems, that is off the table for now.
I use the Lineage OS on a Galaxy A52s.
I experienced something interesting today during further testing.
I had installed the original /e/ via TWRP, which was replaced by /e/'s own recovery during the first update.
Re-flashing TWRP was impossible because the bootloader is obviously locked. (TWRP offers the option to recreate the file system)
Now I used the “factory settings” option under /e/ 2.22 in the hope that all encryption and PIN will then be deleted. And to my surprise, TWRP is now active again as recovery.
So I’ll keep trying.
you are talking about “e-2.21” or “e-2.22”, but latest is only “e-2.8”…
what do you mean exactlly ?
I mean the last /e/ before the version jump to 2.6.
“e-2.2-r” → “e-2.6.3-s”, now “e-2.8-s”
Even recreating the file system (my assumption was that the existing encryption of the “old” file system was causing the above-mentioned error) didn’t help.
It is therefore neither possible to create a fingerprint to unlock it nor to encrypt the file system.
The latter leads to a boot loop.
The only way to get out of this is through recovery and a factory reset…
After a tough battle (flashing a stock ROM to factory settings from the stock ROM), multiple factory resets under Android Pie, and re-flashing TWRP, flashing /e/, a PIN is requested on the first boot (?).
I hadn’t assigned one in the stock Android?
So I went back into recovery, which was then the one from /e/, another factory reset (the fourth in total!).
The installation that was then carried out (2.8) then presented no more errors when assigning the PIN and setting up the fingerprints!