| T42 | <Teleg3_7> I've updated it, following the instructions at https://t.me/sailfishos_porters/202422. Here are the results from the server: | 00:19 |
|---|---|---|
| T42 | <Teleg3_7> git show | 00:19 |
| T42 | <Teleg3_7> commit c67fe5b47b81714c1338c39d5d2547f528933b15 (HEAD) | 00:19 |
| T42 | <Teleg3_7> Merge: fb8e476 0c68433 | 00:19 |
| T42 | <Teleg3_7> Author: Matti Lehtimäki <matti.lehtimaki@jolla.com> | 00:19 |
| T42 | <Teleg3_7> Date: Tue Mar 3 17:42:21 2026 +0200 | 00:19 |
| T42 | <Teleg3_7> | 00:19 |
| T42 | <Teleg3_7> I once ran “rpm/dhd/helpers/build_packages.sh --version” using pulseaudio-modules-droid* for pulseaudio-17, and it worked without errors. However, since this version has already been released, I recently tried rebuilding the RPM from scratch again. When I built the “version” section, it resulted in an error when using pulseaudio-modules-droid* for pulseaudio-17, so I reverted to the version I had built myself. I’m not sure what cau | 00:19 |
| T42 | <Teleg3_7> | 00:19 |
| T42 | <Teleg3_7> Based on the new suggestion, I’ll try updating again using the checkout 41cd1d9dbe6f644c98478705a4d96e9eb3fe0a90 (Commits on Jun 11, 2026). (edited) (re @elros34: did you update droid...) | 00:19 |
| *** n2klb_ is now known as n2klb | 01:15 | |
| T42 | <elros34> @Teleg3_7 but what error you got when building? | 06:41 |
| T42 | <elros34> @Mattia990 if you are brave try 'fastboot oem ramdump enable' but I have no idea whether your device support it or how it works | 07:50 |
| T42 | <Mattia990> I just tried but I got unknown command (re @elros34: @Mattia990 if you ar...) | 08:40 |
| T42 | <Mattia990> I tried with skip_initramfs patch but nothing (re @SailfishFreenodeIRCBridgeBot: <mal>@Mattia990 look...) | 08:40 |
| T42 | <Mattia990> I flashed also dtbo.img and tried with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (extracted from lineage) with no success | 08:41 |
| T42 | <elros34> btw have you tried lineage 18? | 08:42 |
| T42 | <elros34> do you have it flashed now? | 08:42 |
| T42 | <Mattia990> I have flashed lineage 18.1, it goes to lineage boot animation and after a while it reboots to recovery | 08:42 |
| T42 | <Mattia990> /data is populated so probably it is a rom problem | 08:43 |
| T42 | <elros34> so why do even try built sailfish on top on lineage 18 if you have not got working lineage? | 08:43 |
| T42 | <elros34> get "working" lineage's boot.img and repack it -> works? then get "wroking" lineage's kernel and assemble it together with hybris-boot's initramfs to new boot.img and try that. If that doesn't work try to add init=/init to cmdline | 08:55 |
| T42 | <elros34> make sure you still have this sleep 30 in init script | 08:56 |
| T42 | <Mattia990> I'm not able to boot lineage 18.1, I tried 3 different versions i found in Internet (as my device isn't supported officially) | 09:34 |
| T42 | <Mattia990> I found the lineage 19.1 to successfully boot (https://xdaforums.com/t/rom-sv2-unofficial-lineageos-19-1-for-mi-9-cepheus.4465175/) | 09:34 |
| T42 | <Mattia990> Should I try with this? Is lineage os 19.1 supported by hybris and sailfish then? | 09:34 |
| T42 | <Mattia990> There is this note written in the xda post, I don't understand if it just talk about dtbo and vbmeta or something different | 09:34 |
| T42 | <Mattia990> NOTE: Any other recovery is not supported, only Lineage Recovery will work | 09:34 |
| T42 | <Mattia990> NOTE2: This ROM uses FBEv2, any other recovery won't be able to properly format data making Android unbootable, also forget about any sort of decryption | 09:34 |
| T42 | <Mattia990> Seriously, just don't use any other recovery | 09:34 |
| T42 | <Mattia990> NOTE3: FORGET ABOUT CUSTOM KERNELS, THEY WON'T BOOT | 09:34 |
| T42 | <elros34> I guess you can first try with lineage-18 you have. At least it doesn't reboots straight to fastboot right. | 09:36 |
| T42 | <elros34> FBE file based encrytpion? We format /data for sailfish to remove that so this is not very important but can explain your issue with booting lineage-18 | 09:37 |
| T42 | <elros34> there is no hybris-19 I guess nobody needed it | 09:39 |
| T42 | <elros34> this boot image https://lineage.sebaubuntu.dev/cepheus/20220706/ looks sane. Have ramdisk, header v2 so good start point | 09:41 |
| T42 | <elros34> if you still have lineage check /proc/cmdline on it | 09:45 |
| T42 | <Mattia990> So the plan is to unpack that boot image and replace the ramdisk with hybris' one? (re @elros34: if you still have li...) | 09:54 |
| T42 | <elros34> yeah but try with hybris-18 first | 09:55 |
| T42 | <Mattia990> From what I remember lineage 18.1 boot image haven't ramdisk inside it (re @elros34: yeah but try with hy...) | 09:56 |
| T42 | <elros34> yeah but I guess you can add it | 09:56 |
| T42 | <elros34> even in lineage 22 kernel still handle skip_initramfs (and mess with it even more) so I guess bootloader is old and adds it to cmdline. WOuld be nice to confirm it with lineage's /proc/cmdline. https://github.com/xiaomi-sm8150-devs/android_kernel_xiaomi_sm8150/commits/lineage-22.2. | 09:58 |
| T42 | <Mattia990> I installed magisk on the lineage os 19.1 and extracted the cmdline from lineage booted | 10:25 |
| T42 | <Mattia990> www.pastebin.com/gmYEAe1B | 10:25 |
| T42 | <Mattia990> Like you said before there is the init=/init (re @elros34: get "working" lineag...) | 10:26 |
| T42 | <Mattia990> There is also want_initramfs option | 10:28 |
| T42 | <Mattia990> There is also want_initramfs option and rootwait (edited) | 10:28 |
| T42 | <elros34> yeah so you should have this 2 commits init: Add CONFIG_INITRAMFS_IGNORE_SKIP_FLAG (https://github.com/xiaomi-sm8150-devs/android_kernel_xiaomi_sm8150/commit/936f0959715c7510b35df48b2e7f2aaeffe85cfb) and arch: arm64: configs: xiaomi: Enable CONFIG_INITRAMFS_IGNORE_SKIP_FLAG (https://github.com/xiaomi-sm8150-devs/android_kernel_xiaomi_sm8150/commit/f2a065a377ad3d25953a9d156a129c10ac1b7c3b) | 10:30 |
| T42 | <Mattia990> Then should I add something to cmdline or add the do_skipinitramfs fix as hadk hot? (re @elros34: yeah so you should h...) | 10:32 |
| T42 | <elros34> you can't add anything to cmdline. You could use that fix from hadk but if something was tested then better use that 2 commits I have linked | 10:33 |
| T42 | <elros34> btw do you use android_kernel_xiaomi_sm8150 or android_kernel_xiaomi_sm8150-legacy which is linked in xda thread? | 10:34 |
| T42 | <Mattia990> I'm actually using the one that is not legacy (re @elros34: btw do you use andro...) | 10:34 |
| T42 | <elros34> in legacy one these commits are included but it also have only v20 branch so it's little mess | 10:36 |
| T42 | <Mattia990> I will try to revert my skipinitramfs change and add the two commits you sent me | 10:38 |
| T42 | <Mattia990> Thank you for the support! (re @elros34: in legacy one these ...) | 10:38 |
| T42 | <Teleg3_7> An error occurred when running the command: sfossdk sh -c “rpm/dhd/helpers/build_packages.sh --version” Some packages need to be installed. After I tried installing those packages, there were two that couldn’t be installed. The `droid-config-pulseaudio-settings` package requires the `pulseaudio-modules-droid` package to be installed first, but when I tried installing `pulseaudio-modules-droid`, I got the following error: " | 13:11 |
| T42 | <Teleg3_7> *Problem: nothing provides ‘**libpulsecommon-17.0.so**()(64bit)’ needed by the pulseaudio-modules-droid-14.2.106-1.6.1.bso.aarch64* package to be installed | 13:11 |
| T42 | <Teleg3_7> Solution 1: Do not install pulseaudio-modules-droid-14.2.106-1.6.1.bso.aarch64 | 13:11 |
| T42 | <Teleg3_7> Solution 2: Force the installation of pulseaudio-modules-droid-14.2.106-1.6.1.bso.aarch64 by ignoring some of its dependencies | 13:11 |
| T42 | <Teleg3_7> To avoid errors, I first reverted to the pulseaudio-modules-droid package built locally. After successfully installing those two packages, I then built the “version” section. After that, I replaced the pulseaudio-modules-droid* files with support for pulseaudio-17.0.0 (re @elros34: @Teleg3_7 but what e...) | 13:11 |
| T42 | <elros34> did you update target to 5.1? | 13:12 |
| T42 | <the_hiktor> Telnet freeze after 2 seconds | 13:16 |
| T42 | <the_hiktor> https://paste.opensuse.org/pastes/2536a4a71907 | 13:16 |
| T42 | <Teleg3_7> Yes, I changed it in the variables that are set every time I log into the shell: | 13:18 |
| T42 | <Teleg3_7> export SFOSSDK="$PLATFORM_SDK_ROOT/sdks/sfossdk" | 13:18 |
| T42 | <Teleg3_7> export UBUNTU=$PLATFORM_SDK_ROOT/sdks/ubuntu | 13:18 |
| T42 | <Teleg3_7> export RELEASE=5.1.0.11 | 13:18 |
| T42 | <Teleg3_7> export EXTRA_NAME=-lineage-20.0 | 13:18 |
| T42 | <Teleg3_7> export TOOLING_RELEASE="5.0.0.62" | 13:18 |
| T42 | <Teleg3_7> But I see that the release version appears when I run the command: | 13:18 |
| T42 | <Teleg3_7> export EXTRA_NAME=-lineage-20.0 | 13:18 |
| T42 | <Teleg3_7> rpm/dhd/helpers/build_packages.sh --mic (re @elros34: did you update targe...) | 13:18 |
| T42 | <elros34> no, you need to update sdk target/tooling | 13:18 |
| T42 | <elros34> the one you install https://hadk.sailfishos.org/build-env/. I can see there is 5.1 one available now | 13:20 |
| T42 | <Teleg3_7> OK, I just checked https://releases.sailfishos.org/sdk/targets/ | 13:21 |
| T42 | <Teleg3_7> There's something new for version 5.1 | 13:21 |
| T42 | <elros34> even without new tarballs you can also use ssu re/zypper ref/dup in target and tooling | 13:22 |
| T42 | <Mattia990> I tried with that two commits you sent me but nothing, it reboots instantly like before. I tried also with boot header version 0 and 1 | 13:38 |
| T42 | <Mattia990> I checked the output defconfig in order to see if what I put was correctly compiled and yes, it is | 13:38 |
| T42 | <Mattia990> I enabled also pstore in order to see kernel panics but /proc/last_kmsg is not there, probably it is crashing even before or i don't know, a secure boot fail ? | 13:38 |
| T42 | <Mattia990> I think I should give up with this version of lineage (re @elros34: in legacy one these ...) | 13:38 |
| T42 | <elros34> just try that lineaege19 boot.img see if you can include hybris initramfs ang get something. | 13:41 |
| T42 | <Mattia990> Tried but it goes immediately to fastboot like hybris-boot (re @elros34: just try that lineae...) | 14:11 |
| T42 | <elros34> did you test first with simple unpack/ pack lineageos 19 boot.img to make sure you use right commands? | 14:12 |
| T42 | <Mattia990> Mmm, i didn't try and effectively it isn't working | 14:16 |
| T42 | <Mattia990> Something different is the .img size, 128mb the extracted one and 18.4 the new one | 14:16 |
| T42 | <elros34> but does it boot? | 14:17 |
| T42 | <Mattia990> No, it doesn't | 14:17 |
| T42 | <elros34> compare with unpack_boot.img | 14:17 |
| T42 | <elros34> what command do you use to make abootimg? | 14:19 |
| T42 | <Mattia990> I was doing the wrong commands | 14:43 |
| T42 | <Mattia990> Doing that now i have telnet | 14:43 |
| T42 | <elros34> great! | 14:44 |
| T42 | <Mattia990> It is working | 14:44 |
| T42 | <Mattia990> But for sure if I upload the sailfish files into /data it will not work right? | 14:44 |
| T42 | <Mattia990> Because of missing kernel configs | 14:44 |
| T42 | <elros34> yeah but now you have known working abootimg | 14:45 |
| T42 | <Mattia990> Omg, now I have replaced also the kernel and it is still booting to telnet | 14:49 |
| T42 | <Mattia990> So probably there is something wrong with boot image generation ? | 14:50 |
| T42 | <elros34> could be | 14:50 |
| T42 | <Mattia990> I do some stuff, I connected via telnet, extracted the bz2 into /data/.stowaways/sailfishos | 15:59 |
| T42 | <Mattia990> Now, when i reboot after a while the pc shows that the phone is connected but I can't interact using telnet and then after some time it reboots | 15:59 |
| T42 | <Mattia990> The log i extracted is this: www.pastebin.com/csnxJjU8 | 15:59 |
| T42 | <Mattia990> Can it be related to the init*usb*.rc written in the documentation? | 15:59 |
| T42 | <elros34> probably not. use init_enter_debug2, enable journal persistent logging and get journal | 16:33 |
| T42 | <Mattia990> Here's the journal: www.pastebin.com/W2WDb8cQ (re @elros34: probably not. use in...) | 17:05 |
| T42 | <Mattia990> Seems related to rc files | 17:06 |
| T42 | <Mattia990> And /product and /system_ext | 17:06 |
| T42 | <elros34> metadata fixup-mountpoints is wrong. The real issue is: his device does not support updatable APEX. Exiting. There is patch in hadk-hot for it but it's know to fail for many, it will probably still need some work with linker configuration | 17:09 |
| T42 | <Mattia990> Do you mean this? | 17:13 |
| T42 | <Mattia990> https://sailfishos.wiki/link/20#bkmrk-leads-to-apexd-boots (re @elros34: metadata fixup-mount...) | 17:13 |
| T42 | <elros34> no few lines lower about apexes | 17:14 |
| T42 | <Mattia990> This? | 17:15 |
| T42 | <Mattia990> https://sailfishos.wiki/link/20#bkmrk-leads-to-apexd-boots (re @elros34: no few lines lower a...) | 17:15 |
| T42 | <elros34> edited so it should be clear nnow | 17:17 |
| T42 | <Mattia990> I'm still getting the same apex error, I applied the patch linked in the hadk hot | 22:33 |
| T42 | <Mattia990> Are there other things to do? | 22:33 |
| T42 | <elros34> did you build hybris-hal/droid-hal? | 22:58 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!