**** BEGIN LOGGING AT Sun Jan 20 02:59:57 2019 Jan 20 11:11:42 Hi! … @Sergobot The flag for mounting an image as read/write seems to have changed from what's in your guide ... Jan 20 11:12:04 Your guide (for Pixel XL / marlin) uses: /data/.writable_device_image Jan 20 11:12:18 Been wrestling with this for days to no avail😢 Jan 20 11:12:54 Was going to ask you, but thought that hell, I'm not going to disturb his peace with another pointless question, am I?😅 Jan 20 11:13:04 So I looked for it a little harder Jan 20 11:14:00 And found it at last. In the halium-boot instruction page at https://github.com/Halium/projectmanagement/issues/40https://github.com/Halium/projectmanagement/issues/40 … it uses this flag instead: … /data/.writable_image Jan 20 11:30:12 I have a problem now Jan 20 11:30:40 Even though I mounted the rootfs read/write Jan 20 11:30:55 Any and all tests are failing with a Segmentation Fault Jan 20 11:31:48 Running 'strace' on, for example, test_vibrator results in a bunch of "No such file or directory" for a bunch of .so files that should be under /vendor and /system Jan 20 11:46:46 @WaseemAlkurdi, Have you got firmware partition mounted? Jan 20 11:46:53 @WaseemAlkurdi, And vendor? Jan 20 11:47:16 Nope, neither one seems to be Jan 20 11:48:40 Should I try to mount them by hand? Jan 20 11:51:06 Wait a minute Jan 20 11:51:16 I have a vendor partition Jan 20 11:51:26 Where should I mount it? Jan 20 11:52:48 In Halium (halium rootfs), there is: … * A /system folder containing nothing … * A /android folder containing three folders: data, system, vendor Jan 20 11:53:01 The /data/vendor folder is actually a symlink to /system/vendor Jan 20 11:53:16 So where should I mount everything now? Jan 20 11:53:25 @meltstrap, do they have same hardware or? Jan 20 11:59:18 @WaseemAlkurdi, Use mount command and check it Jan 20 12:25:47 @Mattia990 … This is my mount output: … https://termbin.com/b88i Jan 20 12:58:54 @WaseemAlkurdi, I don't see firmware partition Jan 20 13:00:02 Just to be sure … Do you need a mount output from Halium or from a working TWRP? Jan 20 13:01:58 @WaseemAlkurdi, Halium Jan 20 13:04:36 Hang on a sec Jan 20 13:07:55 https://termbin.com/bils Jan 20 13:07:56 There you go Jan 20 13:08:46 Halium mount command after mounting the (real) system and vendor partitions (as opposed to system.img or something) Jan 20 13:09:46 @WaseemAlkurdi did you rename `/data/system.img` to `/data/android-rootfs.img` ? Jan 20 13:10:13 While in TWRP ^ Jan 20 13:10:49 Because I see only one loop device mounted and that's rootfs.img (mounted at /) Jan 20 13:11:36 @Sergobot Of course I did Jan 20 13:11:43 Tried both ways Jan 20 13:11:52 Hm, that's interesting Jan 20 13:11:57 Post dmesg then Jan 20 13:12:07 And tried with the patched script Jan 20 13:12:31 Will do Jan 20 13:16:35 @Sergobot @Mattia990 … Sorry ... the mount command above was for one of my earlier experiments Jan 20 13:16:40 This is the correct one Jan 20 13:16:41 https://termbin.com/rgrb Jan 20 13:18:12 We don't have that partition Jan 20 13:18:16 We use /vendor Jan 20 13:18:23 It's a Project Treble device Jan 20 13:18:29 Ah sorry Jan 20 13:18:35 Haven't understand Jan 20 13:18:44 @Mattia990, No problem!😊 Jan 20 13:18:57 There comes the dmesg: Jan 20 13:18:58 https://termbin.com/nezw Jan 20 13:22:57 `[ 3.853369] mount: mounting /dev/loop1 on /android-rootfs failed: Invalid argument` Jan 20 13:24:23 No driver for fs or wrong loop? Jan 20 13:31:20 @WaseemAlkurdi Try mounting it manually: `mount -o loop,rw /userdata/android-rootfs.img /android` Jan 20 13:34:19 ... And see if that succeeds Jan 20 13:41:46 True, this seems to be the issue … But the 'invalid argument' error is too cryptic Jan 20 13:48:39 No, it fails Jan 20 13:48:53 mount: wrong fs type, bad option, bad superblock on /dev/loop1, … missing codepage or helper program, or other error Jan 20 13:50:31 Image seems to be corrupt Jan 20 13:50:45 @Sergobot I'll try to pull it to my laptop and mount it Jan 20 13:51:15 BTW for some reason also android-rootfs.img gets corrupted when pushing it (a 0 KB file gets pushed, so I push it by hand) Jan 20 13:51:27 The corruption doesn't happen during the push though Jan 20 13:51:36 <_nbvcxw> y0 Jan 20 13:51:55 When I go to halium-install's temp directory, the file is there and is already 0 KB Jan 20 13:53:45 Yeah, you're absolutely correct @Sergobot! … It's actually corrupt Jan 20 13:54:03 This rules out any issue with the rootfs I presume? Jan 20 13:54:47 @WaseemAlkurdi, What other issues are you talking about? Jan 20 13:55:00 @WaseemAlkurdi, How did you install it? Jan 20 13:55:07 Any possible issue with the rootfs itself? … Missing drivers, etc? Jan 20 13:55:24 Installed using JBB's modded halium-install, as you told me to Jan 20 13:55:48 But as I said, the generated system.img is always zero KB in size Jan 20 13:56:09 so I'd go to the Halium build output directory and push the system.img there Jan 20 13:56:14 From there* Jan 20 13:56:21 It'd be the correct size Jan 20 13:57:15 @WaseemAlkurdi, Alright, what's the command? :) Jan 20 13:58:30 ./halium-install -p halium -v /media/waseem/data/halium-rootfs-20170630-151006.tar.gz ~/halium/out/target/product/marlin/system.img Jan 20 13:59:11 Also tried using Plasma Mobile's rootfs Jan 20 13:59:23 with -p pm instead of -p halium Jan 20 13:59:58 Ah, okay Jan 20 14:00:11 Totally not sure what could go wrong then Jan 20 14:00:33 Did you notice any errors during installation? Jan 20 14:00:39 Yeah I did Jan 20 14:00:52 It's related to the corrupt system.img Jan 20 14:00:56 Let me show you Jan 20 14:02:29 And I forgot something Jan 20 14:02:36 There's a locale error with perl Jan 20 14:02:47 Doesn't occur when using the Plasma Mobile rootfs Jan 20 14:03:48 https://termbin.com/jh6g Jan 20 14:04:00 This is the installer output for a Halium rootfs Jan 20 14:06:40 This line: `Failed to read sparse file` Jan 20 14:06:46 An issue with your system.img Jan 20 14:06:55 During compilation? Jan 20 14:07:11 So what do you recommend? Jan 20 14:07:14 A recompile? Jan 20 14:07:35 Idk, but that may help Jan 20 14:07:41 e2fsck: Attempt to read block from filesystem resulted in short read while trying to open .halium-install-imgs.Af8ez/system.img Jan 20 14:07:45 There's this too Jan 20 14:08:01 @Sergobot, What else? What if it didn't help? Jan 20 14:08:26 Never experienced this, sorry :( Jan 20 14:09:02 @Sergobot, Guess I'm on my own in this ... … Well, I really, really appreciate what you've helped me with so far!😍 Jan 20 14:09:39 Laptop batteries aren't eternal (unfortunately), so I'm going out ... Jan 20 14:10:09 Okay, goodbye :) Jan 20 15:53:09 @NotKit, No, but I need a new phone if I want to do it, cuz my phone is a Redmi 5, and I don't have a spare one. Jan 20 15:55:46 The Redmi 5 uses a SD450, which is ideal since it is a Qualcomm SoC and not from MediaTek. Jan 20 15:58:08 Porting should be pretty much straight forward. I won't be using MIUI, because it is so different from AOSP. Instead, I'll use LineageOS 14.1. Jan 20 15:59:19 (unofficial though. There's no official builds for rosy) Jan 20 16:00:02 now let's bringup hermes Jan 20 18:11:06 (Photo, 400x44) https://irc.ubports.com/M5ilpMt8.png Can anyone help me with this? Jan 20 18:11:46 @XiaoAk, Connect to the phone with telnet and check diagnosis.log Jan 20 18:13:03 ok let me try Jan 20 18:19:44 Njoroz Ian was added by: Njoroz Ian Jan 20 18:24:39 onlygecko was added by: onlygecko Jan 20 18:26:03 @WaseemAlkurdi since you're pushing system.img manually, did you convert it to a raw image first? Jan 20 18:30:59 @Mattia990, I did that and added a missing flag in defconfig, but now device reboots into QDloader Jan 20 18:34:35 @XiaoAk, Mmmm idk, sorry Jan 20 18:35:05 no worries, I'll try to look into it myself Jan 20 18:35:12 thanks for the help Jan 20 20:58:07 Beloglazov Evgeniy was added by: Beloglazov Evgeniy Jan 20 22:44:46 <_nbvcxw> hello Jan 20 22:46:50 <_nbvcxw> Someone would tell me why "setup " gets stuck on "Generating makefile for vendor blobs" ? Jan 21 00:43:49 nio_Herzn was added by: nio_Herzn **** ENDING LOGGING AT Mon Jan 21 02:59:56 2019