Yes. I tried that but ended up messing something. Got a data corrupt error and had to reset my phone anyway. Took a couple of hours to set up everything again and all is working fine now.
Did you do an upgrade from 16.0? If yes, did it work there?
On my phone, still on 16.0, it is working thanks to the first post in
Hi, thanks for your work as usual! :good:
Yes, when I try flashing Magisk (tested v20.4 and v20.3) I get a bootloop and have to reflash LineageOS.Hi there,
I tried to upgrade my Xperia XA2 (H4113) from Lineage OS 16.0 + MicroG to LineageOS 17.1 + Magisk but it didn't work for me. Flashing with LOS 17.1 is OK but when I try to flash Magisk 20.4, my phone won't boot anymore. It is stucked on the animated LOS logo.
Is anyone experiencing the same problem?
I tried on my second XA2, it's a H3113, flashed first LOS17.1, then Gapps nano, then Magisk (different tries with 20.4, 20.1 and 20.3).
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
for f in FILE_*; do unzip $f; done unzip boot.zip -d boot
From Twitter (for the sake of completeness):
https://twitter.com/LineageAndroid/status/1256821056100163584LineageOS @LineageAndroid · 3. Mai
Around 8PM PST on May 2nd, 2020 an attacker used a CVE in our saltstack master to gain access to our infrastructure.
We are able to verify that:
- Signing keys are unaffected.
- Builds are unaffected.
- Source code is unaffected.
See http://status.lineageos.org for more info.
haggertk · 7 days ago
Well, it looked like the compromise was fairly contained (more details will be forthcoming in a blog post), but burning it all to the ground and rebuilding, using backups where appropriate, is better than hoping you fully cleaned it all.
No, we're in the process of rebuilding pretty much everything except signing - web, mail, gerrit, buildbots, mirrorbits, etc.
If it's public and up right now it's because it was rebuilt.
https://www.reddit.com/user/haggertk/comments/haggertk · 3 days ago
Something completely independent from the salt exploitation happened somewhere around/just after April 23. The build trees on some of our build servers got "stuck" and weren't picking up submitted changes. Because the build date would be a lie, and it wasn't worth the effort to map which specific builds came off the "stuck" servers, we removed all builds for all devices after the apparent fault timeframe.
They aren't unsafe, just potentially with a codebase that is a few days older than what's represented in the build info.
If the concern is in any way related to the infra exploit, I will repeat what we publicly stated a week ago - no completed builds, source code, keys, or signing servers were compromised in any way.
Did we run into problems? Sure, if you call people's actual paying jobs and personal lives a problem.
Still in work, hoping for by the end of weekend, which is rather good for a "rebuild the entire world" kind of situation. If we miss the date, we miss the date.
It's important to note that development was only halted for less than two days. And let's be honest, the vast majority of devices haven't had anything truly important submitted in a way that really needs a new build.