**** BEGIN LOGGING AT Sat Mar 09 03:00:34 2019 Mar 09 08:08:40 Huh bad news for me, my new porting target did not boot into recovery anymore, so I tried reflashing without error but the same. fastboot format complains about partition type '' not supported. I also cannot reformat it to emmc - any ideas? Mar 09 08:09:55 hmm is there a way to restore the partition tableß Maybe this was just wiped or so Mar 09 08:10:43 does `fastboot boot something.img` still work? Mar 09 08:10:50 ah good point let me try Mar 09 08:11:22 No doesnt look like Mar 09 08:11:51 damn this never happened to me so far Mar 09 08:12:06 What is your device name? Mar 09 08:12:23 I was already in halium reference root ;) everything looked normal, and now this Mar 09 08:12:27 angler Mar 09 08:12:56 twrp was working like always Mar 09 08:12:59 Maybe you can download the original firmware and flash partition gtp.bin Mar 09 08:13:08 yep, but where to get it 😆 Mar 09 08:18:26 Ah I understand it comes from the stock firmware, there should be a prtition table inside right Mar 09 08:18:40 https://www.androidbrick.com/download/unbrick-nexus-6p-angler/ Mar 09 08:18:44 Here it is Mar 09 08:18:55 On XDA all links are down Mar 09 08:19:04 thx I try Mar 09 08:32:15 @Flohack, Is this the 6P? Mar 09 08:33:22 @Flohack, I'll get official firmware link from google Mar 09 08:34:07 @https://developers.google.com/android/images https://developers.google.com/android/images Mar 09 08:34:20 [Edit] @Flohack https://developers.google.com/android/images Mar 09 08:44:44 So `fastboot flash partition gpt_main0.bin` Mar 09 09:31:50 where repo link for download sources? Mar 09 09:35:21 @cruzer_blaze, in docs mb? Mar 09 09:36:56 for compiling Halium Mar 09 09:37:05 docs Mar 09 09:39:48 which branch? Mar 09 09:40:43 pfff `/bin/bash: mkbootimg: command not found` Mar 09 09:41:50 make mkbootimg Mar 09 09:41:52 @nanu_c, source build/envsetup.sh Mar 09 09:43:36 @dohniks, this was right Mar 09 09:43:54 👍 Mar 09 10:02:00 and this one … ``` File "build/tools/check_radio_versions.py", line 56 … print "*** Error opening \"%s.sha1\"; can't verify %s" % (fn, key``` Mar 09 10:03:31 [Edit] and this one … ``` File "build/tools/check_radio_versions.py", line 56 … print "*** Error opening \"%s.sha1\"; can't verify %s" % (fn, key``` … SyntaxError: invalid syntax Mar 09 10:06:58 @cruzer_blaze, halium-7.1 Mar 09 10:08:03 @nanu_c ive seen this before but i dont know what fixed it Mar 09 10:08:04 Fwd from mintyLeaf: ``` print "*** Error opening \"%s.sha1\"; can't verify %s" % (fn, key)``` Mar 09 10:23:32 okey the file `board-info.txt` doesn't exist Mar 09 10:26:30 [Edit] okey the file `board-info.txt` doesn't exist, but i don't know, i am new to everything Mar 09 10:46:18 @nanu_c, Seems like you're using Python 3, you must use Python 2 Mar 09 10:54:29 Giampy was added by: Giampy Mar 09 11:04:17 @Flohack, Just be careful not to reboot before flashing pbl and xbl or whatever is the equivalent of them is in nexus cuz those contain fastboot Mar 09 12:05:54 Azniel Basri was added by: Azniel Basri Mar 09 12:05:59 ..hi Mar 09 12:06:52 ..plez guied me for install ubuntu for my android samsung note5 Mar 09 12:09:11 Guide yourself https://docs.halium.org/en/latest/ Mar 09 12:28:09 Shifat3561 was added by: Shifat3561 Mar 09 12:28:18 (Photo, 1146x564) https://irc.ubports.com/5wXF0qFC.png http://t.cn/EIeMma3 Mar 09 12:28:18 (Photo, 1146x564) https://irc.ubports.com/DPLZKbXd.png hi Mar 09 12:29:18 SPAM Mar 09 12:29:53 @Shifat3561, @bhushanshah @UniversalSuperBox Mar 09 14:22:15 Willian de Oliveira was added by: Willian de Oliveira Mar 09 14:23:34 Ismael, after porting UT to my smartphone, can I make it avaiable for everyone? Mar 09 14:24:07 @Ismael, damn! get a permission denied on the partition table Mar 09 14:24:14 can it be low charge 😆 Mar 09 14:24:27 I mean, in the official website, there's a list of completely supported devices Mar 09 14:24:52 at any point, can my portabillity be uploaded there? Mar 09 14:25:43 Or is the emmc broken now :( Mar 09 14:26:08 I saw something about how to fix that Mar 09 14:26:10 One sec Mar 09 14:30:17 You mean EDL? Mar 09 14:36:13 dont know how that could help to fix a potentially broken flash Mar 09 14:37:16 https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948 Mar 09 14:37:20 Hard brick Mar 09 14:39:13 @Ismael, Well its not hard bricked, fastboot is ok Mar 09 14:39:21 just cannot flash anything anymore Mar 09 14:43:00 @Ismael, This restore the partitions Mar 09 14:43:25 Via com port Mar 09 14:44:25 In the screenshot in the link I sent he is using patch0.xml Mar 09 14:44:33 (Document) https://irc.ubports.com/ka7uuiZE.xml Mar 09 14:45:41 Which is in the firmware I have sent before and, if you read the code you'll see the gpt_main0 and gpt_backup0.bin partitions Mar 09 14:45:55 Which means it restores the partition table Mar 09 14:46:40 And this one? `hardware/qcom/bt-caf/libbt-vendor/src/hardware.c:40:10: fatal error: 'bt_hci_bdroid.h' file not found` It's a lineageos file Mar 09 14:47:03 And it's one of the last things :) `[ 97% 15099/15556]` Mar 09 14:47:36 @Ismael, So recovery works again... turns out it might be the bootloop of death.. Means I have to modify the system to only use the A53 which make it dead slow meh Mar 09 14:49:00 Or low charge... It was on the wrong USB port without power xD Mar 09 14:49:00 What did you do? Mar 09 14:49:11 To get recovery Mar 09 14:49:41 If it has edl it should be possible to get it back, does fastboot oem edl work? Mar 09 14:49:55 (Sticker, 512x512) https://irc.ubports.com/kIBpdKgz.webp Mar 09 14:50:10 @Ismael, Flash the one with A57 cores disabled patch, but battery is now over 25% so it might be this: https://chimicles.com/google-nexus-6p-battery-early-shutoff-bootlooping-class-action-investigation/ Mar 09 14:50:20 the phone is used, and the battery is worse than expected Mar 09 14:50:53 I try now to put back the one with all cores enabled. Mar 09 14:53:19 yeah its that. meh Mar 09 14:54:27 So need to keep battery always over 60% lol Mar 09 17:55:05 parvonsanthan was added by: parvonsanthan Mar 09 17:55:37 Hey peeps Mar 09 17:55:52 I'm using a Moto G5sPlus Mar 09 17:56:13 And I wanna use Halium dist. In it .... Mar 09 17:56:53 Sadly, I can't find any ports for this phone. Only Moto G5 is shown in the list.... Mar 09 17:57:07 Any way that I can get Ubuntu Touch ? Mar 09 17:57:27 MSM8953... it should be relatively straightforward to port it to booting and graphics state Mar 09 17:58:01 do you have LineageOS 14.1 for it though? Mar 09 17:58:45 Lineage OS 16, yes. Mar 09 17:59:14 no, 14.1 in particular Mar 09 18:00:00 Unofficial only bro Mar 09 18:00:08 By XDA developers Mar 09 18:01:00 did they provide device tree source code? Mar 09 18:05:08 Nop Mar 09 18:05:13 PM me bro Mar 09 18:07:32 Okay so what to do next Mar 09 18:07:52 @Ismael, . Mar 09 18:09:00 the issue is that there is no LineageOS 14.1 device tree for that device, and we have no support newer one Mar 09 18:09:08 [Edit] the issue is that there is no LineageOS 14.1 device tree for that device, and we have no support for newer ones Mar 09 18:14:33 @parvonsanthan, I am working on that Mar 09 18:14:47 on G5S Plus or just G5? Mar 09 18:14:57 g5s plus Mar 09 18:15:21 did you find LOS14.1 tree for that? Mar 09 18:15:32 Yes, there are some Mar 09 18:16:05 i got that far `mka systemimage` build until [ 97% 15099/15556] Mar 09 18:16:16 and it faild at bt-caf Mar 09 18:17:35 https://gist.github.com/nanu-c/67a1b477faab12c9025921b4b2a4a977 Mar 09 18:19:40 + modificationas Mar 09 19:35:15 Someone can help me with fastboot recoverymode and adb? Mar 09 19:36:08 @nanu_c, What's the problem Mar 09 19:37:14 i am in fastboot and now i want to use the halium-install-standalone script. For that i need to get in recovery mode but adb doesn't find the phone Mar 09 19:37:45 @nanu_c, You can't use adb in fastboot, you need to boot twrp Mar 09 19:39:10 okey and i need to do `fastboot flash twrp.img` ? Mar 09 19:39:32 Fastboot flash recovery twrp.img Mar 09 19:39:44 Or just fastboot boot twrp.img Mar 09 19:40:50 Nah he should flash it ;) Mar 09 19:41:01 You will need recovery quite often Mar 09 19:41:37 Especially when replacing stuff a lot bc it wont work Mar 09 19:41:58 Also its the only way to turn off the phone Mar 09 19:42:09 And disconnect any charger before you turn off Mar 09 19:42:32 now it asks for a password to encrypt Mar 09 19:42:40 Skip it ;) Mar 09 19:43:49 Let's see if SSH works on Moto G5 Mar 09 19:44:04 Motorola doesn't like halium SSH :/ Mar 09 19:44:26 `pushing rootfs and... ` :) Mar 09 19:45:20 [Edit] Motorola don't like halium SSH :/ Mar 09 19:54:16 okey it doesnt answer on that port, can i ping the device? Mar 09 19:54:37 `connect to host 10.15.19.82 port 22: Network is unreachable` Mar 09 19:55:33 dmesg says ` SerialNumber: halium-initrd telnet 192.168.2.15` Mar 09 19:57:04 and `register 'rndis_host' at usb-0000:00:14.0-4, RNDIS device, 62:6a:ea:c2:3b:ba` Mar 09 19:58:09 okey i follow the docs Mar 09 20:07:08 @nanu_c, the good thing is your kernel works and doesnt bootloop Mar 09 20:07:12 thats already much Mar 09 20:07:14 @nanu_c, You have the telnet interface based on this so ssh won't work yet Mar 09 20:10:08 ```nanu@nanu:~/src/ut/sanders/halium$ ssh phablet@192.168.2.15 … ssh: connect to host 192.168.2.15 port 22: Connection refused … nanu@nanu:~/src/ut/sanders/halium$ telnet 192.168.2.15 … Trying 192.168.2.15... … telnet: Unable to connect to remote host: Connection refused … nanu@nanu:~/src/ut/sanders/halium$ ping -b 192.168.2.15 … PIN Mar 09 20:10:08 G 192.168.2.15 (192.168.2.15) 56(84) bytes of data. … 64 bytes from 192.168.2.15: icmp_seq=1 ttl=64 time=0.286 ms``` Mar 09 20:11:14 [Edit] ping works, telnet not, ssh not Mar 09 20:25:42 the first time i do telnet it's telling `closed by foreign host.` second time i am refused :). @Flohack perfect time to do a porting session Mar 09 21:40:24 powderedtoastman9000 was added by: powderedtoastman9000 Mar 09 21:49:20 Is there a reason why the repo tool doesn't sync all non-device-specific repos like it used to with -b halium-7.1 ? it used to auto add all the repos except device kernel and vendor Mar 09 21:51:12 I'm just getting a new build tree. I can tell that the repo too itself has changed but did I do something wrong or is the procedure requirements more involved than it used to be, or did I do something wrong? Mar 09 21:52:12 like 2 years ago the same commands would have given me a full build tree minus kernel device and vendor Mar 09 21:52:35 What error shows the terminal? Mar 09 21:53:28 none, it only synced audiofingerglue, devices, halium-boot, hybris-boot, and libhybris Mar 09 21:54:06 Have you tried repo `sync --force-sync`? Mar 09 21:54:23 No, good idea I'll try that Mar 09 21:55:04 nope, no difference Mar 09 21:55:41 Could you send me a screenshot? Mar 09 21:55:51 I don't understand what is happening Mar 09 21:55:53 Or a phoro Mar 09 21:55:58 [Edit] Or a photo Mar 09 21:57:14 it's just syncing an incomplete build tree, I know how to fix it but I have done this before and every time before now the commands and docs I am using now did the job without me adding manually to the repo manifests Mar 09 22:00:17 I could solve the problem by adding to the manifests things I find by looking through all the GitHub halium repos, or by just git cloning them that way, but this was done automatically before so I'm asking if there's a reason that I'm doing something wrong or has it changed? Mar 09 22:00:58 Look at your manifest file Mar 09 22:01:06 the manifests that you got unedited used to have the whole build tree minus vendor kernel and device, which I added Mar 09 22:01:14 @powderedtoastman9000, probably you use wrong manifest for repo init Mar 09 22:01:20 @powderedtoastman9000, [Edit] probably you used wrong manifest for repo init Mar 09 22:01:47 @NotKit, I used the repo init command from the official halium docs Mar 09 22:02:14 https://github.com/Halium/android/blob/halium-7.1/default.xml - manifest includes all the repos though Mar 09 22:02:25 were there any errors that it could not sync the rest? Mar 09 22:02:30 I guess I should just stop complaining and make the manifest complete Mar 09 22:02:35 no errors Mar 09 22:03:02 as you see, the manifest is complete Mar 09 22:05:41 I will look more at the manifests... they're different now with the version of repo I got from the Ubuntu repos which is the instructions in the docs. Mar 09 22:13:52 would this problem happen if I used the devices/setup tool with no halium repo or manifest already made for the device? Mar 09 22:14:18 I'm trying to make for herolte Mar 09 22:27:14 @powderedtoastman9000 do you see any repo in the manifest that is not cloned onto your disk? that should not happen, unless you have something in `.repo/local_manifests/*` with a `` inside … if however you think a repo is missing from the manifest, you can add it to your `local_manifests` Mar 09 22:29:14 all the repos are in the manifests. Like I don't get why it's not working, because last time I was doing this everything worked the way it should have and nothing has changed in regards to how I did it Mar 09 22:29:52 It's just annoying because now I'm looking line by line at the manifests and git cloning each one into place Mar 09 22:30:06 ok please don't do that to yourself ;) Mar 09 22:30:30 try remove the repo tool from the ubuntu repos and download the one straight from google, it's a script that will bootstrap itself Mar 09 22:30:55 Okay, I'll try that Mar 09 22:31:12 then remove the `.repo` folder from your tree, since you could have some inconsistencies in there. beware that you will have to re-sync everything if you do that, ~30-50gb Mar 09 22:32:04 my folder doesn't have a .repo folder. this repo tool made a global one in my home folder for all projects, which I never seen in the past Mar 09 22:33:20 that is very odd indeed. yeah so use the upstream google one and you should be fine Mar 09 22:34:09 ```mkdir ~/bin … curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo … chmod a+x ~/bin/repo``` Mar 09 22:34:19 the official one is also using that ~/.repo folder Mar 09 22:34:37 check `.repoconfig` and nuke it Mar 09 22:34:48 okay Mar 09 22:35:14 also your shell env variables, anything unusual? Mar 09 22:37:09 and move `~/.repo` to `.backup_repo`, maybe repo checks for the presence of that folder and then uses it Mar 09 22:37:57 nothing that should affect this, just variables that are specific to stuff that isn't anyhow related and is named in a way I would highly doubt this is taking into account... yes I just nuked ~/.repo I have a fast enough connect that a full sync should be under 40 mins Mar 09 22:39:30 looking through the source code of repo, it should really not be doing anything complicated Mar 09 22:39:54 ok and you have the correct repo in your $PATH, right? Mar 09 22:40:41 yeah, and it's displayed with "which repo" which means the one I downloaded from Google is the one being used Mar 09 22:41:01 great Mar 09 22:41:13 is it syncing correctly now? Mar 09 22:41:17 I just don't get why this isn't working, but I deleted .repo and have begun trying again Mar 09 22:41:39 and more importantly, is it creating `~/.repo` again? Mar 09 22:42:11 it always did the download portions right, but the syncing working tree part usually goes through a few iterations of 0-100 not one line of 221 that syncs right away Mar 09 22:42:15 I'll check Mar 09 22:42:32 if all else fails, you can supply `--repo-dir` to repo Mar 09 22:42:40 no, it's now in my build tree folder Mar 09 22:43:26 hopefully the issue was using the Ubuntu repos copy, if this works I'll advise you to change the porting docs to not apt-get it Mar 09 22:44:29 mind you it could have been something messed up inside your .repo folder, once you start handling with as much plumbing and as much symlinking and what-have-you as repo does, it can mess up your filesystem layer Mar 09 22:44:54 moving gigabytes of symlinked block data back and forth is testing the limits of filesystems Mar 09 22:45:27 repo is really strechting the limits of git Mar 09 22:45:29 yeah, but I just remember over 2 years ago doing the exact same thing and it working perfectly, and I followed the docs exactly like I did this time Mar 09 22:46:57 I'm going to be porting UT to some devices, so I need to make the kernels compatible with the platform they use which is halium 7.1 based Mar 09 22:59:35 Worked this time. Whoever manages the docs, change the porting instructions to not use apt-get and use the method of AOSP docs to get and use it instead Mar 09 22:59:37 terrible showerthought: could we get ubuntu touch compiled entirely against libbionic instead of getting bionic drivers to work with glibc? Mar 09 23:00:17 well, you could if you wanted to Mar 09 23:00:44 the question should be whether or not it's the right thing to spend time on Mar 09 23:01:38 @VeryOriginalUsername, you could, but it would eliminate just one layer of compatibility needed (libhybris) and won't help with the rest Mar 09 23:02:36 well that would open up some possibilities for devices (such as my f...beloved nicki) that have trouble getting hybris android container running Mar 09 23:03:17 container is not related to hybris, SFOS runs Android bits side by side with real system for example Mar 09 23:04:36 what is the problem with nicki? Mar 09 23:05:14 kernel 3.4, I guess? Mar 09 23:05:16 yes Mar 09 23:05:24 and kernel-side broken-iness Mar 09 23:05:42 what is the problem you run to? Mar 09 23:05:45 kernel is dirty as heck due to it being done by foxconn and not sony Mar 09 23:05:53 [Edit] what is the problem you run into? Mar 09 23:06:23 let me see if I can find the dmesg Mar 09 23:06:46 Fwd from mariogrip: proc_ns_follow_link Mar 09 23:06:46 (Document) https://irc.ubports.com/bGGja9n7.null Mar 09 23:09:26 did you attempt to diff it with Nexus 5? Mar 09 23:09:50 yeah, the n5 kernel seems to be much newer Mar 09 23:10:04 and patching it would require me to dig back a few years worth of commits Mar 09 23:11:17 welp... if you're desperate enough, you could try to get LXC 3.0 in UBPorts and run with shared proc namespace Mar 09 23:11:50 I've achieved some (very little) progress with mainline on this device, maybe one day ™️ it'll run ubp hybris-less Mar 09 23:12:07 [Edit] I've achieved some (not enough) progress with mainline on this device, maybe one day ™️ it'll run ubp hybris-less Mar 09 23:12:13 It looks like despite having official builds of Lineage there's no los kernel in their git repos, so I have to start with Samsung's TouchWiz kernel Mar 09 23:12:27 @powderedtoastman9000, check lineage.dependencies Mar 09 23:12:32 or cm.dependencies Mar 09 23:21:20 I don't see anything. there's a kernel for another device using the same chip but it's a tablet so it's probably missing data and phone capabilities Mar 09 23:22:54 I have the 7.0 kernel from samsung, and the hardware stuff didn't break between 7 and 7.1 Mar 09 23:23:07 that seems like the best thing to start with Mar 09 23:25:43 there's unofficial lineage builds I could fork but I don't trust them because if they were respectable and done properly they would be official builds Mar 09 23:30:01 Oh, tablet I did see kernel for... it has lte, that makes it viable Mar 09 23:31:26 @powderedtoastman9000, could you give the codename of device? Mar 09 23:32:35 herolte it's the s7 exynos canadian version, which is the same hardware as international version Mar 09 23:33:52 sm-g930w8 Mar 09 23:34:27 https://github.com/LineageOS/android_kernel_samsung_universal8890/tree/cm-14.1 - this is the kernel LineageOS uses Mar 09 23:34:55 thanks! Mar 09 23:35:02 (from https://github.com/LineageOS/android_device_samsung_herolte/blob/cm-14.1/BoardConfig.mk#L19) Mar 09 23:35:42 yeah I already found vedor and device trees but thanks for helping me find the kernel Mar 09 23:39:10 okay, getting that kernel, then I can start the real work after I take a nap **** ENDING LOGGING AT Sun Mar 10 02:59:56 2019