**** BEGIN LOGGING AT Mon Apr 22 03:01:03 2019 Apr 22 05:12:25 tomz tan was added by: tomz tan Apr 22 05:14:23 Good day, Im just starting out and im curious if its possible to port the samsung tab s 8.4 klimtlte? Apr 22 05:17:45 What is the kernel version . if its better than 3.10 and a cm14 custom ROM is available.. You're good to go man.. Apr 22 05:19:56 its 3.4 Apr 22 05:20:26 what does this mean? Some Halium distributions may use a kernel as old as 3.4, such as Ubuntu Touch. Apr 22 05:20:50 Yeah it's possible.. Apr 22 05:21:01 okay thanks Apr 22 05:21:05 You can try buddy Apr 22 05:21:34 Welcome to the community Apr 22 05:22:12 I think it should work, but with patches for sure Apr 22 05:23:09 okay thanks for the reply Apr 22 06:05:39 So I recompiled the stock kernel with no configuration changes and it still panics Apr 22 06:06:17 I'll have a look at trying the official kernel from ZTEs website instead of the LineageOS one Apr 22 06:39:02 Well I guess that is out of the question Apr 22 06:39:17 The official ZTE kernel is broken and does not compile even without modification Apr 22 06:39:30 There is a missing folder that I have been able to find very little info about, with no fixes Apr 22 06:39:51 And it's not on my end either since other people have had that issue Apr 22 06:39:54 Check for help in XDA thread Apr 22 06:40:01 Already looked Apr 22 06:40:20 The folder "drivers/soc/qcom/vendor" is missing and I have found nothing about it Apr 22 06:41:26 (Sticker, 512x512) https://irc.ubports.com/pWCXq6Jo.webp Apr 22 06:42:54 What is problem with lineage? Apr 22 06:49:43 Lineage kernel seems to always panic on boot no matter what I do Apr 22 06:50:41 Did you use check kernel config? Or fixed the kernel manually? Apr 22 06:50:44 I'm trying a few other ideas I have come up with, currently I'm trying the Schwifty kernel which is based on the stock B32 kernel but (hopefully) fixed to actually compile as well as adding a few other features intended to make it run android better that I hope don't interfere with Halium Apr 22 06:50:59 Also I have tried many different kernel configurations with the Lineage kernel Apr 22 06:51:35 Including unchanged, just the two absolutely required options to boot, supposedly correct options and all the options in the kernel checker Apr 22 06:52:34 @Diago99 [Did you use check kernel config? Or fixed the kernel manually?], If you did kernel config manually using mer kernel , probably its becaz of that Apr 22 06:53:04 What should I do instead of that? Apr 22 06:53:34 Wait a moment Apr 22 06:54:53 https://docs.ubports.com/en/latest/porting/building-halium-boot.html Apr 22 06:55:24 Check the kernel config from this command Apr 22 06:55:46 Alright, I'll have a look at that once I try this modified kernel Apr 22 06:56:29 Hey buddy , better watch the live porting video on yt Apr 22 06:57:15 Yeah, I think this problem is more related to ZTE than differences between Android and Halium but I'll have a look at that video Apr 22 08:47:12 Ok right now I'm compiling with the lineage kernel that has had the configuration modified by the halium boot tool Apr 22 08:47:48 None of the non-lineage kernels compile because of that missing qcom vendor folder Apr 22 09:31:03 If you still get errors , check out the common kernel build errors in halium documentations... Apr 22 09:31:42 With the lineage kernel it builds fine, the problem is that is has been panicking very early in the boot process Apr 22 09:31:50 [Edit] With the lineage kernel it builds fine, the problem is that it has been panicking very early in the boot process Apr 22 09:33:07 Well build system.img and try again Apr 22 09:33:37 Just did, still panicking in the same area Apr 22 09:34:00 Okay where is the problem now? Apr 22 09:35:12 Seems to be the same issue as before https://pastebin.com/yeepLkjM Apr 22 09:36:45 (Document) https://irc.ubports.com/qT0wjBgB.txt Apr 22 09:37:03 (Document) https://irc.ubports.com/E7fw36p5.txt Apr 22 09:39:20 R u using halium-boot? Apr 22 09:39:28 I can try halium boot Apr 22 09:39:29 Or hybrid? Apr 22 09:39:35 I have been using hybris Apr 22 09:39:42 Try halium Apr 22 09:41:49 Same thing Apr 22 09:42:27 Exact same error at the same place Apr 22 09:43:02 Send the full logcat from start Apr 22 09:45:59 (Document) https://irc.ubports.com/T5heOOx9.txt Apr 22 09:46:48 I tried booting it twice to hopefully get more info that isn't corrupted Apr 22 09:51:21 Is debugging enabled? Apr 22 09:51:38 What would enable or disable that? Apr 22 09:52:10 (Sticker, 512x509) https://irc.ubports.com/c0CZCKvM.webp Apr 22 09:52:24 Try youtube Apr 22 09:54:08 Assuming you are talking about telnet debugging, it doesn't even get to that point Apr 22 10:05:27 Good day all. Can I use Halium 7.1 with these settings? … Device: Samsung Tabs S 8.4 Klimtlte … Kernel : 3.4 … Rom: [ROM][7.1.1][UNOFFICIAL] LineageOS 14.1 - SM-T705 Apr 22 10:06:55 Kernel … https://github.com/exynos5420/androi...ung_exynos5420 … Device Tree … https://github.com/exynos5420/androi...msung_klimtlte Apr 22 10:51:40 Im trying to build the halium-boot but gives me this error. Apr 22 10:51:49 https://paste.ubuntu.com/p/dwnzZ5tv3m/ Apr 22 10:52:45 Try installing libncurses5-dev:i386 and libncurses5:i386 I think Apr 22 10:53:02 okay Apr 22 10:53:06 thanks Apr 22 10:54:34 @TuxThePenguin can you do few simple tests? Apr 22 10:55:00 I can once a configuration change I made finishes compiling Apr 22 10:55:05 install matching LineageOS and extract boot.img, take zImage you compiled, repack boot.img with your zImage, see if it boots Apr 22 10:55:15 if it still panicks, something is wrong with toolchain Apr 22 10:55:21 [Edit] if it still panics, something is wrong with toolchain Apr 22 10:55:30 Alright I'll try that in a bit Apr 22 10:57:30 Is there a place where I can download the 14.1 zips? They don't seem to be stored on the lineage servers anymore Apr 22 10:57:47 Owait nvm Apr 22 11:00:46 Oh as well as that there seems to be another thing I have forgotten Apr 22 11:01:08 My device is using the Oreo modem and bootloader, those may be causing issues as well Apr 22 11:02:13 not very likely, but can be, that's why generally it is adviced to have matching LineageOS install before starting Apr 22 11:02:47 Yeah, this came from a LOS 16 install (which because of treble is 100% compatible with LOS 15) Apr 22 11:08:34 It will take me a while to do the kernel swap test like you said, my internet is only about 4mbps down so it takes ages to download :( Apr 22 11:11:50 Oh neat fastboot works in the Nougat bootloader Apr 22 11:16:25 Ok so despite the proper bootloader and everything it still panics, Ill see if lineage boots with the kernel compiled by my system once it downloads Apr 22 11:38:10 installed libncurses5-dev:i386 and libncurses5:i386 still having "libncurses.so.5: cannot open shared object file: No such file or directory" Apr 22 12:04:39 Ok then it could just be libncurses5-dev and libncurses5 without the i386 but if it isn't someone else might know a solution Apr 22 12:10:31 On another note @NotKit when I tried putting the halium zImage into the Lineage boot image it came up with "error: failed writing 'new_boot.img': Bad address" Apr 22 12:10:47 which tool did you use? Apr 22 12:11:27 umkbootimg and mkbootimg Apr 22 12:11:48 I usually use bootimgtool -v qcom Apr 22 12:12:13 https://github.com/vianney/bootimgtool Apr 22 12:22:54 @thelowbudgetvlogger [installed libncurses5-dev:i386 and libncurses5:i386 still having "libncurses.so. …], Bro, of you are using Ubuntu 19.04 , believe me libncurses5 won't work... … So go back to 18.04 or find a solution first Apr 22 12:29:10 you can just use chroot Apr 22 12:31:52 Libncurses5 files are missing, so will it work using chroot? Apr 22 12:37:44 Ok so I put the zImage from the Halium boot image into the Lineage boot image using bootimgtool and it kernel panics the exact same way Apr 22 12:38:27 @NotKit Apr 22 12:38:48 hm, and kernel repo is from LineageOS sources? Apr 22 12:38:54 Yes Apr 22 12:39:05 Just reconfigured for UBports, but the panic is identical Apr 22 12:39:22 @TuxThePenguin [Just reconfigured for UBports, but the panic is identical], try with exact same config as in Lineage to make sure Apr 22 12:39:24 @Diago99 yeah, I figured it out in the ubuntu documentation. thanks Apr 22 12:39:34 backup your changes somewhere Apr 22 12:42:20 Should I just clone the Lineage kernel source and build it without Halium? Apr 22 12:43:05 Actually I don't know how to do that Apr 22 12:46:03 you can build with Halium first, but without config changes Apr 22 12:46:16 but second is also possible Apr 22 12:50:13 Alright I'm just downloading the unmodified kernel now Apr 22 13:29:10 guys i know it's probably been asked a thousand times before but i want to be 100% sure, does halium-install mess with the custom recovery on the phone because i don't remember how i originally installed it at all Apr 22 13:37:56 Nope. It doesn't Apr 22 13:46:05 ok thank you Apr 22 15:01:27 with Odin should i flash hybris-boot to BL ? Apr 22 15:04:47 anyone have an idea about this error? https://paste.ubuntu.com/p/XsBbvPk3YT/?fbclid=IwAR0owflHdCbYgDsDhHgrnC8LmgOGMKpaTn0ACpGEpOCwrLSbIfnTGt5ospg Apr 22 15:05:20 [Edit] anyone have an idea about this error? https://paste.ubuntu.com/p/XsBbvPk3YT/ Apr 22 15:39:31 put this in the folder (assuming it exists along with everything else the path describes) https://android.googlesource.com/platform/frameworks/base/+/marshmallow-release/packages/SettingsLib/common.mk. it fixed it for me Apr 22 15:42:47 will try that. thanks Apr 22 15:49:38 Guys hybris-boot.img flashes fine through TWRP but this is what halium-install gives me when i run the next step : https://paste.ubuntu.com/p/QpQRrTjS4s/ . Does someone know what could be wrong? Apr 22 15:50:19 then if i try to boot it just sends me back to recovery Apr 22 15:58:21 * Danct12[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/RpaFatSOiLOnuquRLXRzwbaz > Apr 22 15:58:47 i get this error on aarch64 device with armhf rootfs Apr 22 15:59:18 then just switch the rootfs Apr 22 16:02:26 There's no aarch64 rootfs for reference and plasma mobile Apr 22 16:02:33 at least, not officially supported Apr 22 16:02:41 oh Apr 22 16:03:01 Especially with the reference rootfs, it's only armhf Apr 22 16:42:16 @TuxThePenguin [Alright I'm just downloading the unmodified kernel now], When I did my port i just compiled without changing anything to see if I was missing anything, of course I knew it wouldn't boot correctly if at all, but it eliminates any questions of whether its the code or something I did, I think your issue could be with the cod Apr 22 16:42:16 e, or possibly a missing folder or something Apr 22 16:44:58 Like my device has a file missing in the bt-caf that breaks the compilation every time Apr 22 16:45:59 I removed the folder after all to fix this Apr 22 16:46:30 And my device has a duplicate camera folder Apr 22 18:12:25 gouster4 was added by: gouster4 Apr 22 18:13:12 Hi. Is possible halium as GSI image? Would be universal and can run on all modern devices. Apr 22 18:13:13 @gouster4 please consider changing your username and profile picture. These are not acceptable here. Apr 22 18:13:23 @UniversalSuperBox [@gouster4 please consider changing your username and profile picture. These are …], Sure i will Apr 22 18:13:47 root256 was added by: root256 Apr 22 18:13:53 I dont share that ideology, it was just funny for me. Yes wierd kind of humor Apr 22 18:14:40 @gouster4 [Hi. Is possible halium as GSI image? Would be universal and can run on all moder …], A prerequisite to this is support in Halium for Android 8/9 and support in its member distributions for Android 8/9 technologies. Neither exist. Apr 22 18:16:29 @UniversalSuperBox [A prerequisite to this is support in Halium for Android 8/9 and support in its m …], Sure. But afaik, halium is beaing updated for new android versions anyways. Slowly because it requires lot of time and development. … So halium GSI would be possible with pie or oreo halium? Apr 22 18:16:46 In future Apr 22 18:17:00 Sure, but it probably wouldn't do what you want it to and it won't be available to test for a long time. Apr 22 18:18:27 @UniversalSuperBox [Sure, but it probably wouldn't do what you want it to and it won't be available …], Got that point. Im not any leader or something likw that here. I like that guys are giving theyr free time to this project. Just wondering about its universality for future Apr 22 18:18:35 @UniversalSuperBox [Sure, but it probably wouldn't do what you want it to and it won't be available …], [Edit] Got that point. Im not any leader or something like that here. I like that guys are giving theyr free time to this project. Just wondering about its universality for future Apr 22 18:20:20 realMartinX3 was added by: realMartinX3 Apr 22 18:20:40 @realMartinX3 [realMartinX3 was added by: gouster4], Welcome mwin deutsche freund Apr 22 18:20:43 nice, we do nazi jokes at germany too with great fun Apr 22 18:20:48 @realMartinX3 [realMartinX3 was added by: gouster4], [Edit] Welcome mein deutsche freund Apr 22 18:20:51 I am a left party member Apr 22 18:20:54 @realMartinX3 [realMartinX3 was added by: gouster4], [Edit] Wilkommen mein deutsche freund Apr 22 18:21:05 "Willkommen mein deutscher Freund" Apr 22 18:21:17 @realMartinX3 [realMartinX3 was added by: gouster4], [Edit] Wilkommen mein deutscher freund Apr 22 18:21:22 Halium looks promising Apr 22 18:21:29 @realMartinX3 [Halium looks promising], Sure Apr 22 18:21:35 Its awesome project Apr 22 18:22:01 Just need to be built for our devices. Thats why i invited u here Apr 22 18:22:27 at the moment i am out of order with twrp, omnirom, aosp for the xperia tama plattform Apr 22 18:23:18 @realMartinX3 [at the moment i am out of order with twrp, omnirom, aosp for the xperia tama pla …], Forget omni and build halium. 😉 Apr 22 18:24:39 @gouster4 [Hi. Is possible halium as GSI image? Would be universal and can run on all moder …], it is kinda possible, but a) needs Android 8/9 support in Halium and UBPorts, which is not currently actively worked on b) it would still require custom kernel for each device Apr 22 18:25:06 @NotKit [it is kinda possible, but a) needs Android 8/9 support in Halium and UBPorts, wh …], B would be a problem with GSI concept Apr 22 18:25:14 c) UBPorts or other projects relying on it would need to get fixed for all the device quirks Apr 22 18:25:44 @gouster4 [B would be a problem with GSI concept], yeah, but nothing can be done with this, as some specific kernel options are required which are not enabled by Android Apr 22 18:26:14 @NotKit [yeah, but nothing can be done with this, as some specific kernel options are req …], Like in kernel cmdline? Apr 22 18:26:27 not cmdline, but kernel configuration Apr 22 18:26:45 With android Q underhood changes it maybe wouldnt be required Apr 22 18:26:53 [Edit] With upcomming android Q underhood changes it maybe wouldnt be required Apr 22 18:27:47 Qith android Q kernel would be mainlined if i understood it correctly Apr 22 18:27:48 I don't think they will drop SELinux and start using AppArmor, for example Apr 22 18:28:24 with Q vendors are forced to use kernel modules and we get APEX and logical partitions Apr 22 18:28:29 @NotKit [I don't think they will drop SELinux and start using AppArmor, for example], Selinux? Permissive can be done by cmdline. If it would be enought Apr 22 18:29:20 @gouster4 [Qith android Q kernel would be mainlined if i understood it correctly], that's far from that, if kernel would be mainlined, we wouldn't need Halium in the first place Apr 22 18:29:54 Hi all. … I have a device Moto X4 "Payton" … It currently supports Lineage OS 16.0 and was supported on 15.1 too. … Which Halium should I use and which Lineage OS should I use...? Apr 22 18:29:57 @NotKit [that's far from that, if kernel would be mainlined, we wouldn't need Halium in t …], Okey, i didnt understood it correctly Apr 22 18:30:16 @Kumar Abhishek [Hi all. … I have a device Moto X4 "Payton" … It currently supports Lineage OS 16.0 a …], Nougat Apr 22 18:31:07 @gouster4 [Selinux? Permissive can be done by cmdline. If it would be enought], no, for example, UBPorts relies on AppArmor for app isolation, support for it needs to be enabled in kernel during compilation, and we have other options required (like devtmpfs for udev, namespaces for LXC and so on) Apr 22 18:31:19 @Kumar Abhishek [Hi all. … I have a device Moto X4 "Payton" … It currently supports Lineage OS 16.0 a …], Los 14 Apr 22 18:32:22 @NotKit [no, for example, UBPorts relies on AppArmor for app isolation, support for it ne …], Can all those requirements be baypassed by modifying halium to not need that? Im sure it isnt easy, but is it possible? Apr 22 18:32:56 @gouster4 [Los 14], What if the device is unsupported on LOS 14..? Apr 22 18:33:05 @Kumar Abhishek [What if the device is unsupported on LOS 14..?], port LOS 14 then Apr 22 18:33:32 @gouster4 [Can all those requirements be baypassed by modifying halium to not need that? Im …], technically yes, but in practice, it would be too many compromises for someone to work on it Apr 22 18:33:39 @Kumar Abhishek [What if the device is unsupported on LOS 14..?], What if halium doesnt support los 15 and 16? Apr 22 18:33:41 @NotKit [port LOS 14 then], 😔😔😔😔😔😔 Apr 22 18:34:41 @gouster4 [What if halium doesnt support los 15 and 16?], Sarcasm won't help dude... Apr 22 18:34:42 @NotKit [technically yes, but in practice, it would be too many compromises for someone t …], Sure, i knew it wouldnt be easy. But maybe some day we would see halium GSI. 😂 Apr 22 18:35:12 @gouster4 [What if halium doesnt support los 15 and 16?], Be nice, please. There's no need for that. Apr 22 18:35:31 @Kumar Abhishek [Sarcasm won't help dude...], I mean, u need … 1. Port los 14 for your device … Or … 2. Port halium for los 15 or 16 … 1 is far far easyer Apr 22 18:36:01 They are working on update. But it requires loooooooooooooooot of development Apr 22 18:36:07 @gouster4 [I mean, u need … 1. Port los 14 for your device … Or … 2. Port halium for los 15 or 16 …], Thanks... Apr 22 18:36:14 @Kumar Abhishek [Thanks...], Good luck Apr 22 18:36:25 I cannot do any of those. Apr 22 18:36:27 😂 Apr 22 18:40:13 @UniversalSuperBox [Be nice, please. There's no need for that.], it doesn't sound like an attack in my eyes/ears Apr 22 18:40:52 in germany we call it a rhetorical question Apr 22 18:42:14 Sarcastically (rhetorically) replying to a common question is not welcoming to newcomers Apr 22 18:44:48 It's not how we work Apr 22 18:54:19 @UniversalSuperBox [Sarcastically (rhetorically) replying to a common question is not welcoming to n …], He asked what if his phone doesnt support los 14. This sarcastic answer/question does the job and explained that halium just dowsnt work with los 15 and 16. But i get it, it can be written nicer. Apr 22 18:54:33 @UniversalSuperBox [Sarcastically (rhetorically) replying to a common question is not welcoming to n …], [Edit] He asked what if his phone doesnt support los 14. This sarcastic answer/question does the job and explained that halium just doesnt work with los 15 and 16. But i get it, it can be written nicer. Apr 22 18:55:01 I'm not interested in just doing the job, the job should be done right. :) Apr 22 18:55:04 Now about that username Apr 22 18:57:38 @UniversalSuperBox [Now about that username], Sure. I will leave for a while. Anyways, i cannot help with development, as i dont know it, and also my device doesnt support los 14 like Kuram's. Getting it working is out of my knowedgle, sooo see u later next time. Once halium will support at leas Oreo, or i learn building. That time i wil Apr 22 18:57:38 l have changed username multipe times. 😉 Apr 22 18:58:07 @UniversalSuperBox [Now about that username], [Edit] Sure. I will leave for a while. Anyways, i cannot help with development, as i dont know it, and also my device doesnt support los 14 like Kuram's. Getting it working is out of my knowedgle, sooo see u later next time. Once halium will support at least Oreo, or i learn porting. That tim Apr 22 18:58:07 e i will have changed username multipe times. 😉 Apr 22 18:58:13 @UniversalSuperBox [Now about that username], [Edit] Sure. I will leave for a while. Anyways, i cannot help with development, as i dont know it, and also my device doesnt support los 14 like Kuram's. Getting it working is out of my knowedgle, sooo see u later next time. Once halium will support at least Oreo, or i learn porting los. That Apr 22 18:58:13 time i will have changed username multipe times. 😉 Apr 22 18:58:23 Bye. 😘 Apr 22 19:02:13 i hope we're not starting to remove "master/slave" from the IT because it may hurts ill feelings Apr 22 19:03:00 @realMartinX3 [i hope we're not starting to remove "master/slave" from the IT because it may hu …], That is completely off topic here @realMartinX3. If you're just looking to make people upset, this isn't the place for it. Apr 22 19:03:23 nono. you're the only one making people upset Apr 22 19:03:54 guys, you have your SODP chat for this kind of stuff, please change your tones, guuuuyys Apr 22 20:02:28 hı Apr 22 20:06:57 as-salamu alaykum Apr 22 20:19:27 @vanyasem [as-salamu alaykum], Alaikum salam Apr 22 20:25:52 @vanyasem [as-salamu alaykum], alaikum salam Apr 22 22:44:24 how can i reolve this error? https://paste.ubuntu.com/p/XsBbvPk3YT Apr 22 22:51:51 About a Halium GSI, only requiring a custom kernel would be nowhere near as bad since companies are legally required to release the kernel that they are using (even if they don't follow it 100% like they should), it would still require some amount of skill to port but it would be a lot faster and easier Apr 22 23:01:05 @NotKit [install matching LineageOS and extract boot.img, take zImage you compiled, repac …], Oh and I got the kernel I compiled and it booted, so I have no idea what to do now... Apr 22 23:06:10 (Photo, 1280x352) https://irc.ubports.com/WbTP0RyW.png When I check the kernel version this appears Apr 22 23:06:16 So evidently that worked Apr 22 23:06:29 But of course now it means that's not the problem... Apr 22 23:45:05 (Photo, 221x33) https://irc.ubports.com/tkAVLzo6.png Umm so I compiled halium with the unmodified kernel and an MTP device called "Failed to boot" appeared, it is not automatically rebooting, I'm trying to get telnet access now Apr 22 23:45:53 (Photo, 626x144) https://irc.ubports.com/YKKHaID4.png Umm Apr 22 23:47:52 Ill try building hybris recovery since that happens on every boot Apr 22 23:49:03 Does it show a MAC address in dmesg? Apr 22 23:49:16 It does, in fact with hybris-recovery I was just able to telnet it Apr 22 23:49:19 [Edit] It does, in fact with hybris-recovery I was just able to telnet in Apr 22 23:50:01 Congrats, you made a milestone, there should be a file called diagnosis.txt, that should tell you what to fix Apr 22 23:51:48 Well it's booted to recovery but I can't access the MTP filesystem Apr 22 23:52:36 Also diagnosis.log is just "No /proc/config.gz. Enable CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC" Apr 22 23:55:56 Yea, those 2 are the bare minimum for halium reference to boot, but that file will tell you everything thats wrong in initrc, until you start trying to get UT working at least Apr 22 23:56:55 Also if you have a successful boot, it might seem like it froze/locked up but just wait, my note 4 takes 20 minutes to boot hybris-boot Apr 22 23:57:09 Alright Im trying to make hybris-recovery with those two options set in the kernel configs Apr 22 23:57:18 Good luck Apr 22 23:57:22 20 minutes??? Apr 22 23:57:38 Whatd you do differently to get it to stop bootlooping? Apr 22 23:58:02 I just cloned the unmodified lineage kernel and am using the android n bootstack and modem Apr 22 23:58:35 @TuxThePenguin [20 minutes???], Yea, first time i thought it was locking or freezing, I only figured it out by leaving it alone and connected with dmesg open while I was doing some googling Apr 22 23:58:43 Wow Apr 22 23:59:25 Yea, I havent bothered to optimise it yet cause the graphics tests didnt work for me, probably part of why plasma didnt like my device Apr 22 23:59:40 Generally if this device panics it will reboot so thats useful Apr 22 23:59:57 Indeed Apr 23 00:00:12 Also Im hoping that because the graphics on this is relatively standard qualcomm GPU it should work Apr 23 00:00:57 Oh and because the device is unlocked the first thing it does is come up with a menu for what I want to do, similar to the fastboot menu but different at the same time Apr 23 00:01:09 That way I don't have to hold keys to get into recovery or fastboot Apr 23 00:03:28 Ah good the recovery booted with CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC Apr 23 00:03:33 Thats a relief Apr 23 00:06:47 Although when I tell it to continue it still seems to just power off Apr 23 00:14:46 Im just setting the next batch of options it recommends Apr 23 00:16:51 I have this error wha does this mean? … https://paste.ubuntu.com/p/4z3FcFv46q/ Apr 23 00:17:16 The error isn't in that text. Please post the full output of the command you ran to get that error. Apr 23 00:17:20 You will need to give more info than that Apr 23 00:20:22 this is the command Apr 23 00:20:23 https://paste.ubuntu.com/p/S2W4Ymsxp2/ Apr 23 00:22:11 before that I was having a common.mk error: … https://paste.ubuntu.com/p/XsBbvPk3YT … I added the common.mk with this code https://android.googlesource.com/platform/frameworks/base/+/marshmallow-release/packages/SettingsLib/common.mk … When I try to build that is the output error Apr 23 00:45:59 So even when I have no diagnosis.txt the device powers off when I tell it to continue booting Apr 23 00:54:09 Ok when I make halium-boot and flash that to the boot partition it boots and comes up with the device failed to boot mtp thing but now I can telnet in Apr 23 00:54:16 Tygerpro Apr 23 00:56:25 Halium-boot is slightly different from hybris-boot, but thats a good thing, did you install system.img and a rootfs.img file? Apr 23 01:01:04 Yes Apr 23 01:02:18 I manually made a rootfs image file by making a 2GB ext2 image, mounting it, extracting the tarball to it as root, umounting, img2simg and then fastboot flashing it (I used ext2 because that is supposedly what the script uses) Apr 23 01:05:22 Although according to TWRP that filesystem is invalid, hold on, I actually don't know why thats dead like that but Ill try a different way of getting the rootfs on the device Apr 23 01:22:49 Ok so I remade the filesystem correctly and it's still failing to boot Apr 23 01:24:55 Is there some way I can get the halium boot logs without rebooting the device? Apr 23 01:25:07 Tygerpro Apr 23 01:26:39 Reccomended way to get rhose installed is with JBBs script, and if you cant connect then no, youll have to reboot Apr 23 01:26:52 I can connect via telnet Apr 23 01:27:09 An MTP device appears called "Failed to boot" Apr 23 01:27:27 And telnet connects in the exact same was as hybris-recovery Apr 23 01:27:58 When I connect with telnet I get a busybox shell Apr 23 01:29:12 https://paste.ubuntu.com/p/MZBjkHXZkZ/ Apr 23 01:46:03 So this is funny, trying to continue the boot process from hybris-recovery not only kernel panics the phone, it brings the entire Linux USB stack on my laptop down, requiring a reboot to fix Apr 23 01:46:56 I mean it's not what I want the device to do Apr 23 01:47:02 But it's funny either way Apr 23 01:52:09 Thats ... interesting Apr 23 02:02:47 Any ideas? I'm kinda stumped here Apr 23 02:15:02 Im assuming that something is wrong with the kernel configs but I don't know for sure **** ENDING LOGGING AT Tue Apr 23 02:59:57 2019