**** BEGIN LOGGING AT Tue Jul 02 02:59:56 2019 Jul 02 12:51:36 themighty420 was added by: themighty420 Jul 02 12:53:08 Halium initrd Failed to boot, builds were successful.. Help please Jul 02 12:53:30 hybris-boot.img? Jul 02 13:03:25 are you able to enter a device shell using ssh? Jul 02 13:03:53 or at least, are you able to find a device in your host machines dmesg output? Jul 02 13:04:12 (probably no ssh without successful initrd boot) Jul 02 13:45:40 @Danct12 [hybris-boot.img?], Hello danct12 i am porting for redmi 4x hybris-boot.img build successfully Jul 02 13:46:44 @themighty420 [Hello danct12 i am porting for redmi 4x hybris-boot.img build successfully], Using kernel source tree and vender from github/ubport-santoni Jul 02 14:12:16 We have never tested hybris-boot, only halium-boot which is used for UBPorts Jul 02 14:12:44 But then, can you check if you could connect to SSH? Jul 02 14:33:50 On hybrids boot as well as on halium boot i got initrd failed to boot Jul 02 14:37:17 Do you have all required kernel flags enabled? Compare with the output of mer-kernel-check Jul 02 15:00:06 Hey, I'm in the same situation as themighty420 Jul 02 15:00:45 I take a look at my console ramoops file and looks like I have a kernel panic but I don't understand what cause this issue Jul 02 15:01:43 Is your /data partition encrypted? Jul 02 15:01:53 @fredldotme [Do you have all required kernel flags enabled? Compare with the output of mer-ke …], Yes did Jul 02 15:02:23 @Danct12 [Is your /data partition encrypted?], No wiped all first Jul 02 15:03:01 Even the red "Format Data" button from TWRP? Jul 02 15:03:13 Which would also wipe internal storage Jul 02 15:03:35 No from advance, all Jul 02 15:07:44 No idea then, I usually would boot hybris-recovery.img when the generic boot image doesn't boot. Might worth a try if you haven't tried it out Jul 02 15:13:46 @Danct12 [No idea then, I usually would boot hybris-recovery.img when the generic boot ima …], Sir i saw a twitter account with name danct12 and he posted that he booted ubport for redmi 4x with almost everything working, is this you? Jul 02 15:15:44 Yep, that's me Jul 02 15:33:07 @Danct12 [Yep, that's me], Oh great Jul 02 15:33:50 So are you still on ubuntu touch Jul 02 15:34:11 Everything is working? Jul 02 15:38:44 not all working btw Jul 02 15:38:54 modem sometimes just doesn't wanna come up until a reboot Jul 02 15:46:27 Can u upload system.img and halium-boot.img to github or any, Jul 02 15:52:16 I probably won't until the most important bug is sorted out Jul 02 15:52:26 the calls bug Jul 02 16:07:21 @Danct12 [the calls bug], Ok Jul 02 20:09:44 Hi! While building the `systemimage`, I got this error: Jul 02 20:09:47 ninja: error: '/mnt/Lavoro/halium/out/target/product/j3xlte/obj/STATIC_LIBRARIES/libbootloader_message_intermediates/export_includes', needed by '/mnt/Lavoro/halium/out/target/product/j3xlte/obj/EXECUTABLES/vold_intermediates/import_includes', missing and no known rule to make it Jul 02 20:10:28 I got similar errors before (about libcurl), but it looks like this "vold" has something to do with the bootloader. Or is it something I can disable safely? Jul 02 20:11:02 it's mentioned in at least these 2 makefiles: build/core/main.mk: system/vold \ Jul 02 20:11:04 build/target/product/base.mk: vold \ Jul 02 20:12:37 Hi, I successfully build my hybris-boot but when I flash it on my device, it's doing a boot loop. … So I check my console-ramoops file and found this line: … [ 8.025180s][pid:1,cpu1,swapper/0]Unable to handle kernel NULL pointer dereference at virtual address 0000001e … And don't know what to do to solve this. Jul 02 20:12:38 Oh and here is the full file: … https://pastebin.com/JZ4XZt9N … And here what it should like when it boots successfully: … https://pastebin.com/stwYCzVw Jul 02 21:00:07 Fwd from ankaos: how running android container? Jul 02 21:00:07 Fwd from ankaos: status stopped say me Jul 02 22:16:05 https://soundcloud.com/ubports/porting-a-true-journey-episode-1-where-do-we-begin Jul 03 01:27:21 Jack ma was added by: Jack ma Jul 03 01:27:30 My ramoops log is a binary file called dmesg-ramoops-0.enc.z and I can't read it. Why is this? Jul 03 02:05:16 Im wondering if its compressed like a zip file if im honest Jul 03 02:28:01 Yes, it looks like gzip, but it can't be decompressed **** ENDING LOGGING AT Wed Jul 03 03:00:28 2019