[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [OTA][SODP]

Search This thread

bamdadkhan

Senior Member
Oct 7, 2013
95
10
umm i really don't want to nag but in the latest (jun 13th) update signature spoofing got turned off? is there any chance you could re-enable it?
 
umm i really don't want to nag but in the latest (jun 13th) update signature spoofing got turned off? is there any chance you could re-enable it?
It should be active, but as I've switched to a whole new build structure, it could slipped through - could you retest with https://gitlab.simonmicro.de/androi...obs/7529/artifacts/download?file_type=archive ? As it is the newest build and should contain all latest patches.

umm i really don't want to nag
No problem - after all I'm sorry for all inconveniences and I'm not able to test all features for a new release, so I'm happy when someone notices any problems and reports them!
 
  • Like
Reactions: bamdadkhan

bamdadkhan

Senior Member
Oct 7, 2013
95
10
It should be active, but as I've switched to a whole new build structure, it could slipped through - could you retest with https://gitlab.simonmicro.de/androi...obs/7529/artifacts/download?file_type=archive ? As it is the newest build and should contain all latest patches.

sadly, it still doesn't work:

2021-06-14 11.15.39 pm.jpg


i don't know what is the problem really because it says it supports spoofing but then it does not work. i didn't change anything, and even tried reinstalling microg.

EDIT: upon further investigation the problem seems to be that i somehow lost root : ( should i flash the stock lineage root zip again or does this have something to do with your build?
 

bamdadkhan

Senior Member
Oct 7, 2013
95
10
okay so flashing magisk back fixed the root issue, but the signature spoofing is still off.

EDIT: you probably already know, but maybe this helps: https://github.com/microg/GmsCore/wiki/Signature-Spoofing

according to this there are some ROMs where this is implemented as an additional per-app permission setting or a global one in developer options. maybe the functionality is there in newer lineage OS builds but the GUI part isn't? i'm just guessing here, i'm not a developer.

EDIT2: i reinstalled the 06-09 OTA and this fixed my problems immediately. please reply if you have a new build available and i'll try to test ASAP.
 
Last edited:
no, i went back to an earlier one. please see the screenshot above for what happens on the latest build. really weird.
CONFIRMED - I have somehow messed up the local_manifests to not include my patched frameworks base. I'll fix, rebuild and report back ASAP. Sorry for this - the whole time I assumed I messed up the patch itself...

EDIT: I forgot to push it. That's embarrassing...
 
  • Like
Reactions: bamdadkhan
Yes and no. Is it still my daily-driver? Yes. Have I any time to fix the current OTA builds? No. Any time to port to LOS 18+? Also no. So, I promise that I will update the post when I intent to not maintain this port anymore (and then also switch my daily-driver), but for now there also won't be any updates, as something somewhere upstream broke again...

A bigger problem is that I do not want to break anything with future updates (sjll had some great additions, but they would need a reformatted data partition) and therefore also have to go that extra step of ensuring this - which take even more time.

So yeah. This is the status now... As promised: When I give this port up, you will be notified.
 

bamdadkhan

Senior Member
Oct 7, 2013
95
10
thanks for the detailed reply. i am also using your ROM as a daily driver so i will wait patiently. also if you need a beta tester i'm here. i can always use my work phone for emergencies and i have backups.. : )
 

bamdadkhan

Senior Member
Oct 7, 2013
95
10
applying the latest update results in a bootloop early in the boot process.. i'm trying to reinstall the nov 8 one.

---

EDIT: tried installing it from recovery to both slot a and b, but no joy. it doesn't even get to the bootanimation, freezes on 'SONY'. fml.

---

EDIT2: tried doing the install process with all the images again, flashed the OEM update to slot a and b, no joy. tried flashing TWRP (because it doesn't suck ass like lineage's crap recovery) and seeing what's up, but i can't decrypt my /data even with the pattern>password from here: https://twrp.me/faq/openrecoveryscript.html

so at this point i have no options but to format my /data without a backup (again, because lineage recovery is useless) and this means i might as well install sailfish or something.. : (

tl;dr i don't blame you Simonmicro or the lineage guys (only for not including TWRP by default), but ppl should really be careful with the latest update, especially if you use magisk too, because i have a feeling its after-update script is what's responsible for this mess..
 
Last edited:
FML - the update is indeed broken. But for me the system boot up fine an then crashes after logging in for the first time - meaning something with the encryption causes the kernel to panic. Classic. If you get stuck during the boot phase you may need to flash opengapps again (in case you used it before). I'll pull the latest update and hope the upstream get's this under control with the next releases :)
 

bamdadkhan

Senior Member
Oct 7, 2013
95
10
hmm well i wasn't really using gapps, so that wouldn't have helped. as i've said, this is expected. currently i've lost all my data so i'll try Sjll's stock-based (i guess, up until now i thought everything is SODP-based) work, but i'll probably end up here again : )

just one odd question, is it possible to strip lineage's awful recovery from the OTA updates? that way TWRP wouldn't be overwritten and i could have proper backups and decrypt /data in recovery.. or would that potentially break even more stuff?
 
Well, it also affects me - and I'm DD this build. I am very f*ed, as my latest backup is from the 2021-10-03... I guess I've also lost some 2FAs... Whatever: This evening I will try to figure out what went wrong with some new engineering builds, hopefully the new kernel did not wipe the encryption keys from the keymaster... Hopefully. In case I'm unable to recover anything I have to think if it still worth weekly building this... Well, well...

F @bamdadkhan
 
Well... The kernel of the current builds triggers a double free call on something inside the EXT4 filesystem - as my system only crashes on first login I assume something is really broken inside the decryption routines... Which is very, very bad... I'll try to use an other version of the kernel, but I guess all data is doomed at this point.

And regarding the Lineage Recovery: I could strip it, but won't be able to include any replacement (I have currently no time to integrate or even port the TWRP fork for SODP)... So, I'll let it be as it is.
 
  • Like
Reactions: Meloferz
"FIXED" IT! I was able to boot my device using an older kernel version (adf2926e25e2a7303256e6b4431244289fb09940) - it seems like newer kernel versions have a bug inside the EXT4 filesystem driver, which causes the system to panic during decryption! I'll try to recompile my engineering build as userdebug and push it ASAP. Again, I'm very sorry for your data loss, but I hope this saves others from experiencing the same pain.
 
Last edited:
  • Like
Reactions: Meloferz

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Hey,

    as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.

    Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. 😄 I'll may post one more update, if I figure this one out.

    Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.

    See you next time,
    simonmicro
    2
    @Simonmicro
    Is it possible to add GCam support in your ROM?
    What exactly do you want? The default camera of the LOS is already used (Snap). We could migrate it to Snap2, but this would "downgrade" the feature set of the app (loosing the qrcode scanner). When you want the Google Camera you should be able to just install it using the Google Play Store or just download the respective apk and patch the config as already by @Sjll done for her version of the rom.
    I would like to not include it by default, as the main goal of LOS is to be clean from any Google stuff by default. Also this version of LOS tries to maximize the used Open-Source code, which would also interfere with this goal.
    2
    Yes and no. Is it still my daily-driver? Yes. Have I any time to fix the current OTA builds? No. Any time to port to LOS 18+? Also no. So, I promise that I will update the post when I intent to not maintain this port anymore (and then also switch my daily-driver), but for now there also won't be any updates, as something somewhere upstream broke again...

    A bigger problem is that I do not want to break anything with future updates (sjll had some great additions, but they would need a reformatted data partition) and therefore also have to go that extra step of ensuring this - which take even more time.

    So yeah. This is the status now... As promised: When I give this port up, you will be notified.
    2
    When I was installing this on Saturday, and I found this a bit unclear. I was able to install nano but not micro (micro installed, but the phone wouldn't boot and said it was bricked. Cue panic. Re-followed instructions w/nano instead and no problems).
    The OpenGApps sizes are pico < nano < micro and so on. I'm sure that pico works, as I use it myself and (based on the size) also nano should work. I know that micro+ is broken - but as I said, I do not want to increase the system image size more to keep the update (and packages) small...

    I freaked out a bit when the GPS wasn't working, but turns out my house just kills the signal. Was working fine for either maps, osm+ or Fito track when out from under the rock. The front camera is working for open camera but not the default camera as above.
    Hehe - same for me (gps). The cameras are still fun... Somewhere is some config screwed up... Also somebody (...) told me that the camera2 HALs are beyond messy...

    My fingerprint reader isn't working for Keepass2 to do quick unlocks (ironic, as that is actually the only thing that really needs it). It looks to be some sort of Java NullPointerException. Copying it proved somewhat difficult (can't just highlight it for some reason). Lmk if the details would be useful and I'll see if I can figure it out.
    Okay. Nett2Know... I'll add it to my issue list. Damn it...

    More that all that though, thanks to all the devs working on LineageOS, and particularly Simon and Martin for putting this together and Simon for maintaining, and Sjll for her work on this ROM and the 18.1 one! Its a real quality of life upgrade having this available. Y'all are awesome.
    On behalf of the whole team: Thank you 😄
    2
    anyone else having problems with the latest OTA? it boots then immediately shuts down. lineage recovery is a crapchute and says i need to reformat, but changing active slots - essentially going back to the may 10 release - works.

    i'd like to know if this is reproducible by anyone..
    Shoot, I can confirm! I had not yet restarted my phone for a while and therefore not noticed that yet. I'll take it down ASAP and look further into it (I'm also restoring an older version of it). Sh*t!