**** BEGIN LOGGING AT Sat May 30 02:59:59 2020 May 30 18:22:05 @Nebrassy it seems I made derps while settings halium flags, that's why my kernel was compiling fine but wasn't booting, however, after fixing derps, I am getting this error … https://paste.linux.pizza/?f8d840affec2e1a2#6msHReQqffydHSDeCcptUcanC6Sw5R4ucsUN8bfuTN45 May 30 19:06:02 Soo May 30 19:07:10 @Deathmist1337 [if it's a newer device using ConfigFS for USB modes (search defconfig for CONFIG …], This seemed to be the issue May 30 19:07:22 And I a line in the config file May 30 19:07:55 4 GNU/Linux Device on rndis0 10.15.19.82 now I am getting this output from the USB serial number May 30 19:08:01 I again May 30 19:08:17 followed the tutorial yet no luck in getting the telnet nor the ssh to work May 30 19:08:32 I tried using the plasma mobile rootfs but that didnt respond at all May 30 19:09:20 I could just move onto porting halium-boot and leave hybris completely but I am guessing this would at least prompt some of the errors before proceeding to that stage May 30 19:09:31 Any help would be appreciated May 30 19:33:23 @NotKit would you mind a `hybris-patch` that makes `systemimage` compilable without a python2 virtualenv (fixes all `#!/usr/bin/env python` lines to `#!/usr/bin/env python2` in scripts)? :p May 30 20:05:43 Alright so i'm havinf trouble with my device, the bootloader says BL:N/A, Baseband:N/A and has no slot information. It cannot boot twrp, but the bootloader is working. May 30 20:08:09 (Photo, 358x779) https://irc.ubports.com/Rnn0ayOl.png oh my May 30 20:13:41 @SolarisSpark [Alright so i'm havinf trouble with my device, the bootloader says BL:N/A, Baseba …], so it's locked then? May 30 20:15:26 @Deathmist1337 [so it's locked then?], No, it's unlocked. May 30 20:15:41 where do people find these devices lol May 30 20:16:00 Its my Pixel lol, I missed a step when I resized a partition. May 30 20:16:11 Been trying to fix it all night May 30 20:18:32 which step and which partition? May 30 20:18:41 I'm unlikely to be able to help but just curious May 30 20:19:07 Boot, and I somehow forgot to use mke2fs -b 4096 -T ext4 /dev/block/sda19 May 30 20:19:18 And the same for sda20 May 30 20:19:36 so you tried to enlarge your boot partition, what is sda20? May 30 20:19:43 boot_b May 30 20:20:10 well then yet another partition is also affected (sda21) assuming you actually were trying to enlarge it May 30 20:20:31 Nope. Just 19 and 20, both boot partitions. May 30 20:20:52 so bigger boot_a and a smaller boot_b? nice. I don't see how this would entirely break everything though May 30 20:22:12 Because I never made the ext4 partitions May 30 20:22:21 can't you just format them from fastboot? May 30 20:22:23 So they never even got named May 30 20:22:25 Nope May 30 20:22:32 Believe me I've tried May 30 20:23:06 and you can't fastboot boot anything either for whatever reason? May 30 20:23:15 Yep. May 30 20:23:25 I've tried. May 30 20:23:40 It looks like it tries for a split second May 30 20:23:45 Then reboots. May 30 20:24:16 TWRP prob has some dependency on `/boot*`, maybe a patched TWRP ramdisk would work? May 30 20:24:28 you'd have to build it from source though May 30 20:24:42 It does May 30 20:24:44 also quick Q: why are you resizing boot in the first place May 30 20:24:47 I looked at the fstab May 30 20:24:58 @Deathmist1337 [also quick Q: why are you resizing boot in the first place], TWRP 3.3.1-4 May 30 20:25:14 that doesn't tell me anything May 30 20:25:42 TWRP 3.3.1-4 doesnt fit in the stock ramdisk. May 30 20:25:46 It's too big. May 30 20:26:29 why should it? it's literally just 2 files; a kernel and a ramdisk, you can just replace the ramdisk with whatever as long as the boot partition is big enough to hold both May 30 20:26:40 Thats the problem May 30 20:26:49 not really, is your boot 16 MB or some crap? May 30 20:26:49 The boot partition is where the recovery is May 30 20:26:53 Its 32 May 30 20:27:10 Or 33 May 30 20:27:13 I cant remember May 30 20:28:19 @SolarisSpark [The boot partition is where the recovery is], god damn, forgot how trash A/B is. I have a 64 MB partition on a "legacy" device lol. I could take a look into creating a TWRP ramdisk without dependency on any `/boot*` stuff May 30 20:29:23 That would be much approciated, as I have tried already but I just cant figure it out. … Im on sailfish, Pixel 1 non XL. May 30 20:29:31 [Edit] That would be much appreciated, as I have tried already but I just cant figure it out. … Im on sailfish, Pixel 1 non XL. May 30 20:31:55 All I'd need to do is comment out the part of fstab.recovery where it mentions /boot May 30 21:55:01 Randall Williams was added by: Randall Williams May 30 22:04:07 Hoàng Công Johnnson was added by: Hoàng Công Johnnson May 30 22:50:13 For building kernel without Android source (per Erfan's recommendation) do you guys use the new clang compiler or the older gcc compiler? May 30 22:52:21 Sorry if my understanding is off but I saw that gcc is no longer present in the 4.9 toolchain. **** ENDING LOGGING AT Sun May 31 02:59:57 2020