| budrz | trying to install SFOS on Google Pixel 3a XL and I still can't boot into SFOS | 00:33 |
|---|---|---|
| budrz | I unzipped the zip file; booted into LOS 18.1; did adb push sailfishos-bonito-release-4.4.0.68-my1.tar.bz2 /sdcard/; adb shell; su; mkdir -p /data/.stowaways/sailfishos; tar --numeric-owner -xvf /sdcard/sailfish*bz2 -C /data/.stowaways/sailfishos; exit; exit; adb reboot bootloader; fastboot flash boot hybris-boot.img; "Start" <power button> | 00:33 |
| mal | do you see the usb interface up when you try to boot it? does the device stay on or does it reboot after some time? | 00:41 |
| mal | I'll check your reply tomorrow | 00:51 |
| piggz_ | mal: video playback seems fixed on my pro1x :) | 08:39 |
| budrz | mal: the device reboots into fastboot and it gives a reason: no suitable slot available | 10:33 |
| budrz | there was one time where, after the google boot logo, a google "G" showed up with a loading bar underneath | 10:36 |
| budrz | it was seemingly indefinite and I have no idea how I got there | 10:37 |
| voidanix[m] | @mal would `rpm/dhd/helpers/build_packages.sh --build external/droidmedia --spec=$ANDROID_ROOT/external/droidmedia/rpm/droidmedia-devel.spec` and `rpm/dhd/helpers/build_packages.sh --mw=https://github.com/sailfishos/gst-droid` work? | 18:04 |
| voidanix[m] | to build gst-droid against the newer droidmedia-devel, that is | 18:05 |
| mal | I think it might, assuming that droidmedia-devel gets installed after build | 18:09 |
| mal | voidanix[m]: wondering which one is easier, that or build older droidmedia | 18:09 |
| voidanix[m] | i just tried using the above commands but it still wont play videos with this | 18:11 |
| voidanix[m] | according to the device, the correct package versions are installed | 18:11 |
| mal | maybe it didn't install droidmedia-devel before building gst-droid | 18:11 |
| voidanix[m] | the local droidmedia-devel is marked with `i+` according to `zypper pa -i` | 18:12 |
| voidanix[m] | the other one with a `v` | 18:12 |
| *** mint[m] is now known as mint[nowtheymintlgbt][m] | 18:19 | |
| budrz | mal: I did the installation of the stock rom and LOS 18.1, and now I get the google "G" logo again this time after following the steps I've mentioned | 18:27 |
| budrz | before the "G" logo, after the fastboot, the normal Google bootup would show up on the screen but reboots after a while in which a charging battery logo would appear | 18:31 |
| budrz | turning the phone, the Google bootup screen would appear as normal but then it would change into a "G" logo with a loading bar underneath it | 18:35 |
| budrz | Ok I think I might know what's happening. My LOS installation is in slot b and after flashing the hybris-boot with fastboot, it tries to load the OS but couldn't so it switches to slot a but slot a has no OS on it | 18:56 |
| budrz | hence the bootloop "G" logo | 18:57 |
| budrz | let me try to install using the steps in 10.3 (again) using TWRP | 18:59 |
| budrz | Installing LOS 18.1 was fine, of course, but after trying to install sfos zip, I get "Updater process ended with signal: 7" | 19:20 |
| T42 | <elros34> you need to really watch host dmesg after first fastboot flashing hybris-boot instead debugging by display logo | 19:33 |
| budrz | elros34: I tried that and I don't see any words containing Mer in the output of either dmesg or lsusb | 20:31 |
| T42 | <elros34> this is also useful, way more then watching screen. Did you read cpio related point in hadk-hot or generating logs section especially "bootloop" point? | 20:34 |
| budrz | elros34: I did not see that point on cpio or bootloops and it looks like I didn't have cpio installed in the HABUILD environment so I installed it | 20:41 |
| T42 | <elros34> yeah hadk is missing this little step to not make porting too easy | 20:42 |
| budrz | I guess that means I have to rebuild the kernel | 20:42 |
| mal | hadk pdf is a bit of a compromise, having all possible quirks etc there would make it quite difficult to use | 20:42 |
| T42 | <elros34> yeah no, this step is not really quirk, it is required to get anything working and it's quite hard to notice by new porters. I remember when new habuild was released some porters had strange issues and can' figure out what is wrong for quite a time until it becomes clear that ubuntu is missing cpiop | 20:45 |
| mal | which step was that again? | 20:47 |
| mal | I'll see if I can get it fixed somehow to next version | 20:48 |
| T42 | <elros34> would be great to have it. Just 'apt-get install cpio' in ubuntu-focal | 20:49 |
| mal | yeah, or mention of it in hadk pdf, of course having the binary in chroot would be easier | 20:50 |
| budrz | I recreated the kernel and the os zip file, and I redid the manual installation but still no luck | 22:55 |
| budrz | I have no log files as mentioned: https://etherpad.wikimedia.org/p/hadk-hot line 183 and 185 | 22:55 |
| budrz | so here is the output of abootimg: https://gitlab.com/budrzproj/sailfish-log-files/-/blob/main/abootimg.log | 22:56 |
| T42 | <elros34> ramdisk is there ~1MB so what excatly happen when you flash hybris-boot.img now: dmesg, reboot time | 23:07 |
| budrz | elros34: dmesg log at the time was this: https://gitlab.com/budrzproj/sailfish-log-files/-/blob/main/dmesg.log | 23:24 |
| budrz | it would sit for a while on the Google boot screen and then reboot twice until the charging battery icon appeared | 23:25 |
| budrz | reboot time I'd say maybe 10 - 20 seconds or so | 23:26 |
| T42 | <elros34> in that case initramfs is not reached or it fails at some point. About these dmesg log: which line is first boot after flasing and first reboot | 23:28 |
| budrz | that I don't recall exactly | 23:29 |
| budrz | I can try reflashing it and reupload it if you want | 23:30 |
| T42 | <elros34> so this log doesn't tell much. Still no idea what is happening at first boot. | 23:31 |
| T42 | <elros34> you can flash hybris-recovery.img instead hybris-boot (make sure you have build it after installing cpio). It will not try to switch to real rootfs | 23:34 |
| T42 | <elros34> This is lineage-18 right so there is no skip_initramfs added by botloader to kernel? | 23:35 |
| T42 | <elros34> but anyway please show your kernel sources | 23:36 |
| T42 | <elros34> btw do you flash kernel using fastboot or via twrp? | 23:39 |
| budrz | it is lineage os 18.1 and I flashed using fastboot. I even tried dd | 23:41 |
| budrz | what sources do you want to see? | 23:41 |
| T42 | <elros34> kernel | 23:41 |
| T42 | <elros34> better use fastboot instead dd to make sure you have right slot active | 23:42 |
| T42 | <elros34> there should be boot.im next to hybris-boot.img. IIRC it contains android initramfs, you can flash and see if there is any difference in host dmesg. As alst resort you just rever your defconfig changes and flash boot.img ( so basically same as lineage) | 23:50 |
| budrz | ok | 23:52 |
| budrz | it is taking a while to upload the kernel sources, so I may have to do this in the morning | 23:55 |
| T42 | <elros34> no, not like that. Fork existing sources then just add your commits. For know just show lineage sources url | 23:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!