| T42 | <Umeaman> https://xdaforums.com/t/guide-unlocking-the-bootloader-of-older-generation-huawei-devices.4729392/ doesn't work for you? (re @Narada55: I real want to insta...) | 08:25 |
|---|---|---|
| *** xmn_ is now known as xmn | 13:04 | |
| T42 | <morciatka> so, finally got droid-hal-init to do something but it still seems to fail later on during the process https://paste.opensuse.org/pastes/c4491d3c2d2c | 22:20 |
| T42 | <morciatka> it looks much more promising than it did before | 22:21 |
| T42 | <Mister_Magister> @morciatka to debug dhi use /usr/libexec/droid-hybris/system/bin/logcat | 22:26 |
| T42 | <Mister_Magister> also /usr/libexec/droid-hybris/system/bin/bootctl you need that | 22:27 |
| T42 | <Mister_Magister> no clue why it isn't in your image but i would check why | 22:27 |
| T42 | <morciatka> I can't run it like I can't run bootctl. I suppose it could be due to dhi not initializing properly yet but I'm obviously not certain on that (re @Mister_Magister: @morciatka to debug ...) | 22:30 |
| T42 | <Mister_Magister> no, you should be able to run it without dhi | 22:30 |
| T42 | <Mister_Magister> something is wrong with your setup | 22:30 |
| T42 | <Mister_Magister> plus it says the bootctl doesn't exist at that path | 22:30 |
| T42 | <morciatka> it exists | 22:31 |
| T42 | <morciatka> it literally is at that path and always has been there | 22:31 |
| T42 | <Mister_Magister> well script says something else | 22:32 |
| mal | @morciatka which android base was that again? | 22:32 |
| T42 | <morciatka> https://paste.opensuse.org/pastes/9d8f6a69d550 (re @Mister_Magister: well script says som...) | 22:34 |
| T42 | <morciatka> android 10, hybris17.1 | 22:34 |
| Mister_Magister | something is messed up | 22:35 |
| mal | did you remember to define android base version in droid-config spec? like this https://github.com/mlehtima/droid-config-fp5/blob/master/rpm/droid-config-fp5.spec#L7 but correct version of course | 22:35 |
| T42 | <morciatka> I have that yes | 22:36 |
| mal | hmm, ok | 22:36 |
| mal | that log shows that droid-hal-init timed out, not sure why | 22:36 |
| T42 | <morciatka> mal: I initially wanted to see logs from droid-hal-init but I'm not sure how to properly get to those | 22:39 |
| T42 | <morciatka> but I'll go to bed most likely for now haha | 22:39 |
| Mister_Magister | logcat like i mentioned | 22:39 |
| Mister_Magister | you can also strace it if you do the steps in the script manually and run it manually | 22:40 |
| T42 | <elros34> not logcat yet, you need dmesg without retelimiting enabled. BTW mind sharing what did you fixed: | 22:45 |
| T42 | <elros34> bootctl not found is probably misleading error -> linker issue but this is less important | 22:47 |
| T42 | <morciatka> basically took a break, completely nuked hadk and started from scratch. The weird issue with intermittent/stuck boots is gone and dhi started continuing after I removed that vendor.camera property from the vendor_property_contexts that is in the /vendor partition | 22:51 |
| T42 | <elros34> ah that duplicated entry | 22:54 |
| T42 | <morciatka> yes, that thing | 22:55 |
| mal | @morciatka might also be good to test starting droid-hal-init manually to see how it behaves, just run the commands from the script that starts it | 23:22 |
| mal | so first mask droid-hal-init to prevent it from starting at boot, then once in telnet in a running system you run the commands from the script | 23:23 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!