UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Is there support for SGP712 (karin_windy)?

    Scheduled Pinned Locked Moved Solved Sony Xperia Z4 Tablet (SGP771 & SGP712)
    6 Posts 2 Posters 529 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • X
      xys9000
      last edited by

      I tried installation on my karin_windy tablet, while installation seems to finish, it doesn't boot. I think it's because the kernel is compiled for the LTE model (SGP771) while I have WiFi model (SGP712) because I get the same issue when trying to boot TWRP linked in the other thread which I assume is for SGP771

      Is there any support for the wifi model?

      LakotaubpL 1 Reply Last reply Reply Quote 0
      • LakotaubpL
        Lakotaubp @xys9000
        last edited by

        @xys9000 If your device is not on here https://devices.ubuntu-touch.io/installer/ then yours will not work. Each port is very device specific. You could try contacting the porter for advice but the chances are very small.

        X 1 Reply Last reply Reply Quote 1
        • X
          xys9000 @Lakotaubp
          last edited by xys9000

          @lakotaubp Thank you for your reply, my device is on that list, it's Xperia Z4 Tablet WiFi only. Also in this post it says SGP712, I've been trying for the past 3 hours to get it to run, but nothing is helping.

          The porter is @Guf hopefully they're still around and can help

          1 Reply Last reply Reply Quote 0
          • X
            xys9000
            last edited by

            Looks like I was right about the kernel being compiled for the LTE model. I just built halium-boot.img from source and managed to get the Sony boot logo finally.
            Now I'm building system.img and hopefully it will work without issues 🙂

            1 Reply Last reply Reply Quote 0
            • X
              xys9000
              last edited by

              Update:
              It seems like it's working, except it doesn't mount the /system partition, so it doesn't fully boot. I ran mka hybris-boot to make sure fixup-mountpoints is being called and it seems like it does.

              Here's dmesg errors that I found interesting:

              [    4.868726] Begin: Running /scripts/nfs-top ... done.
