T42 | <eminarican> i was unable to flash zip file | 02:28 |
---|---|---|
T42 | <eminarican> so extracted rootfs to data/.stowaways | 02:28 |
T42 | <eminarican> and wrote hybris-boot.img to boot | 02:28 |
T42 | <eminarican> | 02:28 |
T42 | <eminarican> now it just bootloops every 1 minute | 02:28 |
T42 | <eminarican> | 02:28 |
T42 | <eminarican> seems like telnet is not running on device | 02:29 |
T42 | <eminarican> and there's nothing like "sample output" from pdf in dmesg | 02:29 |
T42 | <eminarican> | 02:29 |
T42 | <eminarican> tried to create dev/null symlink for ofono.service thru twrp but that didn't worked either | 02:29 |
T42 | <eminarican> (sorry if i'm asking too many questions D : it's my first time getting involved into such stuff) | 02:31 |
mal | most likely it can't setup usb | 02:34 |
mal | 1 minute sleep in init script happens in that case | 02:34 |
mal | can you check if you have these 3 configs in kernel defconfig https://github.com/mer-hybris/android_kernel_sony_msm/blob/hybris-sony-aosp/LA.UM.9.12.r1/arch/arm64/configs/aosp_lena_pdx213_defconfig#L932 | 02:35 |
T42 | <eminarican> lemme see | 02:35 |
T42 | <eminarican> nope i don't have those | 02:37 |
T42 | <eminarican> i'll add then try again | 02:37 |
mal | you only need to run "make hybris-boot" and then flash the new kernel image | 02:38 |
T42 | <eminarican> ty for tip ^^ | 02:38 |
T42 | <eminarican> it doesn't bootloop anymore and dmesg shows mer but | 03:02 |
T42 | <eminarican> | 03:02 |
T42 | <eminarican> node@3:~/Desktop$ sudo lsusb -v | grep iSerial iSerial 1 0000:00:14.5 iSerial 1 0000:00:13.2 iSerial 1 0000:00:13.0 iSerial 3 Mer iSerial 1 0000:00:12.2 iSerial 3 0ME00L1091413 iSerial 1 0000:00:12.0 iSerial 1 0000:00:10.1 iSerial 1 0000:00:10.1 iSerial 1 0000:00 | 03:02 |
T42 | <eminarican> | 03:02 |
T42 | <eminarican> there's no info i can see about telnet on serial | 03:02 |
mal | did you try "telnet 192.168.2.15 23" or "telnet 192.168.2.15 2323" | 03:07 |
T42 | <eminarican> yup didn't worked | 03:08 |
mal | is usb interface up? | 03:08 |
mal | what did dmesg show about mer? | 03:09 |
T42 | <eminarican> [ 2548.848774] usb 1-1: USB disconnect, device number 4 [ 2551.573312] usb 1-1: new high-speed USB device number 5 using ehci-pci [ 2551.731474] usb 1-1: New USB device found, idVendor=18d1, idProduct=d00d, bcdDevice= 1.00 [ 2551.731486] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2551.731491] usb 1-1: Product: Android [ 2551.731494] usb 1-1: Manufacturer: Google [ 2551.731497] usb 1-1: SerialNumber: 61e9a9d8 [ 2622 | 03:10 |
mal | was there something about mer or not? | 03:11 |
mal | did you try to force it to stop before systemd (if it reaches that far) https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L38 | 03:12 |
mal | adding that file to sailfishos root (you can add it via recovery for example) will stop boot quite early which can help debugging (boot can be continued via telnet) | 03:13 |
mal | so that /init_enter_debug2 file | 03:14 |
T42 | <eminarican> okay lemme try that | 03:14 |
mal | you still didn't verify if you had something about mer in dmesg, that could tell how far it booted | 03:14 |
T42 | <eminarican> there's (re @eminarican: [ 2548.848774] usb 1...) | 03:15 |
mal | that had nothing about mer, or did I miss something | 03:17 |
mal | that things in that line where usb 1-1: SerialNumber: 61e9a9d8 [ 2622 | 03:18 |
mal | show only the line which mentioned mer | 03:18 |
T42 | <eminarican> usb 1-1: Product: Failed to boot init in real rootfs | 03:20 |
T42 | <eminarican> usb 1-1: Manufacturer: Mer Boat Loader | 03:20 |
T42 | <eminarican> usb 1-1: SerialNumber: Mer | 03:20 |
T42 | <eminarican> usbcore: registered new interface driver cdc_ether | 03:20 |
T42 | <eminarican> rndis_host 1-1:1.0 usb0: register 'rndis_host' at usb-0000:00:12.2-1, RNDIS device, 6a:47:e3:a9:a5:f2 | 03:20 |
T42 | <eminarican> usbcore: registered new interface driver rndis_host | 03:20 |
T42 | <eminarican> | 03:20 |
T42 | <eminarican> aren't those the stuff about mer (sorry if i'm wrong i'm not well knowledged about these stuff T.T) | 03:20 |
T42 | <eminarican> kinda understood | 03:30 |
T42 | <eminarican> are you refering to the file init-debug? (re @SailfishFreenodeIRCBridgeBot: <mal>adding that fil...) | 03:32 |
mal | that "Failed to boot init in real rootfs" means it fails before it reaches rootfs | 03:39 |
mal | https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L397 | 03:39 |
mal | possible reasons, incorrect kernel configs, incorrectly extracted rootfs at least | 03:40 |
mal | check these kernel configs https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L325 from the .config somewhere in hybris-hal build out/ folder | 03:41 |
mal | @eminarican how did you extract the rootfs? | 03:41 |
T42 | <eminarican> sent it to device, | 03:43 |
T42 | <eminarican> when i realized i can't extract .bz2 | 03:43 |
T42 | <eminarican> extracted it from bz2 on my pc | 03:43 |
T42 | <eminarican> resent | 03:43 |
T42 | <eminarican> then using tar command extracted its content to place | 03:43 |
T42 | <eminarican> sent it to device, | 03:43 |
T42 | <eminarican> when i realized i can't extract .bz2 on my phone | 03:43 |
T42 | <eminarican> extracted it from bz2 on my pc | 03:43 |
T42 | <eminarican> resent | 03:43 |
T42 | <eminarican> then using tar command extracted its content to place (edited) | 03:43 |
T42 | <eminarican> (ah... forgot again sorry for edit) | 03:44 |
mal | are you sure you extracted it to correct place? | 03:45 |
mal | this is how I do it: tar --numeric-owner -xvjf sfos_package.tar.bz2 -C /data/.stowaways/sailfishos | 03:46 |
T42 | <eminarican> its under | 03:46 |
T42 | <eminarican> /data/.stowaways/sailfishos | 03:46 |
T42 | <eminarican> tar --numeric-owner -xvf sfos_package.tar -C /data/.stowaways/sailfishos | 03:47 |
T42 | <eminarican> mine was like that | 03:47 |
T42 | <eminarican> then maybe incorrect kernel config as you said? | 03:48 |
T42 | <eminarican> shouldn't it needs to give some warning or errors? | 03:48 |
mal | I think there are couple of option which can in rare occasion not exist | 03:48 |
mal | so check the list in that init-script manually from your output .config file | 03:50 |
T42 | <eminarican> okay lemme see if i can figure it out | 03:51 |
mal | I need some sleep now | 03:53 |
T42 | <eminarican> actually same... it's 6:53am here T.T | 03:53 |
T42 | <eminarican> maybe it's better look into it tmr | 03:53 |
mal | yeah | 03:53 |
T42 | <eminarican> gn 07 | 03:53 |
T42 | <elros34> ifconfig should show new usb interface now. You should be able to telnet at 23 port and read init.log/diagnosis.log | 07:38 |
T42 | <elros34> but based on output it's something wrongly extracted. Did you format /data partition? Do you have /data/.stowaways/sailfishos/init-debug ? | 07:47 |
*** amccarthy is now known as Guest5129 | 08:02 | |
*** amccarthy_ is now known as amccarthy | 08:02 | |
T42 | <eminarican> it doesn't show up on ifconfig, and yup for the init-debug file i have (re @elros34: but based on output ...) | 09:39 |
T42 | <eminarican> i've realized that i forgot to remove filepath prefixes for fixup-mountpoints | 09:42 |
T42 | <eminarican> /dev & /dev/block removed them and make hybris-boot | 09:42 |
T42 | <eminarican> but it's the same problem occurs | 09:42 |
T42 | <eminarican> do i need to update/build something else for it to take effect or it may not be the root of my problems? | 09:42 |
T42 | <elros34> fixup-mountpoints are irrelevant for this issue. If you have these dmesg messeges and device doesnt reboot then you really should have usb interface in ifconfig. power it up, run dmesg -w and in other terminal ifconfig -a | 09:45 |
T42 | <elros34> even if mountpoints are wrong you should have telnet available but make hybris-boot should be enough for now for any initramfs kernel changes | 09:46 |
T42 | <eminarican> [26691.555406] usb 1-1: USB disconnect, device number 16 [26705.135942] usb 1-1: new high-speed USB device number 17 using ehci-pci [26705.293441] usb 1-1: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.14 [26705.293452] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [26705.293457] usb 1-1: Product: Failed to boot init in real rootfs [26705.293460] usb 1-1: Manufacturer: Mer Boat Loader [26705.293463] | 09:48 |
T42 | <eminarican> | 09:48 |
T42 | <eminarican> usb0: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether fa:1d:5e:1d:f0:9e txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 😎 RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 😎 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 | 09:48 |
T42 | <elros34> usb0 disappears when you disconnect phone? Then this is your interface | 09:50 |
T42 | <eminarican> lemme see | 09:50 |
T42 | <eminarican> yup | 09:50 |
T42 | <eminarican> it has the same id tho | 09:50 |
T42 | <eminarican> fa:1d:5e:1d:f0:9e yea | 09:51 |
T42 | <elros34> https://sailfishos.wiki/link/20#bkmrk-%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0-%2A-if-ifconfi | 09:52 |
T42 | <elros34> you need to see "inet addr:*" in ifconfig then you will be able to telnet | 09:54 |
T42 | <eminarican> idk what did i done but | 10:00 |
T42 | <eminarican> SerialNumber: Mer Debug telnet on port 23 on rndis0 192.168.2.15 - also running udhcpd this started to show up in dmesg | 10:00 |
T42 | <eminarican> but still interface is not up (re @eminarican: [26691.555406] usb 1...) | 10:00 |
T42 | <eminarican> lemme see (re @elros34: https://sailfishos.w...) | 10:01 |
T42 | <eminarican> in init.rc | 10:07 |
T42 | <eminarican> | 10:07 |
T42 | <eminarican> # Mer handles usb stuff #import /system/etc/init/hw/init.usb.rc | 10:07 |
T42 | <eminarican> | 10:07 |
T42 | <eminarican> it is commented | 10:07 |
T42 | <eminarican> should i uncomment and try with it? | 10:07 |
T42 | <elros34> focus on ip address add/ route add commands from halium instruction | 10:10 |
T42 | <eminarican> 07 | 10:11 |
T42 | <eminarican> i'm in := | 10:17 |
T42 | <eminarican> + mkdir /data | 11:02 |
T42 | <eminarican> + mkdir /target | 11:02 |
T42 | <eminarican> + mount /dev/block/bootdevice/by-name/userdata /data | 11:02 |
T42 | <eminarican> mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: No such file or directory | 11:02 |
T42 | <eminarican> + mount --bind /data//.stowaways/sailfishos /target | 11:02 |
T42 | <eminarican> mount: mounting /data//.stowaways/sailfishos on /target failed: No such file or directory | 11:02 |
T42 | <eminarican> + mkdir /target/data | 11:03 |
T42 | <eminarican> + mount --bind /data/ /target/data | 11:03 |
T42 | <eminarican> + mount | 11:03 |
T42 | <elros34> this is clearly incorrect fixup mountpoints | 11:04 |
T42 | <eminarican> https://hastebin.com/share/betehutema.bash | 11:07 |
T42 | <eminarican> so shouldn't it needs to be like that? | 11:07 |
T42 | <eminarican> https://hastebin.com/share/betehutema.bash | 11:08 |
T42 | <eminarican> so it shouldn't needs to be like that? (edited) | 11:08 |
T42 | <elros34> probably no, but I can not say for sure without your fstab | 11:10 |
T42 | <eminarican> / # cat /etc/fstab devpts /dev/pts devpts defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 /proc/sys/debug /proc/sys/debug debugfs defaults 0 0 none /var/run tmpfs size=256k,mode=0755,nosuid,noatime 0 0 | 11:12 |
T42 | <eminarican> this :=? | 11:12 |
T42 | <elros34> no android one, read that hadk-hot link, especially fixup-mountpoints related info | 11:13 |
T42 | <eminarican> 07 | 11:13 |
voidanix[m] | Probably lsblk/blkid would tell more than the android fstab | 11:14 |
T42 | <elros34> no, not at all. fixup-mountpoints are all about android fstab and real block devices | 11:17 |
T42 | <elros34> and he use wrong by-name paths which are from android's fstab | 11:18 |
T42 | <eminarican> now i got into telnet thru 2323 port | 15:23 |
T42 | <eminarican> | 15:23 |
T42 | <eminarican> Welcome to the Mer/SailfishOS Boat loader debug init system. Log so far is in /init.log To make post-switch_root halt before starting systemd, perform: touch /init_enter_debug2 (When run post-switch_root, telnet is on port 2323, not 23) | 15:23 |
T42 | <eminarican> | 15:23 |
T42 | <eminarican> did "ln -s /dev/null /etc/systemd/system/droid-hal-init.service" and how can i continue booting? when i do | 15:23 |
T42 | <eminarican> | 15:23 |
T42 | <eminarican> echo "continue" >/init-ctl/stdin | 15:23 |
T42 | <eminarican> | 15:23 |
T42 | <eminarican> it says nonexistent directory | 15:23 |
T42 | <elros34> why do you mask droid-hal-init? now get journalctl logs | 15:29 |
T42 | <eminarican> https://hastebin.com/share/tigogefuzu.yaml | 15:42 |
T42 | <eminarican> uhh tbh was following the stuff i find thru logs (re @elros34: why do you mask droi...) | 15:43 |
T42 | <elros34> what stuff was not working? enable it back unless device reboots and you cant get logs | 15:52 |
mal | also running "systemctl" will give some idea what services are failing | 15:52 |
T42 | <eminarican> + mkdir /config/usb_gadget/g1/functions/rndis_bam.rndis mkdir: can't create directory '/config/usb_gadget/g1/functions/rndis_bam.rndis': No such file or directory /init-debug: line 281: can't create /etc/udhcpd.conf: nonexistent directory /init-debug: line 282: can't create /etc/udhcpd.conf: nonexistent directory /init-debug: line 283: can't create /etc/udhcpd.conf: nonexistent directory /init-debug: line 284: can't create /etc/udhcpd.con | 16:06 |
T42 | <eminarican> | 16:06 |
T42 | <eminarican> systemctl output: | 16:06 |
T42 | <eminarican> https://hastebin.com/share/pobosusubi.sql | 16:06 |
T42 | <eminarican> | 16:06 |
T42 | <eminarican> after 1 min telnet gets closed but phone doesn't reboot (re @elros34: what stuff was not w...) | 16:06 |
T42 | <elros34> init.log is no longer useful for anything. Like I said get journal log (see hadk-hot). From systemctl output it's clear that system partition is not mounted so this is first to fix | 16:21 |
T42 | <eminarican> this one is journal log (re @eminarican: https://hastebin.com...) | 16:23 |
T42 | <eminarican> do i need to get it while theres no masking? | 16:23 |
T42 | <elros34> of course and also ready whole hadk-hot because it will really save you time especially: "Generating logs", "我有 telnet 但没有 gui" sections | 16:25 |
T42 | <eminarican> 07 okay lemme try to figure it out by lookin them | 16:26 |
T42 | <eminarican> ah right journal log first | 16:26 |
T42 | <elros34> system.mount is wrong so fix this | 16:29 |
mal | does the device use real partitions or dynamic partitions? | 16:32 |
mal | based on this dynamic partitions https://github.com/LineageOS/android_device_xiaomi_surya/blob/lineage-18.1/rootdir/etc/fstab.qcom | 16:34 |
T42 | <eminarican> okay, also there's the journal | 16:43 |
T42 | <eminarican> https://hastebin.com/share/paduduyace.less (re @elros34: system.mount is wron...) | 16:43 |
mal | read the information about dynamic partition from hadk-hot https://etherpad.wikimedia.org/p/hadk-hot | 16:50 |
T42 | <eminarican> so the problem is my device can't mount system since it's not using real partitions? (re @SailfishFreenodeIRCBridgeBot: <mal>does the device...) | 16:52 |
T42 | <elros34> yes | 16:54 |
T42 | <elros34> btw next time you will create image use latest release 4.5.0.24 | 16:55 |
T42 | <eminarican> isn't it easy to update to latest release afterwards? := | 16:56 |
T42 | <elros34> it is but why why download all these packages on device when you for sure will build new image few times | 16:58 |
T42 | <eminarican> you are right but i'm asking it for this time, like | 17:03 |
T42 | <eminarican> "if it's a bit tiring to do then i can just start over with latest release" | 17:03 |
T42 | <elros34> this time you just change one env RELEASE to lastest one and forget about it | 17:06 |
T42 | <eminarican> nice := | 17:06 |
piggz | mal: https://imgur.com/a/2NIRaKY | 21:35 |
mal | piggz: :) | 22:13 |
T42 | <kirbylife> Awesome!! (re @SailfishFreenodeIRCBridgeBot: <piggz>mal: https://...) | 22:16 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!