**** BEGIN LOGGING AT Mon Sep 17 03:00:00 2018 Sep 17 03:00:22 like 30 seconds after it reboots? how would i do that without stopping it at pre-boot Sep 17 03:00:27 https://gist.github.com/UniversalSuperBox/547b89ae177d24aaa723b61f87a405e7 Sep 17 03:01:34 ok, i dont know how to use that, im a noob Sep 17 03:02:02 Toss it in /etc/init with the name something.conf Sep 17 03:02:10 oh ok Sep 17 03:02:11 And wait for it to do its magic Sep 17 03:02:18 On an Upstart OS Sep 17 03:02:30 I should probably make one for systemd Sep 17 03:02:43 But that's not going to happen tonight Sep 17 03:02:44 ok, which ones are upstart? Sep 17 03:02:48 UT Sep 17 03:03:06 ok, so ut edge and the script? Sep 17 03:03:12 Yeah Sep 17 03:03:19 I really must go to sleep though Sep 17 03:03:28 Words aren't quite making sense any more Sep 17 03:03:33 ok, me too, 11pm here Sep 17 03:06:49 i work overnight, and am willing tohelp when i can Sep 17 03:09:54 compiling now, heres hoping Sep 17 03:51:50 new dmesg: โ€ฆ https://paste.ubuntu.com/p/9KfXBfmN2M/ Sep 17 04:00:23 i have added that to my device and i am still getting the console error. Hmmmm. wonder if i have my mounts wrong Sep 17 04:03:20 at this point i am stuck. If anyone wants to look at my dmesg, please do. There might be something else wrong while i am trying to boot into ut Sep 17 06:52:53 @kaibsora, Try to add "console= ecc" bere https://github.com/halium-cancro/android_device_xiaomi_cancro/blob/dc50af3650a8e94807565b62ddd0af643669661e/BoardConfig.mk#L49 Sep 17 06:53:11 @kaibsora, [Edit] Try to add "console= ecc" here https://github.com/halium-cancro/android_device_xiaomi_cancro/blob/dc50af3650a8e94807565b62ddd0af643669661e/BoardConfig.mk#L49 Sep 17 07:08:47 I did put console=ram there and that's what I got Sep 17 07:18:22 And do I need to rebuild the system.img as well or just the boot img? @Mattia990 Sep 17 07:25:04 @kaibsora, Try both Sep 17 07:25:28 Good day to everyone! Guys I need some help with building hallium for my ASUS Zenfone 2 Laser. I cannot create manifest .xml file for my model. I know that some guy do port Halium (almost mine - Z00L, I hame Z00LD, there are no difference between them, LOS images (and build LOS Wikis) are the same) and Plasma Mobile for my phone - https://forum.xda-developers.com/zenfone-2-laser/development/rootfs-plasma-mobile-caf-t3731962 I even found his EAX device tree - h Sep 17 07:25:28 ttps://github.com/Halium/android_device_asus_Z00L Sep 17 07:26:20 but I can't use his manifest sample because some repos he uses there are not exist anymore Sep 17 07:27:48 and I cant use his prebuild images because he got hybris_boot.img, not halium_boot one. Sep 17 07:47:28 *Coughs* Sep 17 07:47:29 see if there are forks of his somewhere @ubports_bot Sep 17 07:48:01 Sorry, my vendor tree was deleted last time Sep 17 07:48:15 If I remember correctly, there are no forks Sep 17 09:11:56 theimpulson, first of all - thanks for your work, it is awesome. Sep 17 09:12:33 https://gist.github.com/theimpulson/bc9df81ecb8cb6d623e032dcefcfd0c1 - your Gist page with how-to is not aviable too ( Sep 17 09:14:51 And this repos: deadlyindian/android_device_asus_Z00L and Sep 17 09:14:51 TheMuppets/proprietary_vendor_asus Sep 17 09:14:53 too Sep 17 09:15:01 its a pity ^(( Sep 17 09:17:33 unfortunatly I can't even try your work - there are no android-tools-fsutils which is requred in your install script. Standart script halium-install-standalone works? but system do not boot at all - bootlogo ASUS Powered by Android and broken USB connection. looks like bootloader do not start Sep 17 09:18:12 sorry missted some style in my last msg Sep 17 09:19:04 Standart script halium-install-standalone works, but system do not boot at all - bootlogo ASUS Powered by Android and broken USB connection. looks like bootloader do not start Sep 17 09:19:43 how can I communicate with @ubports_bot? Sep 17 09:23:57 lol, there are no android-tools-fsutils only in Debian 9 Stretch. This package existing in Sid, wheezy, Jessie and even in buster.... Sep 17 12:16:07 @Semn, What are you trying? Sep 17 13:24:41 unfortunately, im still getting this: [ 5.247402] [1: run-init: 760] [c1] run-init: opening console: No such device Sep 17 13:25:19 ive tried adding console= ram, console= ecc and console= null to my boardconfig cmdline Sep 17 13:25:29 console=/dev/tty0 Sep 17 13:25:46 (without space!) Sep 17 13:25:47 to the boardconfig? Sep 17 13:25:50 yeys Sep 17 13:25:52 *yes Sep 17 13:26:02 alright. and i dont have to mka clean do i? Sep 17 13:26:13 no Sep 17 13:26:24 didnt think so. Sep 17 13:27:24 and i feel like this is a stupid question, but how tf do you reboot in telnet? Sep 17 13:27:35 (To recovery) Sep 17 13:32:28 no idea about that tho, i dont think it is even available Sep 17 13:32:40 do it manually Sep 17 13:32:41 didnt think so lol Sep 17 13:32:43 i do Sep 17 13:35:24 @kaibsora, My suggest wasn't console=ecc but console=what you want๐Ÿ˜‚๐Ÿ˜‚ Sep 17 13:35:48 idk what it wanted tho Sep 17 13:38:50 do i have to remake the systemimage as well Sep 17 13:38:51 ? Sep 17 15:58:33 kde plazma-- > not install lightdm? **** ENDING LOGGING AT Tue Sep 18 03:00:00 2018