<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Is there support for SGP712 (karin_windy)?]]></title><description><![CDATA[<p dir="auto">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</p>
<p dir="auto">Is there any support for the wifi model?</p>
]]></description><link>https://forums.ubports.com/topic/8350/is-there-support-for-sgp712-karin_windy</link><generator>RSS for Node</generator><lastBuildDate>Mon, 18 May 2026 18:13:58 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/topic/8350.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 25 Nov 2022 19:01:40 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Is there support for SGP712 (karin_windy)? on Sat, 26 Nov 2022 17:16:37 GMT]]></title><description><![CDATA[<p dir="auto">Managed to get it to boot, looks like it has problems with configurations, copied the partition lines from <code>kernel/sony/msm8994/arch/arm64/configs/kitakami_karin_defconfig</code> to <code>kernel/sony/msm8994/arch/arm64/configs/kitakami_karin_windy_defconfig</code></p>
<p dir="auto">it boots into ssh now, but still no screen or anything, anyway it's progress.</p>
]]></description><link>https://forums.ubports.com/post/68695</link><guid isPermaLink="true">https://forums.ubports.com/post/68695</guid><dc:creator><![CDATA[xys9000]]></dc:creator><pubDate>Sat, 26 Nov 2022 17:16:37 GMT</pubDate></item><item><title><![CDATA[Reply to Is there support for SGP712 (karin_windy)? on Sat, 26 Nov 2022 14:32:48 GMT]]></title><description><![CDATA[<p dir="auto">Update:<br />
It seems like it's working, except it doesn't mount the /system partition, so it doesn't fully boot. I ran <code>mka hybris-boot</code> to make sure <code>fixup-mountpoints</code> is being called and it seems like it does.</p>
<p dir="auto">Here's dmesg errors that I found interesting:</p>
<pre><code>[    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

</code></pre>
<pre><code>[    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

</code></pre>
<p dir="auto">as you can see <code>/dev/mmcblk0p44 </code> which is the <code>/system</code> partition is not mounted.</p>
<p dir="auto">Any ideas?</p>
]]></description><link>https://forums.ubports.com/post/68683</link><guid isPermaLink="true">https://forums.ubports.com/post/68683</guid><dc:creator><![CDATA[xys9000]]></dc:creator><pubDate>Sat, 26 Nov 2022 14:32:48 GMT</pubDate></item><item><title><![CDATA[Reply to Is there support for SGP712 (karin_windy)? on Sat, 26 Nov 2022 02:42:08 GMT]]></title><description><![CDATA[<p dir="auto">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.<br />
Now I'm building system.img and hopefully it will work without issues <img src="https://forums.ubports.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=bc7965752a7" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
]]></description><link>https://forums.ubports.com/post/68664</link><guid isPermaLink="true">https://forums.ubports.com/post/68664</guid><dc:creator><![CDATA[xys9000]]></dc:creator><pubDate>Sat, 26 Nov 2022 02:42:08 GMT</pubDate></item><item><title><![CDATA[Reply to Is there support for SGP712 (karin_windy)? on Fri, 25 Nov 2022 22:08:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/lakotaubp" aria-label="Profile: lakotaubp">@<bdi>lakotaubp</bdi></a> Thank you for your reply, my device is on that list, it's Xperia Z4 Tablet WiFi only. Also in <a href="https://forums.ubports.com/topic/4351/porting-ubuntu-touch-ubports-to-karin-sony-xperia-z4-tablet-sgp771-and-karin_windy-sony-xperia-z4-tablet-sgp712">this post</a> it says SGP712, I've been trying for the past 3 hours to get it to run, but nothing is helping.</p>
<p dir="auto">The porter is <a class="plugin-mentions-user plugin-mentions-a" href="/user/guf" aria-label="Profile: Guf">@<bdi>Guf</bdi></a> hopefully they're still around and can help</p>
]]></description><link>https://forums.ubports.com/post/68658</link><guid isPermaLink="true">https://forums.ubports.com/post/68658</guid><dc:creator><![CDATA[xys9000]]></dc:creator><pubDate>Fri, 25 Nov 2022 22:08:22 GMT</pubDate></item><item><title><![CDATA[Reply to Is there support for SGP712 (karin_windy)? on Fri, 25 Nov 2022 21:25:25 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/xys9000" aria-label="Profile: xys9000">@<bdi>xys9000</bdi></a> If your device is not on here <a href="https://devices.ubuntu-touch.io/installer/" target="_blank" rel="noopener noreferrer nofollow ugc">https://devices.ubuntu-touch.io/installer/</a> 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.</p>
]]></description><link>https://forums.ubports.com/post/68654</link><guid isPermaLink="true">https://forums.ubports.com/post/68654</guid><dc:creator><![CDATA[Lakotaubp]]></dc:creator><pubDate>Fri, 25 Nov 2022 21:25:25 GMT</pubDate></item></channel></rss>