SebastianoGaleazzo[m] | @mal @elros34 So great news (I hope)... I've been digging around with stock bootimg, los bootimg... And I noticed that they all have same size obviously (64.0mb) but hybris-boot has practically half of their size (24mb). Unpacking and repacking stock/los bootimg with unpack_bootimg.py and mkbootimg.py reduced their size to 24mb making them unflashable!!! Instead using "abootimg" when unpacking a file named | 08:40 |
---|---|---|
SebastianoGaleazzo[m] | "bootimg.cfg" is created and there it writes the boot.img size too, to be used while repacking the img. So I thought can it be due to wrong *.img file size not being applied during hybris-hal build and not being applied during manual unpacking/repacking using *.py scripts? | 08:40 |
SebastianoGaleazzo[m] | So I used "abootimg" to unpack hybris-boot.img and I changed the line "bootsize = 0x0178a000" (which is equal to 24682496 bytes = 24 mb) to "bootsize = 0x4000000" (equal to 67108864 bytes = 67 mb), then I flashed it and it just worked!!! | 08:40 |
T42 | <adampigg> Mal: how did the alsa update go? Are you using it for your native device? | 11:09 |
mal | @adampigg I have only tested that it builds so far, my own native ports don't have audio yet | 11:25 |
SebastianoGaleazzo[m] | For hybris-18.1 do we have to apply selinux related fixes described under hybris-17.1 section too? | 13:25 |
mal | yes, | 13:26 |
SebastianoGaleazzo[m] | Ok so that could be the cause about why device keeps bootlooping without last_kmsg or console-ramoops | 13:27 |
mal | how soon does it reboot? | 13:27 |
SebastianoGaleazzo[m] | very early... after 1-2 sec the boot logo has been showed up and then it stucks at the logo | 13:31 |
SebastianoGaleazzo[m] | i think when it stucks at logo it is trying to switch to the other slot | 13:31 |
SebastianoGaleazzo[m] | * i think that when it | 13:32 |
SebastianoGaleazzo[m] | * i think that when it, * at logo (after first early reboot) it is | 13:34 |
mal | do you see anything in host dmesg? | 13:37 |
mal | if you have usb cable connected | 13:37 |
SebastianoGaleazzo[m] | dmesg see it when in fastboot mode before starting but then it only detects it has been disconnected | 13:42 |
SebastianoGaleazzo[m] | * dmesg see it when in fastboot mode before starting but then it only detects it has been disconnected (running "sudo dmesg -wH"): | 13:43 |
SebastianoGaleazzo[m] | https://pastebin.com/wCg6Y1EH | 13:43 |
mal | so nothing about sailfish in there, does your device use some secure boot with verity | 13:43 |
SebastianoGaleazzo[m] | I check... But I didn't applied selinux fixes of hybris-17.1 section of hadk-faq yet... | 13:45 |
SebastianoGaleazzo[m] | Can it be because of this^? | 13:45 |
mal | usually it wouldn't be that fast reboot afaik | 13:48 |
SebastianoGaleazzo[m] | So since it has been launched with Andorid 9.0 it should have AVB 2.0: | 13:48 |
SebastianoGaleazzo[m] | https://source.android.com/docs/security/features/verifiedboot/avb | 13:48 |
mal | we usually disable verity stuff in kernel | 13:48 |
mal | SebastianoGaleazzo[m]: you said it's stuck at the boot logo, what did that mean? | 13:49 |
SebastianoGaleazzo[m] | After first early reboot it bootloop some times and then it stuck at boot logo without rebooting again... It should be treble feature that automatically switch to the other slot (in my case _b) to try booting from there | 13:51 |
SebastianoGaleazzo[m] | * After first early reboot it bootloop some times and then it stuck at boot logo without rebooting again... It should be treble feature that automatically switches to the other slot (in my case _b) to try booting from there | 13:52 |
SebastianoGaleazzo[m] | In fact when I force rebooting to booloader "fastboot getvar all" shows "currently slot: b" and not _a which is the slot from where it booted before | 13:53 |
SebastianoGaleazzo[m] | <mal> "so nothing about sailfish in..." <- Could be this one? | 13:54 |
SebastianoGaleazzo[m] | https://github.com/LineageOS/android_device_motorola_exynos9610-common/blob/ba6e28ee7abd16d8485dc6a750be606eea0e922a/BoardConfigCommon.mk#L147 | 13:54 |
mal | SebastianoGaleazzo[m]: wondering if you need to flash the dtbo.img also? | 13:57 |
mal | to proper partition | 13:57 |
SebastianoGaleazzo[m] | I flashed dtbo.img from lineageos base, do I have to flash hybris one in out/ folder? | 13:57 |
mal | quite likely those are the same if you used same sources | 13:58 |
SebastianoGaleazzo[m] | Checking with md5sum it gives two different hashes... | 13:59 |
SebastianoGaleazzo[m] | Even if they have same size | 14:00 |
SebastianoGaleazzo[m] | I flashed dtbo.img from out/ now I'm booting... Something has changed I think since until now it hasn't rebooted yet | 14:02 |
mal | anything in dmesg? | 14:03 |
SebastianoGaleazzo[m] | dmesg doesn't see it | 14:03 |
mal | also make sure you now booted from correct slot | 14:03 |
SebastianoGaleazzo[m] | I'm trying reflashing all to be sure... | 14:06 |
SebastianoGaleazzo[m] | Ok booting from _a slot it doesn't reboot now | 14:08 |
SebastianoGaleazzo[m] | it just stucks at boot logo and dmesg doesn't see it | 14:08 |
SebastianoGaleazzo[m] | * be sure... (hybris-boot.img with correct size, dtbo.img from out/ folder) | 14:14 |
SebastianoGaleazzo[m] | So after flashing dtbo -> first boot stuck at logo | 14:39 |
SebastianoGaleazzo[m] | Rebooting to bootloader and booting again -> early reboot a lot of times and then fall back to second slot booting system from slot _B | 14:39 |
SebastianoGaleazzo[m] | s/_B/_b/ | 14:39 |
SebastianoGaleazzo[m] | * So after flashing dtbo -> first boot stuck at logo | 14:39 |
SebastianoGaleazzo[m] | Rebooting to bootloader and booting again (from same slot) -> early reboot a lot of times and then fall back to second slot booting system from slot \_b | 14:39 |
SebastianoGaleazzo[m] | * So after flashing dtbo -> first boot stuck at logo without rebooting | 14:44 |
SebastianoGaleazzo[m] | Force rebooting to bootloader and booting again (from same slot) -> early reboot a lot of times and then fall back to second slot booting system from slot \_b | 14:44 |
*** Ischwitch is now known as Ingvix | 15:22 | |
T42 | <MonopolyPlayer> Hello! My vollaX just freezed on the select menu when pressed power button + vloume down. How can I boot to fastboot or recovery for example? | 16:32 |
SebastianoGaleazzo[m] | * So after flashing dtbo -> first boot stuck at logo without rebooting | 16:42 |
SebastianoGaleazzo[m] | Force rebooting to bootloader and booting again (from same slot) -> early reboot a lot of times and then fall back to second slot booting system from slot \_b | 16:42 |
piggz_ | spiiroin: where in mce, does it actually hit the kernel api to turn on the screen ... there is a lot of abstraction in that program! :D | 18:14 |
Thaodan | The community irc bridge might not work properly as my server provider is getting DDoSed right now. | 20:19 |
Thaodan | Everything is fine again. | 22:26 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!