Oneplus 3/3T

A Former User

I can't seem to get the installation to work. I was able to format /system, /data and /cache as ext4 with TWRP at one point, but now after using the UBports installer it just boots to a glowing circle and reboots.

When I try to fastboot flash recovery twrp.img, touch input is no longer working in TWRP, so I can't do anything.

A Former User

Ok, I got it to work. Apparently I just had to wait a long time on that Android-ish glowing circle screen and then it booted Ubuntu Touch.

I was confused because the boot logo still showed "Powered by Android", whereas my old OnePlus One showed "Powered by UBports", so I assumed the installation failed.

Is it normal for the boot screen to not show the UBports logo? And is there a way to get rid of the fastboot oem (un)lock "scary" warning?

gischpelino

@the7thstranger
Is it normal for the boot screen to not show the UBports logo?
--> yes
And is there a way to get rid of the fastboot oem (un)lock "scary" warning?
--> no, needs signed system (lineageos has signed system images).

Logo: you have to flash it yourself. Take a look here. I used it on a op3t.
You can flash the 'logo.bin' for your device from terminal (twrp) with a command like:

dd if=logo.bin of=/dev/block/by-name/LOGO

Be careful, check twice before you do it! You can brick your phone if something is wrong.

A Former User

@gischpelino Thanks. Though that repository's README says it should be flashed with fastboot. Does it make a difference if I use dd instead of fastboot?

Also, what do you mean with terminal (twrp)? Can I use a shell in Ubuntu Touch, or must I reboot to recovery and then use adb?

There's no /dev/block/by-name/LOGO accessible from the OS, so I guess not.

A Former User

I was eventually able to do it by booting to bootloader mode, running fastboot boot twrp.img, and running adb sideload from there.

Then I downloaded the update.zip and ran adb sideload update.zip.

I was not able to run fastboot flash LOGO logo.bin, because I got the described FAILED (remote: Partition flashing is not allowed).

Now I have a proper UBports logo. Great!

gischpelino

@the7thstranger inside twrp you can use the terminal and make it with dd. I told you to use dd because a flash logo using fastboot is not possible and I did not know, if there is a flashable zip available. Well done.

weigeloveu

how to making system be rw?
this guide need adb but adb doent work,anyother idea?

NoelFlantier

You can install ubuntu tweak tool (https://open-store.io/app/ut-tweak-tool.sverzegnassi) from the open store, go to system and then chose rw, i think it should solve your problem

A Former User

This post is deleted!

A Former User

This post is deleted!

JimShady

@ComLarsic said in Oneplus 3/3T:

Hello, everyone. i am trying to install ubuntu touch on my device again using the ubports installer but i get this error:
Error: systemimage: Error: Error: {"error":{"killed":false,"code":2,"signal":null,"cmd":"/tmp/.mount_ubporte14WRR/resources/app.asar.unpacked/platform-tools/linux/adb -P 5037 shell mount -a"},"stdout":"","stderr":"mount: mounting /dev/block/bootdevice/by-name/system on /system failed: Invalid argument\nmount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Invalid argument"}
I am using the installer on manjaro 19.0
is there any way to fix this?

Hi @ComLarsic . Having the same issue. How did you format the system please? I've got fastboot running on my desktop, I guess I need to use that?

gleblee

Did anyone has working hotspot connection? Hotspot is activating, but no internet connection, looks like problems with DNS etc.

A Former User

@JimShady First flash TWRP from here using fastboot flash recovery twrp-3.4.0-0-oneplus3.img.

Then run fastboot reboot recovery and format /system, /data and /cache as ext4 from TWRP. After that you can run the UBports installer again.

Lakotaubp

arm64 devices now have a devel channel!!! arm64 will now follow normal release schedule and with OTA 13 being the first stable release for arm64 Please test it out https://system-image.ubports.com/16.04/arm64/hybris/
From Marius, and yes it's on the OP3 now.

danqo6

Hello guys,
I installed today ubuntu-touch with official installer (devel and edge checked) on oneplus 3T, and I was unable to connect to phone with ssh. Both ssh and usb-tethering services was stopped. In ssh.overide file is first line manual and in file usb-tethering.conf too. I am suspecting that autoenabling of these services doesn't work.
And after starting this 2 services with ip a I am getting

enp0s20f0u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether e2:0a:36:e1:fe:a7 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5ed9:d70d:7e23:2dda/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

and unable to connect because IP assignment didn't worked

3T_Ed

As per the latest Q&A 83:

"One effect of this is that devices using Halium 7 will now be able to use the installer and to get updates via the server in the normal way. Xiaomi Redmi 4 and OnePlus3/3T should be immediate beneficiaries of that, along with the little mentioned but nice BQ Uplus. That ease of install should extend the user base of those phones quite considerably."

Just to be sure:

does this imply that G-droid camera app can be installed and will not (be)affect(ed) when updated?
Is the Halium operation, which used to be a separate action, now included in the installer itself?
What are the immediate beneficiaries for OnePlus 3/3T?
If one is about to would, what would be the best way to do it? preferably a step-by-step instruction, considering the user to be a newbie having a OP with UT already installed and looking to preserve the content and apps currently working.
edit: Will the UT black logo splash screen be included in the OnePlus 3/T installer (replacing the Android one on startup?

Personally I had quite some troubles getting UT installed initially. Now that I have managed to get my device running UT (without Halium!) I'm kind of reluctant to re-install and no doubt others with the device feel the same. Maybe it's just an easy task, so hopefully someone will be able to reply to the questions above in order to make users more confident in re-installing the whole thing as of September 9th.

Thanks!

Lakotaubp

@3T_Ed To move to the standard update cycle just change to devel in system settings. That puts you on a more stable footing than being on the edge. Nothing else changes. As for camera I only have the OP3 and that did not change workability on devel, camera worked video didn't, but the OP3t is different. As for the splash screen the installer did not install that last time I tried.
Using the installer didn't change anything else app wise when I last used it either. Just don't select wipe.

danqo6

I was recently testing ubports GSI for OnePlus 3T, and Camera experience there was great. Much faster switching between cameras, faster recovery after taking photo, video recording worked, even video playback works. I think that are last pieces for this phone to get properly working. Would be possible to take advantage of this for Halium 7.1 port?

3T_Ed

@Lakotaubp

Until last Friday I was on ~~dev~~ edit: Release Candidate channel and changed it back to Edge. I will switch back to dev again.

As the blog post mentioned the OTA-13 would be beneficial for OP 3/T, in combination with Gst-droid, so I was hoping to get the one thing that keeps me from using the phone as my daily driver: the camera app.

The blog post mentions to use the installer, whereas your advice is to just switch to dev channel. Will OTA-13 include the Gst-droid camera for 3T then? Without having to re-install UT?

paci87

Anyone else have problems with display auto-rotate since recent (470+ish) updates?