[    4.868854] Begin: Running /scripts/nfs-premount ... done.
[    4.868983] Begin: Running /scripts/local-top ... done.
[    4.869080] Begin: Running /scripts/local-premount ... done.
[    4.887885] initrd: checking filesystem integrity for the userdata partition
[    4.890246] EXT4-fs (mmcblk0p42): couldn't mount as ext3 due to feature incompatibilities
[    4.890749] EXT4-fs (mmcblk0p42): couldn't mount as ext2 due to feature incompatibilities
[    4.895359] EXT4-fs (mmcblk0p42): recovery complete
[    4.895775] EXT4-fs (mmcblk0p42): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[    4.905681] initrd: checking filesystem for userdata took (including e2fsck) 0 seconds
[    4.910537] dumpe2fs 1.43.4 (31-Jan-2017)
[    4.914357] initrd: mounting /dev/mmcblk0p42
[    4.931388] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support!
[    4.931414] EXT4-fs (mmcblk0p42): couldn't mount as ext3 due to feature incompatibilities
[    4.931917] EXT4-fs (mmcblk0p42): Mount option "data=journal" incompatible with ext2
[    4.933713] EXT4-fs (mmcblk0p42): mounted filesystem with journalled data mode. Opts: discard,data=journal
[    4.935361] initrd: Halium rootfs is  
[    4.935828] initrd: mounting system rootfs at /halium-system
[    4.936728] initrd: WARNING: Android system image not found.
[    4.936802] initrd: mounting   (user mode)
[    4.937630] mount: can't find /halium-system in /proc/mounts
[    4.937934] initrd: mounting android system image (/tmpmnt/android-rootfs.img) ro, in /android-unknown (unknown mode)
[    4.937996] initrd: mounting android system image from system rootfs
[    4.939391] mount: mounting /halium-system/var/lib/lxc/android/android-rootfs.img on /android-unknown failed: No such file or directory
[    4.939625] initrd: WARNING: Failed to mount Android system.img.
[    4.942987] sed: /android-system/build.prop: No such file or directory
[    4.943219] initrd: Android system image API level is 0
[    4.943272] initrd: boot mode: halium
[    4.943738] initrd: Normal boot
[    4.944373] mount: mounting /halium-system on /root failed: Invalid argument
[    4.946508] mount: mounting /android-rootfs on /root/var/lib/lxc/android/rootfs failed: No such file or directory
[    4.953577] grep: /android-system/build.prop: No such file or directory
[    4.954103] initrd: WARNING: Didn't find a device name. Is the Android system image mounted correctly?
[    4.954152] initrd: device is unknown
[    4.954222] initrd: This rootfs does not have any writable-paths defined
[    4.954313] initrd: checking fstab /root/var/lib/lxc/android/rootfs/fstab* for additional mount points
[    4.956392] cat: can't open '/root/var/lib/lxc/android/rootfs/fstab*': No such file or directory
[    4.959316] initrd: moving Android system to /android/system
[    4.959975] mount: mounting /android-system on /root/android/system failed: Invalid argument
[    4.960331] Begin: Running /scripts/local-bottom ... done.
[    4.960474] done.
[    4.960612] Begin: Running /scripts/nfs-bottom ... done.
[    4.966009] mount: mounting /dev on /root/dev failed: No such file or directory
[    4.966675] mount: mounting /dev on /root/dev failed: No such file or directory
[    4.960856] Begin: Running /scripts/init-bottom ... done.
[    4.967877] mount: mounting /run on /root/run failed: No such file or directory
[    4.968706] run-init: current directory on the same filesystem as the root: Not a typewriter
[    4.968847] Target filesystem doesn't have requested /sbin/init.
[    4.969434] run-init: current directory on the same filesystem as the root: Not a typewriter
[    4.970076] run-init: current directory on the same filesystem as the root: Not a typewriter
[    4.970703] run-init: current directory on the same filesystem as the root: Not a typewriter
[    4.971367] run-init: current directory on the same filesystem as the root: Not a typewriter
[    4.972024] run-init: current directory on the same filesystem as the root: Not a typewriter
[    4.972949] No init found. Try passing init= bootarg.
[    4.975439] enable_store: android_usb: already disabled
[    5.201815] android_work: android_work: sent uevent USB_STATE=CONNECTED


              [    6.513015] rootfs / rootfs rw 0 0
[    6.513015] sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
[    6.513015] proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
[    6.513015] udev /dev devtmpfs rw,nosuid,relatime,size=1205140k,nr_inodes=301285,mode=755 0 0
[    6.513015] devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
[    6.513015] tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=282808k,mode=755 0 0
[    6.513015] /dev/mmcblk0p42 /root/userdata ext4 rw,relatime,discard,nodelalloc,data=journal 0 0
[    6.513015] /dev/mmcblk0p42 /root/android/data ext4 rw,relatime,discard,nodelalloc,data=journal 0 0
[    6.513015] /dev/mmcblk0p42 /root/android/cache ext4 rw,relatime,discard,nodelalloc,data=journal 0 0
[    6.513015] none /config configfs rw,relatime 0 0
[    6.526555] ########################## Beginning inject loop

              as you can see /dev/mmcblk0p44 which is the /system partition is not mounted.

              Any ideas?

              1 Reply Last reply Reply Quote 0
              • X
                xys9000
                last edited by

                Managed to get it to boot, looks like it has problems with configurations, copied the partition lines from kernel/sony/msm8994/arch/arm64/configs/kitakami_karin_defconfig to kernel/sony/msm8994/arch/arm64/configs/kitakami_karin_windy_defconfig

                it boots into ssh now, but still no screen or anything, anyway it's progress.

                1 Reply Last reply Reply Quote 0
                • X xys9000 has marked this topic as solved on
                • First post
                  Last post