Ubuntu Touch on LG G6 (h870 model): call for testers
@Litcornes i'll give it a try...
@franky32 it was the rootfs the one you used worked for me as well... just that i selected the wrong one the first time i tried after downloading it
I saw this post and immediately bought a used LG G6. Unfortunately it was the LS993 model which can't fastboot. So was totally excited to install and test your port, @Guf ... but won't be able to.
</end of rant>
@enrolado I found this post where they said that you need to visit a support center. But I suppose the main issue might be Sprint firmware. Now, I don't know which hardware differences yours might have versus h870, they are probably firmware based.
Try to unlock it officially by requesting unlock.bin, then let's see what we can do
Hello! When i first started to hear about Ubuntu on Lg g6, I imedietly jumped to my mom's phone to try it out. I'm just a begginner and know absolutely nothing about how to install this OS. Can somebody help me?
I already unlocked my phone, and managed to install twrp (idk if I did it okay). My phone model is h870, EU version. I'd want to experience the Ubuntu OS at the earliest possible moment. Thanks!
Keneda last edited by
Is your mum ok for you wiping her phone out?
@Keneda yes, because I would trade with my phone (which is much better). But you didn't answered my question.
Keneda last edited by Keneda
@T0p0r Sorry i have a MX4 so can't tell...
What i can tell is if you want to use uTouch as a daily phone OS, you should choose a full supported device.
@vadikas I am dealing with the same situation and the patch did not resolve the issue. Have you succeeded in solving this?
@makeixo @walidham Fixed! I applied the patch for bullhead which suggested the same: to disable CONFIG_ANDROID_PARANOID and to enable SECURITY_ANDROID_GID_CAPABILITIES, but I hadn't done it well. With the help of @tanevanwifferen (who suggested what was wrong), we fixed it ... so let's go for other issues, now
Could you be more specific, please? I am porting the LG G4 and the patch did not resolve the issue. But then my port is also based on a different kernel version (the 3.10). Don't know how relevant the fix is for my version?