**** BEGIN LOGGING AT Thu Dec 14 03:00:01 2017 **** BEGIN LOGGING AT Thu Dec 14 12:51:01 2017 Dec 14 18:02:48 Tofe: Think I found the problem... Seems I flashed MIUI 8 based rom which is Android 6 instead of MIUI 9 based rom which is Android 7 ;) Dec 14 18:02:57 Now have correct rom and get something more useful :D Dec 14 18:03:13 ooh, ok, yes, well found Dec 14 18:03:20 https://bpaste.net/show/3e4d3cfd104e Dec 14 18:03:35 [ 6.868541] Failed to find valid rootfs Dec 14 18:03:43 That's logical since I didn't flash anything :P Dec 14 18:03:50 Just booted the fastboot img ;) Dec 14 18:04:18 I was happy when I saw 3.18.85 in the first few lines because that's the new kernel I'm building :D Dec 14 18:04:49 So I guess I should try a proper flash now? Dec 14 18:13:47 yep, it does look good ! Dec 14 18:30:56 Tofe: Seems I need to tweak something still Dec 14 18:31:05 Even with image flashed I get that it cannot find rootfs it seems Dec 14 18:31:06 https://bpaste.net/show/efc7a6c75c1e Dec 14 18:31:53 mount: mounting /dev/mmcblk0p28 on /sdcard failed: Invalid argument Dec 14 18:32:25 Tofe: How I check the partitions again? Dec 14 18:33:04 easiest may be in recovery, look at /dev/mapper (I think) Dec 14 18:33:15 but it looks like something different Dec 14 18:33:39 F2FS-fs (mmcblk0p28): Magic Mismatch, valid(0xf2f52010) - read(0x0) Dec 14 18:34:07 so it wants to mount a F2FS fs, but it doesn't match Dec 14 18:34:26 in recovery, can you mount /data and check what kind of fs it is ? Dec 14 18:35:07 (maybe it's /sdcard -- whatever is mmcblk0p28) Dec 14 18:35:23 How I see the type? Dec 14 18:36:14 just type "mount" Dec 14 18:37:07 https://bpaste.net/show/c9d47571f16c Dec 14 18:37:12 Seems ext4? Dec 14 18:37:29 "/dev/block/dm-0 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered) Dec 14 18:37:56 mmmh "/dev/block/dm-0" ... Dec 14 18:38:41 I'm happy to flash back android if that helps? Dec 14 18:38:48 can you try "dmsetup info /dev/block/dm-0" Dec 14 18:39:00 no no, it's just what I thought: a LVM device Dec 14 18:40:07 dmsetup: not found Dec 14 18:40:40 ah, ok... how to find this information elsewhere... Dec 14 18:41:16 lsblk ? Dec 14 18:43:08 nope Dec 14 18:43:32 anyway, I think the mapping is pretty obvious: two ext4 partitions in a logical device dm-0 Dec 14 18:44:59 so... we should ship a little lvm mapper with our ramdisk, like we do on TP Dec 14 18:46:12 but on TP I think we reuse an old lvm binary which is in /boot, or something like that Dec 14 18:51:08 I must say, in this case, using hybris-boot would probably have helped :D Dec 14 18:53:21 Tofe: https://bpaste.net/show/231be3f41913 Dec 14 18:53:32 Seemsd there's no sdcard there? Dec 14 18:53:42 So 028 is incorrect? Dec 14 18:54:44 userdata -> ../../mmcblk0p49 looks better Dec 14 18:55:44 can you try to mount it from recovery by hand? Dec 14 18:56:15 mount -t ext4 /dev/mmcblk0p49 /whatever Dec 14 18:56:51 it will probably fail, if that partition holds an LVM volume Dec 14 19:05:04 Tofe it seems I don't have any mmcblk in /dev in recovery Dec 14 19:07:30 Let me simply rebuild with the 2 partitions updated Dec 14 19:09:44 ok Dec 14 19:11:09 system was wrong too Dec 14 19:17:08 OK new image copying to be flashed Dec 14 21:13:25 Tofe: Dinner & xmas tree got in between https://bpaste.net/show/dd28fd745476 Dec 14 21:13:59 049 still issue but error slightly different Dec 14 21:32:48 Tofe: You mean this script for TP? https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-hp/recipes-core/initrdscripts/initramfs-boot-android/init-tenderloin.sh **** ENDING LOGGING AT Fri Dec 15 03:00:02 2017