**** BEGIN LOGGING AT Wed Nov 27 02:59:57 2019
Nov 27 03:11:24 <ubptgbot> <Alva> (Photo, 582x749) https://irc.ubports.com/xESw90vj.png 非小号Mytoken推特脸书增关注，菠菜棋牌推广霸屏强推，微信电报增粉私聊、推广，交易所上币投票，交易所平台账号代实名，如有需要请联系:➡️    @yx226688
Nov 27 03:12:01 <ubptgbot> <Antoine9298> ^ @admin
Nov 27 07:10:59 <ubptgbot> EmilSMN was added by: EmilSMN
Nov 27 07:18:19 <ubptgbot> <EmilSMN> Hello.  I studied the instructions far and wide, but did not understand what to do if in fstab.device instead of the expected / dev / block / bootdevice / by-name / system, there is nothing like this.  There is only content in the form of emmc @ system (for example).  The phone didn’t work either.  entering ls / dev / block / bootdevice /
Nov 27 07:18:20 <ubptgbot>  by-name / -al gives the error "there is no such directory."  Can you tell me what to do?
Nov 27 07:23:02 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/fR0nu0Kt.png
Nov 27 07:23:41 <ubptgbot> <ultravioletnanokitty> @EmilSMN [Hello.  I studied the instructions far and wide, but did not understand what to …], post the content of fstab.device?
Nov 27 07:23:52 <ubptgbot> <ultravioletnanokitty> `using code tags` please
Nov 27 07:25:04 <ubptgbot> <EmilSMN> (Document) https://irc.ubports.com/nfVY4rZ9.txt
Nov 27 07:27:26 <ubptgbot> <ultravioletnanokitty> @EmilSMN [<reply to media>], oh, well, i see what you mean.... i feel like i've seen that format before but i think i'll have to leave the suggestions to others. i suspect it might be a manufacturer-specific implementation
Nov 27 07:28:41 <ubptgbot> <ultravioletnanokitty> @EmilSMN [Hello.  I studied the instructions far and wide, but did not understand what to …], what's the output of ls on each level of that path?
Nov 27 07:29:02 <ubptgbot> <ultravioletnanokitty> for example … /dev … /dev/block … /dev/block/<bootdevice>
Nov 27 07:29:22 <ubptgbot> <EmilSMN> yes
Nov 27 07:30:12 <ubptgbot> <ultravioletnanokitty> @ultravioletnanokitty [for example … /dev … /dev/block … /dev/block/<bootdevice>], so what do you get if you run `ls -al /dev/block/<bootdevice>/ ?
Nov 27 07:30:18 <ubptgbot> <ultravioletnanokitty> @ultravioletnanokitty [for example … /dev … /dev/block … /dev/block/<bootdevice>], [Edit] so what do you get if you run `ls -al /dev/block/<bootdevice>/` ?
Nov 27 07:31:20 <ubptgbot> <ultravioletnanokitty> @ultravioletnanokitty [for example … /dev … /dev/block … /dev/block/<bootdevice>], [Edit] so what do you get if you run `ls -al /dev/block/`?
Nov 27 07:31:32 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/gjBv7UvQ.png
Nov 27 07:31:56 <ubptgbot> <ultravioletnanokitty> @EmilSMN [Hello.  I studied the instructions far and wide, but did not understand what to …], where are you getting "bootdevice" anyway
Nov 27 07:31:59 <ubptgbot> <ultravioletnanokitty> @EmilSMN [Hello.  I studied the instructions far and wide, but did not understand what to …], [Edit] where are you getting "bootdevice" anyway?
Nov 27 07:32:09 <ubptgbot> <ultravioletnanokitty> it should just be /dev/block
Nov 27 07:32:23 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/xE5IxJRc.png
Nov 27 07:36:05 <ubptgbot> 淑钧 was added by: 淑钧
Nov 27 07:40:20 <ubptgbot> <EmilSMN> There is no "bootdevice" and for some reason I can not find it anywhere.
Nov 27 07:48:06 <ubptgbot> <ultravioletnanokitty> @EmilSMN [There is no "bootdevice" and for some reason I can not find it anywhere.], well it actually shouldn't be part of the path
Nov 27 07:48:18 <ubptgbot> <ultravioletnanokitty> where did you read "bootdevice"?
Nov 27 07:53:53 <ubptgbot> <EmilSMN> @ultravioletnanokitty [where did you read "bootdevice"?], There is no bootdevice anywhere. As far as I understand, LG Magna partitions are mounted somehow differently. So I'm trying to understand how they are mounted and through what. Since there is no "bootdevice" but there is a "platform" and there are "mtk-msdc.0" and "mtk-msdc.1". But
Nov 27 07:53:53 <ubptgbot>  as I understand it, this is not it either, it fails to find out about the mount sections.
Nov 27 09:12:13 <ubptgbot> <NotKit> @EmilSMN ls -la /dev/block platform
Nov 27 09:12:21 <ubptgbot> <NotKit> [Edit] @EmilSMN ls -la /dev/block/platform
Nov 27 09:32:22 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/fEPThr1I.png
Nov 27 09:33:12 <ubptgbot> <NotKit> ls -la /dev/block/platform/mtk-mscd.1/by-name
Nov 27 09:33:51 <ubptgbot> <NotKit> but it seems internal paritions are on mtk-mscd.0
Nov 27 09:34:07 <ubptgbot> <NotKit> [Edit] ls -la /dev/block/platform/mtk-msdc.1/by-name
Nov 27 09:34:16 <ubptgbot> <NotKit> [Edit] but it seems internal partitions are on mtk-mscd.0
Nov 27 09:35:09 <ubptgbot> <NotKit> you may check /proc/dumchar_info, /proc/mtd and /proc/emmc
Nov 27 09:35:20 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/fA7A4G4Y.png
Nov 27 09:36:09 <ubptgbot> <Mattia990> @EmilSMN [<reply to media>], Try to use readlink … Ex. "readlink /deb/block/platform/mtk-mscd.0/by-name/system"
Nov 27 09:36:16 <ubptgbot> <Mattia990> @EmilSMN [<reply to media>], [Edit] Try to use readlink … Ex. "readlink /dev/block/platform/mtk-mscd.0/by-name/system"
Nov 27 09:37:04 <ubptgbot> <EmilSMN> @EmilSMN [<reply to media>], Please note that this is not what mountpoints require, because it leads to mmcblk1p1, but it is a microSD card
Nov 27 09:38:52 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/K8wIw0Ev.png This command does not work
Nov 27 09:40:37 <ubptgbot> <Mattia990> @Mattia990 [Try to use readlink … Ex. "readlink /dev/block/platform/mtk-mscd.0/by-name/system"], Try readlink -f ....
Nov 27 09:41:27 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/FsEpv7ru.png
Nov 27 09:46:41 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/mRxAPrgd.png
Nov 27 09:48:37 <ubptgbot> <NotKit> @EmilSMN what you need to figure out is which partition number is what somehow
Nov 27 09:48:45 <ubptgbot> <NotKit> system and userdata are easy to get from mounts
Nov 27 09:57:00 <ubptgbot> <EmilSMN> @NotKit [system and userdata are easy to get from mounts], Unfortunately not in the case of LG Magna.  I’ve been trying for the second day.
Nov 27 10:02:02 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/OvWt0Qzh.png This is it?  How do you understand no?
Nov 27 10:24:23 <ubptgbot> <NotKit> @NotKit [you may check /proc/dumchar_info, /proc/mtd and /proc/emmc], ^
Nov 27 10:49:18 <ubptgbot> <EmilSMN> @NotKit [^], What should this team look like?  enter ls -al /dev/block/platform/mtk-msdc.0/ proc / mtd?  Or something else?
Nov 27 11:15:14 <ubptgbot> <NotKit> @EmilSMN cat /proc/dumchar_info
Nov 27 11:15:18 <ubptgbot> <NotKit> cat /proc/emmc
Nov 27 11:15:22 <ubptgbot> <NotKit> cat /proc/partitions
Nov 27 11:15:27 <ubptgbot> <NotKit> (some of those may not exist)
Nov 27 11:24:37 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/fI6zt9jK.png
Nov 27 11:35:43 <ubptgbot> <NotKit> well, you have the names now
Nov 27 12:44:17 <ubptgbot> <intel777> Hmm, today started with Halium won't even boot properly. It just saying  … ```[    6.429790] mkdir: can't create directory '/root/android': Read-only file system … [    6.430207] mkdir: can't create directory '/root/userdata': Read-only file system … [    6.430836] mount: mounting /tmpmnt on /root/userdata failed: No such file or directo
Nov 27 12:44:17 <ubptgbot> ry … ```  … etc. Can anyone help me with this?  … https://del.dog/fegnulolof.txt
Nov 27 12:46:08 <ubptgbot> <intel777> I've already tried to completely recompile systemimage, but this has no effect
Nov 27 12:52:59 <ubptgbot> <EmilSMN> @NotKit [well, you have the names now], Apparently I'm slowly thinking.  What exactly from this write in fixup-mountpoints?
Nov 27 12:57:09 <ubptgbot> <vanyasem> Well can you see how others have done it and figure it out?
Nov 27 12:57:18 <ubptgbot> <vanyasem> I find it very annoying that you’re not even trying
Nov 27 12:59:59 <ubptgbot> <EmilSMN> @vanyasem [I find it very annoying that you’re not even trying], Me too ... that you are not trying to read.  At the command mka mkbootimg, I have a mount error of / boot and / data.  But how exactly to register them in fixup-mountpoints if there is no / boot among the partition names?
Nov 27 13:06:29 <ubptgbot> <intel777> so add them into fstab.qcom in yours device tree
Nov 27 13:07:40 <ubptgbot> <intel777> in my case there was no /boot in fstab.qcom that I originally used, so I just simply googled for fstab.qcom of any device that relatively close to mine and copied parameters from there
Nov 27 13:14:11 <ubptgbot> <EmilSMN> @intel777 [in my case there was no /boot in fstab.qcom that I originally used, so I just si …], In my case, this is LG Magna.  A smartphone that does not understand the commands / dev / block / bootdevice (re-read the messages) and so on.  It seems that we figured out that the data that needs to be entered into fixup-mountpoints lies alon
Nov 27 13:14:11 <ubptgbot> g the path dev / block / platform / mtk-msdc.0 / but from the data only mmcblk0p are in a row with a different number without names.  and separately there are names, without the necessary ones, for the error in mounting which bash swears: by the command mka mkbootimg
Nov 27 13:17:53 <ubptgbot> <intel777> Can you provide device tree link that you are using?
Nov 27 13:20:29 <ubptgbot> <EmilSMN> @intel777 [Can you provide device tree link that you are using?], https://github.com/xcore995/android_device_lg_my90ds/blob/cm-14.1/rootdir/root/fstab.magna
Nov 27 13:21:38 <ubptgbot> <EmilSMN> Just in case, I remind you - the error looks like this https://pastebin.com/6u9AVCsU
Nov 27 13:26:22 <ubptgbot> <intel777> Ok, let's try this.  … Install this app https://play.google.com/store/apps/details?id=me.kuder.diskinfo
Nov 27 13:26:32 <ubptgbot> <intel777> (Photo, 720x1280) https://irc.ubports.com/ZTPrrLqn.png
Nov 27 13:26:32 <ubptgbot> <intel777> (Photo, 720x1280) https://irc.ubports.com/OTHGDejo.png
Nov 27 13:26:44 <ubptgbot> <intel777> Set settings like on this screens
Nov 27 13:39:31 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/04Yzwzmj.png
Nov 27 13:39:31 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/zo9PyKDf.png
Nov 27 13:39:31 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/xI4w5020.png
Nov 27 13:39:32 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/0NiZf6lL.png
Nov 27 13:49:48 <ubptgbot> <intel777> Can you, please do  … ```su … cd / … ls -l ``` … ?
Nov 27 13:53:15 <ubptgbot> <EmilSMN> (Photo, 720x1280) https://irc.ubports.com/2gJX9tAN.png
Nov 27 13:53:52 <ubptgbot> <NotKit> I think there is enough input now
Nov 27 13:54:45 <ubptgbot> <NotKit> just write info into fixup-mountpoints to convert paths from fstab.magna into real block devices
Nov 27 13:55:22 <ubptgbot> <intel777> He haven't even come to fixup-mountpoints part
Nov 27 13:55:43 <ubptgbot> <intel777> compiller complains about absence of /data in fstab
Nov 27 13:56:45 <ubptgbot> <intel777> Firstly, try to remove declaration of second /data that got f2fs filesystem in fstab
Nov 27 13:57:34 <ubptgbot> <intel777> f2fs is not supported by halium anyways, and it also can confuse compiller
Nov 27 13:59:24 <ubptgbot> <intel777> data in 0p11 if I'm not wrong
Nov 27 14:00:45 <ubptgbot> <EmilSMN> @intel777 [data in 0p11 if I'm not wrong], Yes, for sure, I was wrong.  but is the command correct?
Nov 27 14:01:32 <ubptgbot> <intel777> you can simply use /dev/block/mmcblk0p11
Nov 27 14:02:14 <ubptgbot> <intel777> but boot partition will be challanging as there is no mount point
Nov 27 14:02:53 <ubptgbot> <intel777> but, AFAIK halium not really care about /boot, so try to skip it
Nov 27 14:03:37 <ubptgbot> <intel777> @intel777 [Firstly, try to remove declaration of second /data that got f2fs filesystem in f …], do this and try to compile again
Nov 27 14:04:22 <ubptgbot> <intel777> as error message states … ```There should be a one and only one device entry for! … ```  … so one, and only one
Nov 27 14:10:54 <ubptgbot> <EmilSMN> Nothing has changed, the errors are the same
Nov 27 14:13:57 <ubptgbot> <Qusay362> Kind of a stupid question is halium-boot the boot.img in the out folder
Nov 27 14:15:54 <ubptgbot> <EmilSMN> @Qusay362 [Kind of a stupid question is halium-boot the boot.img in the out folder], out/target/product/*/ … * codename device
Nov 27 14:15:59 <ubptgbot> <Qusay362> Yea
Nov 27 14:17:16 <ubptgbot> <Qusay362> So I compiled everything with no build error and wanna install UT so I need halium-boot and I'm confused cause there is no .IMG file with the same name only systemimage,DT,boot so I assume that bootimg is the halium boot
Nov 27 14:17:44 <ubptgbot> <Qusay362> @EmilSMN [out/target/product/*/ … * codename device], My path is out/target/product/hltechn
Nov 27 14:20:29 <ubptgbot> <EmilSMN> @Qusay362 [So I compiled everything with no build error and wanna install UT so I need hali …], Look for hybris-boot.img according to the instructions, it seems to be so called
Nov 27 14:44:33 <ubptgbot> <gagamali> hello everyone, does phone has any response when flash hybris-boot.img and without system.img rootfs
Nov 27 14:45:16 <ubptgbot> <gagamali> I just got reboot in few seconds again and again.
Nov 27 14:45:38 <ubptgbot> <gagamali> No USB action
Nov 27 14:53:01 <ubptgbot> <intel777> @gagamali [hello everyone, does phone has any response when flash hybris-boot.img and witho …], yeah, it generaly must give you telnet if everythink was done right but there is no system.img/rootfs.img
Nov 27 14:53:24 <ubptgbot> <intel777> or if there was done enough to boot
Nov 27 14:54:26 <ubptgbot> <intel777> @EmilSMN [Nothing has changed, the errors are the same], try adding /data /data emmc defaults defaults at the end of fstab
Nov 27 14:54:44 <ubptgbot> <intel777> @EmilSMN [Nothing has changed, the errors are the same], [Edit] try adding  … ``` … /data     /data     emmc     defaults     defaults … ```` …  at the end of fstab
Nov 27 14:54:47 <ubptgbot> <intel777> @EmilSMN [Nothing has changed, the errors are the same], [Edit] try adding  … ```/data     /data     emmc     defaults     defaults``` …  at the end of fstab
Nov 27 14:55:57 <ubptgbot> <intel777> I believe script is searching for /data declaration exactly as `/data` but gets `/emmc@usrdata`
Nov 27 14:56:34 <ubptgbot> <intel777> so you will add another /data to link on /data that mounted at /emmc@usrdata
Nov 27 14:56:59 <ubptgbot> <intel777> @gagamali [hello everyone, does phone has any response when flash hybris-boot.img and witho …], [Edit] yeah, it generaly must give you telnet if everything was done right but there is no system.img/rootfs.img
Nov 27 14:58:16 <ubptgbot> <intel777> @gagamali [No USB action], follow this instructions to find whats happend  … https://docs.halium.org/en/latest/porting/debug-build/dmesg.html
Nov 27 16:05:23 <ubptgbot> <intel777> @intel777 [Hmm, today started with Halium won't even boot properly. It just saying  … [    6. …], Hmm, interestly enough is that  … ```[    6.429790] mkdir: can't create directory '/root/android': Read-only file system … ```  … can be easily fixed by  … ```mount -o remount,rw /root``` … through recovery-telnet that opens up
Nov 27 16:09:25 <ubptgbot> <intel777> where is that script located?
Nov 27 16:15:49 <ubptgbot> <Qusay362> @EmilSMN [Look for hybris-boot.img according to the instructions, it seems to be so called], umm...lol my mistake didn't compile the halium-boot i'm trying to port UT so i skipped hybris-boot
Nov 27 16:20:24 <ubptgbot> <Qusay362> tried to build again sucessful then ran the ubuntu kernel check config redited then error can't figure out what's the problem from this output ,
Nov 27 16:21:27 <ubptgbot> <Qusay362> https://pastebin.com/UVd93zk7
Nov 27 16:24:10 <ubptgbot> <intel777> @intel777 [where is that script located?], nvm, found instructions in halium/halium-boot/README.md
Nov 27 16:40:43 <ubptgbot> <intel777> Oh jesus crist
Nov 27 16:41:08 <ubptgbot> <intel777> I just realized that I was doing halium-boot instead of working hybris-boot
Nov 27 16:59:42 <ubptgbot> <intel777> So I finally booted halium reference rootfs
Nov 27 16:59:52 <ubptgbot> <intel777> and sucessfully ssh into it
Nov 27 17:00:29 <ubptgbot> <intel777> but now lxc won't start because it can't find init.rc of android … ```Feb 11 16:28:02 localhost.localdomain lxc-start[1221]: sed: can't read /var/lib/lxc/android/rootfs/init.*.rc: No such file or directory … Feb 11 16:28:02 localhost.localdomain lxc-start[1221]: sed: can't read /var/lib/lxc/android/rootfs/init.rc: No such file or directo
Nov 27 17:00:29 <ubptgbot> ry``` … Anyone know where I can find them?
Nov 27 20:33:30 <ubptgbot> <ankaos> https://paste.ubuntu.com/p/W9QdqB7bJP/ CONFIG_KERNEL_LZO? how to fix this error?
Nov 27 20:34:37 <ubptgbot> <intel777> Add it to kernel config, maybe?
Nov 27 20:35:08 <ubptgbot> <intel777> CONFIG_KERNEL_LZO=y
Nov 27 20:38:22 <ubptgbot> <ankaos> @intel777 [CONFIG_KERNEL_LZO=y], Not fix
Nov 27 21:07:31 <ubptgbot> 孔豪淡 was added by: 孔豪淡
Nov 28 02:48:37 <ubptgbot> <EmilSMN> I had such a question - the fstab file is in the root directory of the smartphone.  But for some version of the firmware, for some reason, it has a different name.  In the firmware that is now on the smartphone, it is called fstab.goldfish, and in the firmware that stood before it, there was a fstab.qcom file but the contents of these fil
Nov 28 02:48:37 <ubptgbot> es are the same.  It differs from what lies in the source.  In the sources in the fstab.magna file, mount points (as I understand it) are written as emmc @ name, and in files that want the root directory of the firmware, the contents of fstab files have other mount points and most often looks like "/ dev / block / bootdevice / by-  name Can anyone
Nov 28 02:48:37 <ubptgbot> explain why this is?
Nov 28 02:52:41 <ubptgbot> <EmilSMN> I ask this because if you use the fstab file from the sources in the assembly, the process stops with an error indicating problems with the mount points.  But if you use the contents of the fstab file that lies in the root directory of the smartphone, then the process also contains mount point errors, but the process does not end with an
Nov 28 02:52:41 <ubptgbot> error, but continues and ends successfully, after which you can build hibrys-boot.img but since  I did not fully understand the mounting points until I tried to install it.
**** ENDING LOGGING AT Thu Nov 28 02:59:57 2019