hi there.
one of the issues of dual booting android with ubuntu touch is not being able to access your files in the other OS.
in ubuntu :
the android files (or /sdcard/ content) are located at /userdata/media/0 while your files are at ~/. make a mount point and bind these two directories: (i used adb for this)
Code:
$adb shell
#su - phablet
$cd ~
$sudo mkdir android
$sudo mount --bind /userdata/media/0 ~/android
$sudo chmod 775 android
$sudo chown phablet:phablet android
after this you'll be able to access your data with ubuntu's file manager
in android :
ubuntu files are at /data/user-data/phablet/ while your files are at /data/media/0. unfortunately only the app that performs the mount (for me terminal emulator) can see the files i don't know why... more info @ http://forum.xda-developers.com/showthread.php?t=2065856
and as you can see stickmount doesn't support nexus 4. so if you've got something else give it a try
Code:
mount -o bind /data/user-data/phablet /data/media/0/ubuntu
you can always access your ubuntu files using a file explorer with root permissions.
notes:
i've got a nexus 4 but it should work for all supported devices.
Tasssadar said:
If you're using MultiROM, update to the latest version and replace /userdata/media/0 with /android/realdata/media/0
Click to expand...
Click to collapse
MTN_HD2 said:
hi there.
one of the issues of dual booting android with ubuntu touch is not being able to access your files in the other OS.
in ubuntu :
the android files (or /sdcard/ content) are located at /userdata/media/0 while your files are at ~/. make a mount point and bind these two directories: (i used adb for this)
Code:
$adb shell
#su - phablet
$cd ~
$sudo mkdir android
$sudo mount --bind /userdata/media/0 ~/android
$sudo chmod 775 android
$sudo chown phablet:phablet android
after this you'll be able to access your data with ubuntu's file manager
in android :
ubuntu files are at /data/user-data/phablet/ while your files are at /data/media/0. unfortunately only the app that performs the mount (for me terminal emulator) can see the files i don't know why... more info @ http://forum.xda-developers.com/showthread.php?t=2065856
and as you can see stickmount doesn't support nexus 4. so if you've got something else give it a try
Code:
mount -o bind /data/user-data/phablet /data/media/0/ubuntu
you can always access your ubuntu files using a file explorer with root permissions.
notes:
i've got a nexus 4 but it should work for all supported devices.
Click to expand...
Click to collapse
hi
i have a problem doing this it says that the directory /userdata/media/0 does not exist
line that the command does give out : mount : special device /userdata/media/0 does not exist
btw i am using stable saucy but i will try the newes version now
any suggestions with that ?
chris1005 said:
hi
i have a problem doing this it says that the directory /userdata/media/0 does not exist
line that the command does give out : mount : special device /userdata/media/0 does not exist
btw i am using stable saucy but i will try the newes version now
any suggestions with that ?
Click to expand...
Click to collapse
It's "/host/media/0"
woernsn said:
It's "/host/media/0"
Click to expand...
Click to collapse
This gave me same error as before
what i forgot to say is that i am using Multiboot for the Teamwin recovery / this app to install Ubuntu Touch
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Also i tried to find the folder with cd and ls but i couldnt find it.
but thanks for your support
chris1005 said:
This gave me same error as before
what i forgot to say is that i am using Multiboot for the Teamwin recovery / this app to install Ubuntu Touch
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Also i tried to find the folder with cd and ls but i couldnt find it.
but thanks for your support
Click to expand...
Click to collapse
mmmh.. did you try searching for something, that is on the SD with 'find' via adb shell?
helped me
Sent from my Nexus 4 using Tapatalk
chris1005 said:
This gave me same error as before
what i forgot to say is that i am using Multiboot for the Teamwin recovery / this app to install Ubuntu Touch
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
Also i tried to find the folder with cd and ls but i couldnt find it.
but thanks for your support
Click to expand...
Click to collapse
MultiROM uses a different partition layout. Maybe @Tasssadar can tell you more about that. (I would be interested as well.)
nikwen said:
MultiROM uses a different partition layout. Maybe @Tasssadar can tell you more about that. (I would be interested as well.)
Click to expand...
Click to collapse
Ok thanks you for the support
chris
chris1005 said:
Ok thanks you for the support
chris
Click to expand...
Click to collapse
If you get any information on that topic, please share it here.
nikwen said:
If you get any information on that topic, please share it here.
Click to expand...
Click to collapse
I wrote Tasssadar if he has a solution for the problem i will post this
chris1005 said:
I wrote Tasssadar if he has a solution for the problem i will post this
Click to expand...
Click to collapse
Thank you very much.
@chris1005: Install MultiROM v22b, go to recovery -> Advanced -> MultiROM -> List ROMs -> *ubuntu* -> Re-patch init and boot to Ubuntu. The "real" /data will be mounted under /android/realdata, so use folder /android/realdata/media/0/ instead of /userdata/media/0.
Tasssadar said:
@chris1005: Install MultiROM v22b, go to recovery -> Advanced -> MultiROM -> List ROMs -> *ubuntu* -> Re-patch init and boot to Ubuntu. The "real" /data will be mounted under /android/realdata, so use folder /android/realdata/media/0/ instead of /userdata/media/0.
Click to expand...
Click to collapse
Thanks for the support
but i still get the same error
I installed Multirom v22 i could not find v22b i searched on the offical forum thread and the Multirom manager.
Sorry if i am blind >.<
Tried it several times to Re-patch init and install the latest available Multirom and recovery
I will try different Ubuntu release see what this does
chris1005 said:
Thanks for the support
but i still get the same error
I installed Multirom v22 i could not find v22b i searched on the offical forum thread and the Multirom manager.
Sorry if i am blind >.<
Tried it several times to Re-patch init and install the latest available Multirom and recovery
I will try different Ubuntu release see what this does
Click to expand...
Click to collapse
This one is v22b: http://d-h.st/djy
The changelog says that it's just been implemented in v22b: http://forum.xda-developers.com/showthread.php?p=48508468#post48508468
@Tasssadar: What's about the Nexus 4? Will we be able to mount the partition in Ubuntu as well?
Why did I think this is in N5 section? Oo Anyway, it's v22a for mako and flo and v22b for grouper and hammerhead.
@MTN_HD2: Can you please add info about MultiROM to the first post? Something along the lines of "If you're using MultiROM, update to the latest version and replace /userdata/media/0 with /android/realdata/media/0". Thank you.
Tasssadar said:
Why did I think this is in N5 section? Oo Anyway, it's v22a for mako and flo and v22b for grouper and hammerhead.
@MTN_HD2: Can you please add info about MultiROM to the first post? Something along the lines of "If you're using MultiROM, update to the latest version and replace /userdata/media/0 with /android/realdata/media/0". Thank you.
Click to expand...
Click to collapse
Thank you very much.
Thank you very much just saw the update in multirom manager
Sent from my Nexus 4 using xda app-developers app
nexus 7 2013 LTE (4.4.2)
Hi
I have nexus 7 4g (v4.4.2 )
I install multiROM v22b with Ubuntu touch r206(default)
But phone not active (3g/4g)
Can you help me?
mohammadhossein said:
Hi
I have nexus 7 4g (v4.4.2 )
I install multiROM v22b with Ubuntu touch r206(default)
But phone not active (3g/4g)
Can you help me?
Click to expand...
Click to collapse
This is normal. Its still in a testing phase. I have had the same issue, even on the latest versions still. You're not doing anything wrong.
-wardawgmalvicious
Rooted N5/N7 2nd Gen
MultiROM TWRP
Franco Kernel
Stock 4.4.2 infused with GB
Ubuntu Touch
-Sent using Tapatalk
Have a look at this post in the Nexus 4 thread: http://forum.xda-developers.com/nex...ouch-14-10-utopic-unico-t2324683/post53850263
You can now finally use your Android music and pictures in Ubuntu.
Do you know how to get the folders mount at each boot ?
Related
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Tip from aled99 to edit without linux.
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
Some files that are already edited:
CoreDroid HD 0.4 edited by ricola7
Desire_hd2 system.ext2 file
HD2ONE 0.3.5 system.ext2
JDMS 1.62
MDJ HD v4.6
MDJ rEVOlution 2.3 rootfs.img
NexusHD2-FRG83D v1.8 from nzxtneo
Superram 1.5 from letama
Builds that already work with magldr:
DL DesireZ v2.2 from dandiest
HD2 Gingerbread/CyanogenMod7 from copenhagen
Is this a method to boot a NAND Rom from SD Card without flashing?
blax123 said:
Is this a method to boot a NAND Rom from SD Card without flashing?
Click to expand...
Click to collapse
No it boots the sd builds from this subforum. Not the nand builds.
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
izzy spun said:
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
Click to expand...
Click to collapse
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
buzz killington said:
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Click to expand...
Click to collapse
thanks.. so i must use linux? any tools available in win?
buzz killington said:
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Click to expand...
Click to collapse
can you elaborate on this please.
can you give a step by step.
i am real interested in trying this.
thanks in advance.
Anthonayy said:
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
Click to expand...
Click to collapse
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
vista1984 said:
thanks.. so i must use linux? any tools available in win?
Click to expand...
Click to collapse
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
WOOZ!E said:
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Dude, it has nothing to do with WP7, You boot Android from MAGLDR not WP7. So you would either use a different SD card to boot into Android BEFORE booting windows or you would partition your SD card in a way that it allows you to use it for WP7 and Android at same time.
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
asdfg2010 said:
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
Click to expand...
Click to collapse
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
buzz killington said:
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
Click to expand...
Click to collapse
I try but not successful
windows ext2 editing
buzz killington said:
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Click to expand...
Click to collapse
I think you can edit an ext2 image with windows using the method in post #4 from this thread: http://forum.xda-developers.com/showthread.php?t=808169
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
I've tried editing the file and it seemed to save the changes, but I haven't tried booting android yet.
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
can anyone uploade the files? i dont have linux..
Cool, thanks! I seems to be working for me with MDJ FroYo HD v4.6. Has anyone had any success getting two Android ROMs running from their microSD card? I was doing this when booting from WM6.5 by putting them in different directories and modifying rel_path in the startup.txt for one of them, but obviously this method won't work until MAGLDR supports startup.txt...
clio94 said:
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
I didn't do the superram built myself, but letama posted a full version later in that magldr thread. Try to see if you can find it. If not I'm sure I still have it somewhere I can post it for you.
You can change Android folder on SD using MAGLDR
Enter Magldr
Select 9. Services
then 1. BootSettings
then 3. AD SD Dir
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ReverendJKR posted a great video on TWRP and Goo Manager working together.. Much more to come with this relationship
http://youtu.be/OA0S275XO3U
Oh man. Awesome!
Looks nice...looking forward to trying it out.
This looks very slick!
Sent from space
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Super cool, thanks guys, I am now into Nook Color... HD2, AMAZE 4G...
Jainyankee1993 said:
Can this recovery be used on any phone/tablet?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
We have a list of supported devices on the main twrp2 page: http://teamw.in/project/twrp2
So I see you got that stuck in recovery bug all worked out ehh? nice work.
eyeballer said:
TeamWin is proud to present TWRP 2.0 for Nook Color!!
Click to expand...
Click to collapse
Congrats TeamWin... this is supercool.
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
hm, anyway to install this on an existing install?
Midnitte said:
hm, anyway to install this on an existing install?
Click to expand...
Click to collapse
Right from their page? Though idk what kernel they are talking about.
Download the above file. Connect your Nook Color to the PC via the USB cable. This assumes you have working ADB.
Execute the following:
adb shell busybox remount / -o rw,remount
adb shell busbbox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb push twrp-encore-2.0.0RC0.ub /boot/uRecRam <--- You can change uRecRam to uAltRam for alternate boot.
adb push kernel /boot/uRecImg
adb shell busybox umount /boot
Click to expand...
Click to collapse
RileyGrant said:
eyeballer one of the install steps is to push "kernel" to uRecImg but there is none? Am I missing something obvious?
Click to expand...
Click to collapse
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
eyeballer said:
Sorry guys, the page is updated now with the kernel link. However, we just use a stock AOSP kernel so if you had CWM on emmc already you don't need to push the kernel since it's the same.
Click to expand...
Click to collapse
Actually what I thought, thanks for clarifying man .
Oooh, i look forward to trying this.
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
bobtidey said:
I was not having success installing this on emmc with the adb instructions probably because busybox was not set up the same way.
So I tried an different approach which was to use the NookColor UMS app to mount the boot partition so it shows up as a USB drive on PC called boot. I then just renamed uRecRam to uRecRamOld and copied in twrp-encore-2.0.0RC0.ub and renamed that to uRecRam. I didn't bother copying the kernel as per the previous posts.
Rebooting into recovery then brought up the TWRP recovery which looks very nice to use. Also works off the power up N after emmc recovery selected as expected.
Clockwork has given me good service but I think I'll be using this going forward.
Click to expand...
Click to collapse
I had to do the same thing. Kept getting an error that "applet not found" for busybox in adb.
Thanks for the alternate method.
This is a much better implementation of our hardware in backup.
Thanks TeamWin.
Nburnes said:
Right from their page? Though idk what kernel they are talking about.
Click to expand...
Click to collapse
It wasn't there before! I swear! /thanks
Hm, is usb storage working for anyone?
The only thing I don't really care for is... and I know I am doing things in a unique way....
I have SASD with CM7 on it... verygreen's recovery as alt-boot and replaced CWM with TWRP as recovery mode on the uSD... when in TWRP and reboot... it boots stock on eMMC instead of a normal boot... it should do a normal boot (uSD first)
HTML:
I AM NOT RESPONSIBLE IF YOUR DEVICE GETS BRICKED
Alright, I have been working on porting Ubuntu Touch to our lovely Evo 3D's. I will be posting my work here and will change the thread once I get it out of alpha. As you can see this is only recommended for devs or people that know how to use Linux just now.
FAQ
Plz halp i am stuk!?
Click to expand...
Click to collapse
A: No.
Can I help?
Click to expand...
Click to collapse
A: Sure! I have a github where I upload my source code, feel free to fork and submit pull requests.
Requirements
Ubuntu FS - (raring-preinstalled-phablet-armhf.zip).
Decent knowledge of Linux.
Guide
1. Download the Ubuntu FS & shooteru image
2. Backup your phone.
3. Wipe everything (Wipe data/factory reset + dalvik cache, and your ext4 partition).
4. Format your sdcard to have two partitions - one Fat32 (for android) and one ext4 (for Ubuntu)
4. Turn off your phone, insert the SD-card into your computer.
5. Transfer the shooteru image to your SD-card (Like you would do if you'd flash it normally).
6. Open a terminal, Unzip the Ubuntu FS.
7. Run the following command; sudo tar --numeric-owner -axf blabla.tar.gz
8. Run the following command; sudo mv binary /INSERT-PATH-TO-SDCARD-EXT4-PARTITION/ubuntu/
9. Safely eject the SD-card and insert it into your phone.
10. Boot into recovery.
11. Flash the shooteru image
12. Boot up
13. Change the values in /usr/bin/ubuntu-session (Look for export GRID_UNIT_PX = 18 and change it to 12)
14. Reboot
15. Win.
Download
Shooteru image 0.1 (Dev-Alpha)
Changelog
0.1 - 12/7/13
Initial Release
Bugs
Camera
Wi-Fi
Bluetooth
Data
3D
3G
Touch Buttons
Volume
Audio
Resolution
Thanks
Evervolv team
Ubuntu Touch team
helicopter88
good job! thanks
thanks! i'm trying to develop on Ubuntu Touch!
slinkyregent said:
thanks! i'm trying to develop on Ubuntu Touch!
Click to expand...
Click to collapse
It's awesome isn't it?
I won't be able to update this as much as I would like to for just now due to some important family matters. I am however talking with some Ubuntu Touch developers to help solve some issues
Ubuntuz said:
It's awesome isn't it?
I won't be able to update this as much as I would like to for just now due to some important family matters. I am however talking with some Ubuntu Touch developers to help solve some issues
Click to expand...
Click to collapse
I sow the same thread,the same OP like yours on Chinese forum.
dr_jerremy said:
I sow the same thread,the same OP like yours on Chinese forum.
Click to expand...
Click to collapse
Hm.... Odd. I used the same style as the old Evervolv ubuntu threads.
EDIT: Updated the thread with newer Ubuntu builds... it now boots! A lot doesn't work just now but as always I am working hard on it.
dr_jerremy said:
I sow the same thread,the same OP like yours on Chinese forum.
Click to expand...
Click to collapse
I am very curious about the chinese forum you said. can you tell me the website? thanks in advance
uBuntuz working on uBuntu
epic stuff there
im afraid everytime the chinese forum is mentioned, XDA admin/mods close it
jcsy said:
uBuntuz working on uBuntu
epic stuff there
im afraid everytime the chinese forum is mentioned, XDA admin/mods close it
Click to expand...
Click to collapse
haha yeah I'm working on getting the latest Ubuntu Touch images to work and also make it easier to install
I don't know what all this business is about the chinese forums but I'll just stay out of it
Ubuntuz said:
It's awesome isn't it?
I won't be able to update this as much as I would like to for just now due to some important family matters. I am however talking with some Ubuntu Touch developers to help solve some issues
Click to expand...
Click to collapse
When I have some time, i download and i try this rom... I've got a really slowly connection (150kb/s ****ing italian ISP). Please take that updated! :good:
PS: If anyone want to help me or work with me for create Ubuntu Apps, send me a PM!
it seems like windows cannot read a sd with 2 partitions.. no problem on SuSe, though... here... be wwarned...
e3d said:
it seems like windows cannot read a sd with 2 partitions.. no problem on SuSe, though... here... be wwarned...
Click to expand...
Click to collapse
Having 2 partitions on the SD card shouldn't matter with 0.2.
The file you requested was not found in goo.im,the link is broken.
tzpm said:
The file you requested was not found in goo.im,the link is broken.
Click to expand...
Click to collapse
Oops! Fixed it!
loop logo htc ,
---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------
boot up ? what is your mind? how to do /
dqhuy1989 said:
loop logo htc ,
---------- Post added at 11:01 AM ---------- Previous post was at 10:56 AM ----------
boot up ? what is your mind? how to do /
Click to expand...
Click to collapse
try 0.1 with the 0.1 guide. I'm kinda putting off supporting this since hardly anyone has a) used it and b) commented their results.
I got evervolv boot screen with the first method and second method gave this messege in terminal
"sudo rsync -aP binary /INSERTPATHTOSDCARD/ubuntu/
sending incremental file list
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: mkdir "/INSERTPATHTOSDCARD/ubuntu" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]"
Ubuntuz said:
try 0.1 with the 0.1 guide. I'm kinda putting off supporting this since hardly anyone has a) used it and b) commented their results.
Click to expand...
Click to collapse
What did you expect when you said this:
Ubuntuz said:
Alright, I have been working on porting Ubuntu Touch to our lovely Evo 3D's. I will be posting my work here and will change the thread once I get it out of alpha. As you can see this is only recommended for devs or people that know how to use Linux just now.
Click to expand...
Click to collapse
I don't think such attitude will get you anywhere as a dev. First you need to feel you want to do something for yourself. Then you can start enjoying it... Just my $0.02
zzrzr said:
I got evervolv boot screen with the first method and second method gave this messege in terminal
"sudo rsync -aP binary /INSERTPATHTOSDCARD/ubuntu/
sending incremental file list
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: mkdir "/INSERTPATHTOSDCARD/ubuntu" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]"
Click to expand...
Click to collapse
See where it says "INSERTPATHTOSDCARD" yeah? Put the path to your SD card there.
decemberhayes said:
What did you expect when you said this:
I don't think such attitude will get you anywhere as a dev. First you need to feel you want to do something for yourself. Then you can start enjoying it... Just my $0.02
Click to expand...
Click to collapse
I figured that there was plenty of people on this board that could figure out how to use Linux.
I think if u don't have anything valuable to help Ubuntu, then we should keep quiet
I don't, so I wouldn't criticise anything
For those who do, please help and assist in any way
Testing, drivers, kernel, etc
I believe Ubuntu meant well when he is asking for any form of help from the community to help develop this
Whether he has passion for himself or the project or not , that's not appropriate to condemn or expect
Let's work together when we can, where we can
-----------------------------------------------------
Tapatalked from my HTC EVO 3D GSM
Johnnyslt CM10.1, 06-July-2013
Stock kernel & SIO
-----------------------------------------------------
Ok guys, starting this theard also to find other devs that also are working on porting ubuntu touch to the same device and buildup a team, anyone interested?
So my 1st try was when CM wasn't final release and got stuck at boot, i could connect with adb, but i only got displayed ubuntu and kernel version, and only a few commands worked, this is my 2nd try, so let's hope it will work better this time, also i will put my work on github.
24.NOV.2013:
-Having issues with libstagefright: http://pastebin.com/C8cuCAYA
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
JustSueMe said:
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
Click to expand...
Click to collapse
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
Nice I have a dev build env for ubuntu touch but unsure how to pull repo for unknown device. But if u get a build that boots I'm more than eager to work on it
Sent from my GT-I9505 using xda app-developers app
I've tried a few times to get it going for the M919 but each time I can't get past the Samsung Splash screen. I wasn't even able to connect via adb. Granted, I don't exactly know what I'm doing, but I do have a build environment set up and do have a little experience building and debugging builds. I should have time to tinker with it again in a few weeks.
ubuntu build
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
i have a build enviroment made up and pulled repos ect.. i just need to work a few things out before im ready to test it and post on here, if you can point in right direction (if yours boots)
need to do the audio part but can boot without sound in the alpha
neeed to add in apparmor later, can be done later ubuntu should boot without it
brightness, i dont think it matters so much as booting up is priority but i dont seem to have file it wants me to change "device/[manufacturer]/[codename]/init.[codename].rc"
problem with the way fstab has to be setup
within my android source my fstab is "void.fstab" which has lines that look like :
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.4/mmc_host/mmc2/ /devices/platform/msm_sdcc.2/mmc_host/mmc2/
ubuntu port guide for fstab asks to find a filename like "fstab.jfltexx" and have lines that look like:
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1
help with fstab will be much appreciated.
then ill make my build ready for testing/debugging + suppose ill upload files output files for others that are interested to use
Try this
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,journal_async_commit wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,journal_async_commit,noauto_da_alloc,errors=panic wait,check,encryptable=footer,length=-16384
# recovery
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults recoveryonly
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults recoveryonly
# vold managed volumes
/devices/platform/msm_sdcc.2/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=sda:auto
Yes I used part of that, problem now is compile errors, I have fixed a lot of them which involved discarding some features for the time being.
Boot is the main priority though
Im stuck on a compile errors for shared library, ill attempt this one after I've slept.
Hope fully this is the last error, then ill have a .zip to upload .
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
coolnessQ said:
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
JustSueMe said:
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
Click to expand...
Click to collapse
are you unsing tw stock sources for the kernel? with 7.3mb it almost looks like that.
I have tried porting it before and here is my advise, you really have to look at the errors that it gives you during compiling rather then skipping it, or ignoring it, this is the only way you will get it decently working. the rom itself is only around 100mb if i remember correctly. the ubuntu package is like 400mb on top, but thats all proprietary files so universal.
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
JustSueMe said:
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
Click to expand...
Click to collapse
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
broodplank1337 said:
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
Click to expand...
Click to collapse
Ah I see this seems to of cleared it up abit for me, im busy today but may get look in at code, if not then tomorrow and clean it up abit and try recompile.
If it looks like a lost cause ill jump over to your git and pull that repo.
Fingers crossed
Sent from my GT-I9505 using xda app-developers app
commit to github so we can all take a look at it
.
..
You need to copy some header files for libstagefright to compile:
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMetaData.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-
core/inc/QOMX_AudioExtensions.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/OMX_QCOMExtns.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libmediaplayerservice
My cm compiled but it wont boot (after flashing .zip and ubuntu system)
hmm.. did you remove all unecessary APPS? that are only needed by android not ubuntu touch? at you it seems relating to mounting points, something in your source doesn't let the kernel mount the partitions, maybe find a different approach to mount and add it to the source tree.
http://e2fsprogs.sourceforge.net/
everyone with interest in using ubuntu
if your interested in ubuntu touch on jfltexx and want to help
your now in luck
go here http://forum.xda-developers.com/showthread.php?p=48344910#post48344910
there is the download links and a few fixes for connectivity
Here is the link to the AT&T/Tmobile rom download : http://www.androidfilehost.com/?fid=23252070760974893'
Here is the link to the how to site (now instead of the phablet download use the one above) : http://forum.xda-developers.com/showthread.php?t=2564187
Oh and you need to flash the lokidoki zip file if used for AT&T.
Had it working perfectly, it is in extreme alpha, I had the wifi working and sound only works when plugged into headphones.
This should be more than enough to get the rom started up and getting a nice UT running shortly where everything works :3
I am not responsible for whatever happens to you or your device before, during, or after this. :3
I am not responsible for bricked devices,
This is a port of Ubuntu Touch for the LG V20 T-Mobile h918 variant. Not yet stable.
Before install halium-boot.img backup only your boot partition. You can restore your current system after try Ubuntu touch. Ubuntu touch will be install in data partition not in system partition.
Youtube :
Sources:
Kernel:
https://github.com/walidham/android_kernel_lge_msm8996/tree/halium-7.1
Device:
https://github.com/walidham/android_device_lge_h918/tree/halium-7.1
https://github.com/walidham/android_device_lge_msm8996-common/tree/halium-7.1
Manifest file
https://github.com/walidham/lge_manifest/tree/master
Status
Working:
Audio
Calling
SMS
4G
Wifi
GPS
Vibration
Orientation sensor
Missing:
Video recording/decoding
Bluetooth
Flash light
ADB/MTP
Libertine
camera
fingerprint
There are two methods to install Ubuntu Touch
Method 1 : unofficial installation with TWRP
1- Download zip file UT TWRP
2- push it in internal storage or sdcard
3- backup up your current boot partition (to restor it later if you want return to android rom)
4- install zip file, make sure your data partition is ext4 (option if you want fresh install you can wipe data partition)
5- rebbot
Note : password is "1111"
Method 2 : official installation/ hard for newbie
NOTE: As the LGV20 aren't community devices yet, the install process may be a little "non-noobie-friendly"
Install twrp on your device, format data partotion to ext4
Download the latest precompiled system.img and halium-boot.img from : halium-boot
Download the JBB's halium install script
Download either the regular rootfs or the Edge one
While on TWRP:
Code:
halium-install -p ut the_rootfs_you_choose.tar.gz system.img
While on TWRP:
Code:
adb shell 'mkdir /a; mount /data/rootfs.img /a; echo manual | tee /a/etc/init/rsyslog.override; umount /a; sync'
While on TWRP: install halium-boot.img (on boot partition)
Then reboot
Connect to phone with ssh
Code:
ssh [email protected]
When entering in ssh run those commands:
Code:
$ sudo -i
$ mount -o remount,rw /
$ cat /var/lib/lxc/android/rootfs/ueventd*.rc | grep ^/dev | sed -e 's/^\/dev\///' | awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/etc/udev/rules.d/70-h918.rules
$ reboot
If you want suport this project you can donate
Edited : 03-09-2022 :
Now H910 is supported,
For LG V20, i finished the port for H910, its beta version need more test and fixe bugs.
Download link : https://www.androidfilehost.com/?fid=14871746926876820212
Installatio:
1- backup your data and boot partition. System partition you can take it, we not use it.
2- Download ubuntu-touch-h910-01-01-2020.zip
3- Install the zip
4- Rebbot
excellent sir
Got Camera work, but without video record, just take photo on 12mb max
i want to try ubuntu. can you make more detail about instal ubuntu.
because in step 1 . always like this
not found.
thank you
Tried
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
nickhaven said:
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
Click to expand...
Click to collapse
Can you tell to me how to Input step 1 in twrp?
In my device every want to input halium-boot always not found
nickhaven said:
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
Click to expand...
Click to collapse
try to fix display scalling
1- when system boot connect to the phone via ssh
ssh [email protected]
Code:
sudo -i
cd /etc/ubuntu-touch-session.d
nano h918.conf
add this lines
Code:
GRID_UNIT_PX=29
QTWEBKIT_DPR=2.5
NATIVE_ORIENTATION=portrait
FORM_FACTOR=handset
save file and reboot
For debug
Code:
cat /var/log/syslog
dmesg
sudo /system/bin/logcat
raf21 said:
Can you tell to me how to Input step 1 in twrp?
In my device every want to input halium-boot always not found
Click to expand...
Click to collapse
in twrp, select install -> clique button install image (at the bottom)
select halium-boot.img (you must copie from pc to your phone)
walidham said:
in twrp, select install -> clique button install image (at the bottom)
select halium-boot.img (you must copie from pc to your phone)
Click to expand...
Click to collapse
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
raf21 said:
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
Click to expand...
Click to collapse
Look at halium-install link
halium-install is done on a linux pc/livecd/virtual machine that has the following installed
qemu-user-static
qemu-system-arm
e2fsprogs
simg2img
sudo
binfmt-support
Looks like it asks for the phone to be connected via usb as well.
Phoenix591 said:
Look at halium-install link
halium-install is done on a linux pc/livecd/virtual machine that has the following installed
qemu-user-static
qemu-system-arm
e2fsprogs
simg2img
sudo
binfmt-support
Looks like it asks for the phone to be connected via usb as well.
Click to expand...
Click to collapse
i noob in linux
can you make step for install this .... please
iam very interest in ubuntu touch
raf21 said:
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
Click to expand...
Click to collapse
1- reboot to recovery
2- connect your phone to pc (system ubuntu must be)
3- copy halium-boot.img to interal storage of phone
4- run halium install script
Code:
ex : ./halium-install -p ut ubuntu-touch-hybris-xenial-edge-armhf-rootfs.tar.gz system.img
5-install halium-boot.img with twrp
walidham said:
1- reboot to recovery
2- connect your phone to pc (system ubuntu must be)
3- copy halium-boot.img to interal storage of phone
4- run halium install script
Code:
ex : ./halium-install -p ut ubuntu-touch-hybris-xenial-edge-armhf-rootfs.tar.gz system.img
5-install halium-boot.img with twrp
Click to expand...
Click to collapse
how to run script
every i take halium script in terminal ubuntu always
/home/alienware/Desktop/ubuntu touch/halium-install-master/halium-install.sh' -p
Unsupported post install release! Exiting now
maybe i will try again if anybody can tell to me complete step by step to install ubuntu touch
thank for porting to ubuntu touch to h918
raf21 said:
how to run script
every i take halium script in terminal ubuntu always
/home/alienware/Desktop/ubuntu touch/halium-install-master/halium-install.sh' -p
Unsupported post install release! Exiting now
maybe i will try again if anybody can tell to me complete step by step to install ubuntu touch
thank for porting to ubuntu touch to h918
Click to expand...
Click to collapse
make dot and slash before commande like this ./halium-install.sh
youtub : https://youtu.be/E2FtIR7SUYU
Any chance that this would come to the other LG V20's such as the L997 (sprint)?
Americancosworth said:
Any chance that this would come to the other LG V20's such as the L997 (sprint)?
Click to expand...
Click to collapse
I have just h918, but i can build UT for others variant and i need tester for it.
walidham said:
I have just h918, but i can build UT for others variant and i need tester for it.
Click to expand...
Click to collapse
Can you help me to build Ubuntu touch for us998 lg v30 sir
raf21 said:
Can you help me to build Ubuntu touch for us998 lg v30 sir
Click to expand...
Click to collapse
for help you can join us at telegram
https://t.me/ubports_porting
unofficial installation with TWRP
1- Download zip file UT TWRP
2- push it in internal storage or sdcard
3- backup up your current boot partition (to restor it later if you want return to android rom)
4- install zip file, make sure your data partition is ext4 (option if you want fresh install you can wipe data partition)
5- rebbot