Hello.
Since last week my S7 phone won’t start. I type in the password, the jumping E logo appears, and after a few minutes I’m back at the start with the phone asking for the password. The first time it happened, the phone finally started again after many trials. But now it’s in this loop and won’t start at all. I was one /e/OS update late.
Any idea on how to try and solve that?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
i tried the safe mode with no more success.
Are you reasonably confident of your backup of the phone?
Do you have installed an official or community build?
So you had a e-2.6.3-s-xxx build?
Are you able to boot into recovery?
If yes, before considering (destructive) Factory reset you could try
adb sideload e-2.6.3-s-xxx - xxx .zip
where e-2.6.3-s-xxx - xxx is a certain match with the previously running system.
Hi,
Thanks for your answer.
Except for my contacts and agenda, i’m reasonably not confident of the backup of my phone, at least not a recent one.
I bought the phone from the /e/ shop a few years back, so i suppose i have an official build, and yes it was 2.6 something.
I can boot in recovery, i will try adb sideload. Never did that before though.
So, from /e/ shop, yes it was official.
There should be little risk, this is the same task as a manual update. Loosely speaking, there is a clue in the name “sideload”; the new file is added alongside everything else but being an unchanged file it can result in a “repair” of system if something odd there is preventing boot. If it is not the desired fix nothing should be lost.
Hello,
thanks for your help, it worked, and I didn’t lose any data 
Hello,
Here i’m again with the same problem with e-2.9. Except this time I can’t do the adb sideload. My device appears as “unauthorised”. Yet I’m in recovery mode, I enabled ADB, and i’m in the apply update from ADB menu.
I tried finding a solution to this “unauthorised” message by looking on the internet, with no succes so far…
Any idea?
Are you referring to USB debugging? Do you know for certain if USB debugging was allowed before the failure?
I think you mean e-Recovery > Advanced > Enable ADB.
You might also try (same location) Mount system.
Hello,
Yes it’s exactly what I meant.
I tried Mount System, I got the same result
List of devices attached
ce0217127c72cc1d0c unauthorized
The most common cause of “Unauthorized” is that USB debugging is disallowed within Developer options and with modern encryption maybe you cannot avoid Factory reset. [1]
Again your decision on this will depend on the state of your backup.
Following Factory reset (all data lost), the phone may start normally if you are lucky, if not you could pick up the troubleshooting I offered last time and / or we can take a different path depends what you find.
Following Factory reset USB debugging is disallowed within Developer options for sure.
Search Settings > System > Developer options > USB debugging
If access to Developer options is required …
Settings > About Phone > Build Number or Version > Tap seven times
[1] Edit. Try the suggestion below first.
On this Samsung device modele s7, you should be abble to install or update /e/ without adb from the PC,
but from internal storage or SDcard using recovery.
Hello,
i tried to install from SD card, it said it was successful, but then it wouldn’t start either.
Factory reset worked tough, my last backup was from march, so it wasn’t so bad after all.
Except for Signal : i have the backup, but not the passphrase 