[ROM][OFFICIAL] LineageOS 18.1 for castor/castor_windy

[creditabricole]

Hi _Linar_
Did you give the modified Magisk 22.1 (check post#12) a try ?

 

[_Linar_]

Hi _Linar_
Did you give the modified Magisk 22.1 (check post#12) a try ?

Installed via TWRP. Asks for updates to complete installation, then "Failed to process the package"

 

[creditabricole]

Ooops, my bad , sorry !
Apparently Magisk 22.1 doesn't work anymore with the latest official LoS 18.1
Check @Aqq123 post#151 that should fix your problem.
My apologies for my bad advice.

 

[creditabricole]

Hi everybody,
I applied @qsnc thread more than 1 year ago when Los18.1 for our tablet was still unofficial.
I'd like to update with the latest official revision so here here is my noob question:
Is it safe to simply dirty wipe and flash the official build directly from TWRP ?
Or do I have to restart it all: get back to stock and apply the all process (& so loose my data!)
Thank you for sharing your experience.

 

[Aqq123]

Is it safe to simply dirty wipe and flash the official build directly from TWRP ?
Or do I have to restart it all: get back to stock and apply the all process (& so loose my data!)

You can keep your data if you update the package signatures, see below:

Finally switched to the official build now (20221012). So far so good.

I used the migration.sh script to update keys so that I can keep my user data. Details if anyone's interested: https://wiki.lineageos.org/signing_builds

 

[_Linar_]

Ooops, my bad , sorry !
Apparently Magisk 22.1 doesn't work anymore with the latest official LoS 18.1
Check @Aqq123 post#151 that should fix your problem.
My apologies for my bad advice.

Magsik from post#151 causes a circular reload. The problem was solved by the subsequent manual installation of the latest version of Magsik from the official site.

 

[Aqq123]

Magsik from post#151 causes a circular reload. The problem was solved by the subsequent manual installation of the latest version of Magsik from the official site.

I'm the author. For the record, it does work fine, if applied to a clean partition. In your case there were probably some leftovers from the failed installation of Magisk 22.1 you attempted before. At least that was the cause in @pokazene_maslo's situation (post #158):

It works now! Wiping the /system partition and reinstalling the OS did the trick. I guess it didn't work previously because /system was already modified with Magisk-v22.1_mod_sony.zip installation.

Thank you very much!

Anyway, good to know the issue was addressed in Magisk, and that you got it sorted out. I think 23.0 is still the sweet spot though for this device, with less overhead than the newer versions and MagiskHide still built-in. That's just my personal opinion though.

 

[creditabricole]

You can keep your data if you update the package signatures, see below:

Hi @Aqq123,
This process is a bit beyond my skills . . .
I'm not sure about the purpose of this script: is that a way to tamper an unofficial build signature to make it "official" and so let the LoS updater do its job ? In other words, the goal would be to force a standard update, not an upgrade . . . ? (& so keep our data)

 

[Aqq123]

This process is a bit beyond my skills

That's the only way I know of. There should be a flashable ZIP with this script inside somewhere, if you don't want to run it yourself.

I'm not sure about the purpose of this script

Official LineageOS builds are signed with release keys.
Unofficial LineageOS builds are signed with test keys.

Database of installed packages, stored in the file /data/system/packages.xml, includes the public key (signature) for each package.

After a change from an unofficial to official release, the keys for system packages will no longer match.

Packages with mismatching signatures are removed from the database upon boot by the Package Manager.

Then the same system packages will be re-added but with different (correct) signatures.

So if you reboot directly after flashing, your system settings will be lost.

If you run the script instead first, it will change the keys in the package database to match those of the build you're switching to. This way no packages will be deleted upon boot due to signature mismatch, and all your settings will be preserved.

It only changes a single file on the /data partition, doesn't modify the system image in any way. If you're prepared to do a clean install (wipe the data partition) anyway, you might as well try it: you have nothing to lose.

 

[creditabricole]

Thank you very much for your detailed answers to my questions
I deeply agree with your conclusion: I have nothing to lose. It's worth to give it a try !
I'm a bit busy these days but I'll let you know when I get into it

 

[creditabricole]

Hi @Aqq123,
As promised, here is some feedback.
I followed your post#187 and I'm now running the latest official LoS18.1 build
Data+TWRP+root: everything is here. Absolutely no loss during update, great job !
One more time: thank youuuuuu !

 

[Rusty_Gunn]

My tablet was going a bit glitchy so I reflashed with the latest nightly but now chrome won't work. It is pretty much frozen (although periodically it will show life) and the tabs are unusable (see image). Tried flashing it again with a nano gapp package instead if pico and same issue. Both times did a complete wipe before flashing on lineageos. In hindsight the glichyness i was seeing before i flashed might of been a chrome issue. Thoughts?


edit:
loaded on an old version of chrome which fixed the freezing and tab issue. still have issues when games do the ad rolls between rounds (screen becomes unresponsive)

 

[Verity.]

Hello, I don't know if it's a bug in this rom or the issue is with gapps, but I have a problem with installing bigger apps from play store (1GB+) - it happens using open gapps and many other different providers. As I click "download" it usually immediately throws an error 'can't install this app' or somewhere in the area of 50% or 100% Sometimes apps do install when I clear google play data but it's kinda rare. Edit: It is related with app having OBB files

 

[N_L]

Since Magisk wouldn't install with lineage recovery I flashed twrp, but that just got me back to bootloop (but this time without going into twrp just restarts, before I had twrp and was trying to install with it still on and had to flash stock to get everything working). I flash lineage recovery, formated data and reinstalled lineage and it's working again but still don't have root. Gotta figure this part out now, I'm using the zip file from post 151 but no apk shows up when I boot :s

Edit: I think it's working, gonna setup the device and see, disregard my post