Skip to content
Snippets Groups Projects
New look: Off

Tracking issue for HTC Droid DNA (dlx) port

    • Closed Imported Issue created by Administrator @root

    Created by: rschulman

    When attempting to build the kernel for htc-dlx (based on the m7 kernel from Lineage), pmbootstrap fails with numerous failures to find either arm-eabi-gcc or arm-eabi-ld. Full build log and copy of APKBUILD file are available in this gist.

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      The problem is, that the cross-compiler is hardcoded in your kernel's Makefile. It has a different name in postmarketOS, so this fails.

      The following patch fixes it (save it as Makefile-no-hardcoded-CROSS_COMPILE.patch or something like that inside the aports/linux-... folder and add it to your source= line inside the APKBUILD.)

      This fixes errors like the following (because our cross-compiler has a different name):
    /bin/sh: arm-eabi-ld: not found
    /bin/sh: arm-eabi-gcc: not found

--- a/Makefile
+++ b/Makefile
@@ -194,8 +194,6 @@ SUBARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
 export KBUILD_BUILDHOST := $(SUBARCH)
 ARCH       ?= $(SUBARCH)
 CROSS_COMPILE  ?= $(CONFIG_CROSS_COMPILE:"%"=%)
-ARCH       := arm
-CROSS_COMPILE  := arm-eabi-

 # Architecture as present in compile.h
 UTS_MACHINE    := $(ARCH)

      I have seen, that you have forked the kernel in your own repository and applied patches there. I strongly recommend not to do this, and use the original kernel source (the one you have forked) as base, and apply patch files on top of that, for the following reasons:

      • less fragmentation, we really have enough kernel forks in the Android world (the long time goal is to unify them with pmOS, not to have further forks)
      • it is much easier to see, what has been changed with single patch files
      • when you made a new patch, you/other people using your kernel don't need to download the whole source code archive again
      • the patch files can be re-used for other kernels (e.g. patches from the mako kernel were used for the hammerhead kernel)

      Upstreaming your changes to the kernel you have forked is of course the best solution here - but in the meantime, I suggest keeping the patches inside the aports folder.

      With that being said, thanks for making the bug report and working on this port :thumbsup:

      By * postmarketOS Bot on 2017-06-19T17:52:39

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      Thanks for putting up your current source here: https://github.com/rschulman/pmbootstrap/tree/dlx

      You've said on IRC, that it does not build yet. I will investigate this further tomorrow.

      By * postmarketOS Bot on 2017-06-19T21:31:04

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      I have merged your commit into the device-htc-dlx branch and fixed the linux-htc-dlx aport, the kernel compiles now :) Could you try to get your device to boot it?

      By * postmarketOS Bot on 2017-06-20T16:31:19

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: rschulman

      (Renamed the issue to reflect the broader effort to get HTC Droid DNA building)

      By * postmarketOS Bot on 2017-06-20T23:31:56

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: rschulman

      Current update: Kernel now builds successfully. Using pmbootstrap.py flasher boot hangs the device immediately. Fastboot still sees the device from my laptop but nothing I can do gets it to respond.

      If I try pmbootstrap.py flasher flash_kernel or flash_system I get FAILED (remote: not allowed) after writing 'SHLVL=1'.

      Googling implies that this error is related to not having an unlocked bootloader, but my HBOOT screen shows *** UNLOCKED *** across the top and S-OFF.

      By * postmarketOS Bot on 2017-06-21T03:08:48

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      I think you need to unlock your bootloader first:

      You basically use fastboot to ask for a code from your bootloader, then send that to that HTC site (you must register for that), then wait until they send you an e-mail with the unlock code (which takes 15 minutes or so). After that, you can use that code to unlock your device with fastboot. They have detailed instructions with images at least. I have done this process once.

      By * postmarketOS Bot on 2017-06-21T05:53:01

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      If that does not help it, what do the following commands say?

      • fastboot flashing get_unlock_ability
      • fastboot flashing unlock

      EDIT: And could you upload a photo of your device in the bootloader mode?

      By * postmarketOS Bot on 2017-06-21T05:55:23

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      ...last but not least, if we can't get it to work by unlocking fastboot, I think we should make a new flashing method based on exploiting the outdated Android kernels (#101 (closed)) :>

      By * postmarketOS Bot on 2017-06-21T06:56:21

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      Too bad we didn't get anywhere yet. By now we know a lot more about boot.img files. Please answer if you're willing to try out some more ideas, closing otherwise.

      By * postmarketOS Bot on 2017-09-02T22:20:08

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: rschulman

      No! I'm still here! Sorry, was just on vacation over the summer and had to turn away from this for a bit. If there's a new method that might work, I still have the dlx just lying around. Happy to give it a shot.

      By * postmarketOS Bot on 2017-09-06T01:16:51

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      No need to be sorry, this is a free time project :thumbsup: Cool that you want to try it again. What we did not try yet with the htc-dlx, but lead to success at least in one case.

      • use abootimg (packaged for Ubuntu/Debian, not yet for pmOS, but we can do that if you need it: #135 (closed)) to modify the known working boot.img file (from LineageOS/TWRP/whatever)
      • replace the initramfs and kernel with the postmarketOS kernel and initramfs
      • quick remainder on how to generate them: pmbootstrap install, then pmbootstrap export.

      By * postmarketOS Bot on 2017-09-06T19:59:06

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      In case you want to pick this up again, check out Troubleshooting:boot in the wiki.

      After asking @drebrez, who successfully ported the HTC desire, we have some new information: https://wiki.postmarketos.org/wiki/Troubleshooting:boot#Note_about_HTC_devices

      By * postmarketOS Bot on 2018-02-06T23:14:56

      Edited by Ghost User
    • Administrator moved to pmaports#100 (closed) · Imported

      moved to pmaports#100 (closed)

      By Bart Ribbers on 2018-09-18T17:24:06

    Please register or sign in to reply