**** BEGIN LOGGING AT Fri Oct 05 03:00:02 2018 Oct 05 03:04:17 Oh, that's in the init files O.o Oct 05 03:06:45 https://github.com/LineageOS/android_device_nvidia_shield-common/blob/cm-14.1/initfiles/init.tegra_emmc.rc Oct 05 03:06:48 weiiiiiird. Oct 05 03:19:55 @Lyokanthrope, remove those options from fstab Oct 05 03:23:30 @trivial_inanity, it wasn't in my fstab, the device's initscripts were just doing weird stuff Oct 05 03:31:13 https://paste.ubuntu.com/p/jzF5gRrJnn/ … finally built a proper image using hybris-boot and trying to boot halium rootfs without success, it boots to telnet again and looking through my dmesg it seems that it is still unable to open initial console. Am i correct or is there something else i am not seeing? Oct 05 03:33:23 nevermind. I think i have to mount as ro, but am unsure how. i believe it is in the halium guide somewhere. off to go look. (look at line 871) Oct 05 03:44:31 i cant find it :( Oct 05 05:04:29 Any ideas? Oct 05 05:27:02 @kaibsora, mount what? Oct 05 05:27:36 @kaibsora, Look at the line in my dmesg Oct 05 05:27:42 @kaibsora, the log is from halium-boot for sure Oct 05 05:27:56 Hybris-boot Oct 05 05:28:02 @NotKit, Not halium Oct 05 05:28:36 hybris-boot ramdisk doesn't have /scripts folder Oct 05 05:28:56 I know for sure that I am running hybris-boot Oct 05 05:29:25 are you sure the log is correct one then? Oct 05 05:29:40 Yes Oct 05 05:30:24 [ 4.428201] [2: init: 1] [c2] initrd: device is gtaxlwifi … [ 4.428285] [2: init: 1] [c2] initrd: This rootfs does not have any writable-paths defined Oct 05 05:30:31 hybris-boot never had support for this Oct 05 05:30:38 maybe image didn't get reflashed somehow Oct 05 05:30:43 Hm Oct 05 05:31:00 Should I reflash boot or system? Oct 05 05:31:05 boot Oct 05 05:31:28 you don't flash system, it gets pushed into /data/system.img Oct 05 05:31:38 @NotKit, Alright. I know. Oct 05 05:31:39 [Edit] you don't flash system, it gets converted into raw image and pushed into /data/system.img Oct 05 05:33:15 Wait Oct 05 05:33:21 It was halium boot Oct 05 05:33:36 Hybris just reboots constantly Oct 05 05:38:41 And the doc that I thought was for halium is for ubports after ssh which doesn't help :/ Oct 05 07:44:00 @kaibsora, are you able to get logs? Oct 05 07:44:00 for example by going into recovery after reboot Oct 05 07:44:43 What logs are you looking for Oct 05 07:46:28 last_kmsg Oct 05 07:46:33 for reboot reason Oct 05 07:47:06 For what hybris boot? Oct 05 07:47:40 That was thedmesg for halium-boot Oct 05 07:47:43 to understand why it reboots (probably after switching to rootfs, as this also happened with mine modifed halium-boot ramdisk on your device) Oct 05 07:48:08 It doesn't reboot on it's own. It just goes to telnet with that dmesg Oct 05 09:05:24 https://paste.ubuntu.com/p/FNwtTvfTMQ/ this is halium boot - trying to run mako on halium-5 Oct 05 09:05:52 any idea what those unsupported optional features would be? Oct 05 09:06:16 in the end it does not moung system.img and only the rootfs.img Oct 05 09:20:58 @anpok, No but as I've seen in the guide its harmless due to the fact that it is supposed to be mounted with ext4-fs Oct 05 09:22:14 @anpok try doing fsck.ext4 on system.img Oct 05 09:22:32 failing to mount as ext2/ext3 is fine as system.img is generally ext4 now Oct 05 09:22:56 I have the impression thatI am using the wrong boot Oct 05 09:23:17 What do you need from me again @NotKit Oct 05 09:23:38 maybe I should used ubports-boot for that Oct 05 09:23:43 boot with hybris-boot, wait till it reboots, hold volume key to get into recovery, get /proc/last_kmsg Oct 05 09:23:59 @anpok, it doesn't look like boot issue to me but more an issue with system.img Oct 05 09:23:59 Ok. I'll try in a little bit Oct 05 09:24:17 check its checksum on device and desktop and do fsck.ext4 just in case Oct 05 09:24:40 [ 4.278839] EXT4-fs (loop1): INFO: recovery required on readonly filesystem … [ 4.279022] EXT4-fs (loop1): write access unavailable, cannot proceed Oct 05 09:25:27 hm ok Oct 05 09:26:46 yeah that was it Oct 05 09:52:18 @NotKit https://paste.ubuntu.com/p/4ccHbCbkPx/ having a hard time with this one. This is my last_kmsg Oct 05 09:54:24 which rootfs? Oct 05 09:54:42 halium Oct 05 09:55:21 20170630-151006 Oct 05 10:00:52 do you also have hybris-recovery built? Oct 05 10:08:37 Yes Oct 05 10:12:40 try to boot it to see if it gets to telnet Oct 05 10:13:17 By flashing the recovery over my twrp? Oct 05 10:13:36 over boot Oct 05 10:13:41 it's not recovery actually Oct 05 10:13:44 Ah Oct 05 10:13:54 I will when I get home. Just got off of work Oct 05 11:50:44 @NotKit hybris-recovery gets into telnet Oct 05 11:50:49 What now Oct 05 11:50:53 is /target mounted? Oct 05 11:51:05 Cmd pls Oct 05 11:51:10 XD Oct 05 11:51:11 ls /target Oct 05 11:51:59 Yes Oct 05 11:52:33 It says "data" @NotKit Oct 05 11:52:51 that's all? Oct 05 11:52:56 Yes Oct 05 11:52:58 mount Oct 05 11:53:11 [Edit] get output of "mount" Oct 05 11:53:55 also please pastebin /diagnosis.log Oct 05 11:54:15 Will do. Waiting for the vm to respond ugh Oct 05 11:55:29 ~ # mount … rootfs on / type rootfs (rw,size=851628k,nr_inodes=212907) … devtmpfs on /dev type devtmpfs (rw,relatime,size=851628k,nr_inodes=212907,mode=755) … devpts on /dev/pts type devpts (rw,relatime,mode=600) … sysfs on /sys type sysfs (rw,relatime) … proc on /proc type proc (rw,relatime) … rootfs on /target/data type rootfs (r Oct 05 11:55:29 w,size=851628k,nr_inodes=212907) Oct 05 11:56:32 is your fixup-mountpoints correct? Oct 05 11:56:45 grep DATA_PARTITION /init Oct 05 11:57:49 I'm trying to find it. They aren't being listed... Oct 05 11:58:07 should be in / Oct 05 11:58:46 cat: can't open '/diagnosis.log': No such file or directory Oct 05 11:59:14 what about init.log? Oct 05 12:01:24 https://paste.ubuntu.com/p/GS7DhGdfcd/ Oct 05 12:01:28 @nek Oct 05 12:01:49 @NotKit there you go Oct 05 12:02:09 + mount mmcblk0p22 /data … mount: mounting mmcblk0p22 on /data failed: No such file or directory Oct 05 12:02:15 your fixup-partitions is wrong Oct 05 12:02:26 should be /dev/mmcblk0p22 Oct 05 12:03:08 But I dont see /dev/ in front of any of the other devices mountpoints Oct 05 12:03:14 Mine needs it though? Oct 05 12:04:21 could you point me to it and your device tree? Oct 05 12:05:39 On github. kaibsora/android_device_samsung_gtaxlwifi Oct 05 12:05:57 What do you want me to point you to? My fstab? Oct 05 12:06:15 entry in fixup-mountpoints Oct 05 12:06:35 Paste in coming up Oct 05 12:06:42 [Edit] Pastebin coming up Oct 05 12:07:53 @NotKit https://paste.ubuntu.com/p/R6phG9z6FC/ Oct 05 12:08:30 ``` -e 's /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM mmcblk0p19 ' \``` … change to … ``` -e 's block/platform/13540000.dwmmc0/by-name/SYSTEM mmcblk0p19 ' \``` Oct 05 12:08:44 same with the other ones Oct 05 12:08:56 ok Oct 05 12:09:36 then remove out/target/product/$device/obj/ROOT and rebuild hybris-boot Oct 05 12:09:43 [Edit] then remove out/target/product/$device/obj/ROOT and rebuild hybris-boot and hybris-recovery Oct 05 12:15:34 Both rebuilt. Hybris-boot is not rebooting on it's own now. But it just started up and is not giving a connection to the machine. Normal? Oct 05 12:20:40 not really "normal" Oct 05 12:20:43 if rootfs boots, it should start SSHd Oct 05 12:21:18 I let it sit for 5 minutes. Didn't boot. I installed the recovery and am in telnet again Oct 05 12:23:20 @NotKit https://paste.ubuntu.com/p/PHkNSVHs5k/ Oct 05 12:24:20 echo continue > /init-ctl/stdin Oct 05 12:24:29 rootfs is mounted now Oct 05 12:25:15 Oh my goodness Oct 05 12:29:26 Should I be able to use hybris boot now? Oct 05 12:31:26 Hmmmm. It doesn't seem to boot with hybris boot. But it boots with hybris recovery. Any reason why? Oct 05 12:31:41 boots with hybris recovery? you mean you can SSH? Oct 05 12:31:47 Yes Oct 05 12:31:57 Like after using the command Oct 05 12:32:03 It shows up as ssh Oct 05 12:33:43 that's weird, them both are exactly same script with alwaysdebug disabled/enabled Oct 05 12:39:45 @NotKit, So it shows up as ssh connection but it won't let me connect :/ Oct 05 12:40:13 ssh root@10.15.19.82? Oct 05 12:40:22 Nope Oct 05 12:43:33 It also doesn't ping Oct 05 12:44:01 I get a notification of activation of network connection failed on the vm Oct 05 12:44:25 no idea about vm Oct 05 12:44:38 (Its my ubuntu vm for building) Oct 05 12:47:18 what is in dmesg on host? Oct 05 12:47:28 [Edit] what is in dmesg on host after the switch? Oct 05 12:48:38 @NotKit https://paste.ubuntu.com/p/pjjb4WjnRt/ Oct 05 12:52:03 does ip addr output proper ip for it? Oct 05 12:52:41 After I assign the ip or before? Oct 05 12:53:12 ok, so you assign it manually then Oct 05 12:53:25 According to the guide yes Oct 05 13:07:52 Halium boot is supposed to work with halium rootfs correct? Oct 05 13:11:25 https://paste.ubuntu.com/p/xpMhncWHbh/ if so this is my dmesg from telnet Oct 05 13:13:30 Seems like the error is because the partitions are read only, which I am unsure of how to change Oct 05 13:15:46 which partitions? Oct 05 13:16:30 halium-boot will mount rootfs as ro by default as that's needed for UBPorts Oct 05 13:16:56 I'm just stuck then aren't I. Oct 05 13:17:04 Hybris boot doesn't work Oct 05 13:17:14 are you sure it doesn't? Oct 05 13:17:30 from what it seems it did its job of booting into systemd Oct 05 13:17:39 No connection to pc :/ nothing on screen Oct 05 13:18:01 you won't get anything on screen for sure, but connection would be handy Oct 05 13:18:22 And it seems the rndis adapter keeps soft resetting making a connection impossible since it won't ping Oct 05 13:18:49 in VM or on host? Oct 05 13:18:57 Vm or host Oct 05 13:21:21 ls -la /target/var/log in hybris-recovery Oct 05 13:21:30 maybe there is usb_info.log Oct 05 13:28:32 There is @nekit Oct 05 13:28:36 GNU/Linux Device on rndis0 10.15.19.82 … GNU/Linux Device on rndis0 10.15.19.82 Oct 05 13:29:52 and you see this as well? Oct 05 13:30:00 [Edit] and you see this on host as well? Oct 05 13:30:14 Wait what? Oct 05 13:30:48 I mean, does device display as "GNU/Linux Device on rndis0 10.15.19.82" on host after booting to rootfs? Oct 05 13:31:28 Yes Oct 05 13:31:43 so hybris-boot is working for this Oct 05 13:31:57 it boots to systemd, which later starts usb-tethering.service Oct 05 13:32:06 I wonder why rndis0 doesn't work then though Oct 05 13:33:38 I really dont know. I dont get any connection when I use hybris boot Oct 05 13:35:37 I mean it likely boots into system fine, but there is something wrong on next step then Oct 05 13:36:10 @kaibsora, just plug the phone and wait for atleat three FULL minutes , dont touch it, then use jbb's connect.py Oct 05 13:36:44 In his repo? Oct 05 13:37:12 @kaibsora, yup , halium-install comes with connect.py script Oct 05 13:37:15 use that , Oct 05 13:37:23 bute before that wait for 3 minutes Oct 05 13:37:52 On it Oct 05 13:41:13 @abhishek_0, Sometimes even more.. Oct 05 13:43:24 @Lyokanthrope, What's the data partition called? Oct 05 13:47:33 @VeryOriginalUsername, *mostly Oct 05 13:48:01 [Edit] but before that wait for 3 minutes Oct 05 13:52:38 @abhishek_0, Still no connection Oct 05 13:56:02 your device is Exynos, right? Oct 05 13:56:13 Yup. Exynos 7870 Oct 05 13:57:58 just a wild guess,but try ln -s /dev/null /target/etc/systemd/system/lxc@android.service Oct 05 13:58:05 [Edit] just a wild guess, but try ln -s /dev/null /target/etc/systemd/system/lxc@android.service Oct 05 13:58:25 From telnet with hybris recovery? Oct 05 13:58:27 this will disable LXC container startup in case it messes with USB state somehow Oct 05 13:58:27 yes Oct 05 14:12:10 @NotKit, and nothing still Oct 05 14:46:11 Anyone knows why on Earth when I try to run : ./halium/devices/setup cheeseburger I get this: https://paste.ubuntu.com/p/3p6wbvH9sP/ Oct 05 14:46:32 and my manifest is here: https://paste.ubuntu.com/p/TzQ7XHKMPN/ Oct 05 14:47:27 I have tried to change the manifest so many times, and still the same error message, I don't get it. Oct 05 14:48:53 @Linuxman1, Remove lineageos from name Oct 05 14:56:27 @Mattia990, but from which line/s ??? Oct 05 15:04:04 Yeah, like @Mattia990 said, you have the Github organization name duplicated. … `fatal: repository 'https://github.com/LineageOS/LineageOS/android_vendor_nxp-nfc_opensource_Nfc/' not found` … LineageOS should only be there once. So, in your manifest, for the three repositories it couldn't find, remove "`LineageOS/`" from the `name` at Oct 05 15:04:05 tribute, then try to re-sync. That should fix the issue. Oct 05 15:04:27 [Edit] Yeah, like @Mattia990 said, you have the Github organization name duplicated. … `fatal: repository 'https://github.com/LineageOS/LineageOS/android_vendor_nxp-nfc_opensource_Nfc/' not found` … LineageOS should only be there once. So, in your manifest, for the three repositories it couldn't find, remove "LineageOS/" from the `nam Oct 05 15:04:28 e` attribute, then try to re-sync. That should fix the issue. Oct 05 15:10:03 Any other ideas? I'm kinda stuck without getting a connection... Oct 05 15:11:37 @r3pwn, yeah, it worked, I also removed the cm14.1 Oct 05 15:13:06 @Linuxman1, From where? The one that says `revision="cm-14.1-cheeseburger"` Oct 05 15:13:14 @Linuxman1, [Edit] From where? The one that says `revision="cm-14.1-cheeseburger"`? Oct 05 15:15:44 @r3pwn, from the project path as it was complaining fatal: Couldn't find remote ref refs/heads/cm14.1 Oct 05 15:16:26 Oh. Well, if it works now, and it's the branch you need, then I guess all is good. Oct 05 15:20:57