@MrT10001 I certainly don't mean to sound ungrateful to the porter and their efforts in this space, but I'm ultimately happy in an ironic way that an upgrade to focal wasn't available earlier. I'd already had to retire my OPO from daily use due to the 3G shutdown here, and I think I may just keep it on 16.04 now till the day it dies as a host for the various apps that are unlikely to be rebuilt for Focal and beyond. It's kind of a time machine for checking the Open Store.

And TBH, TuxRacer, TuxDungeon and TuxHunter have some real "waiting for the dentist with child" utility, and I think I'd be kicking myself if I'd unsuspectingly lost those to a distro version upgrade.

@messayisto I haven't had much time lately, but now I finally have some time to myself. Will be sure to take a look at it!

@ricardo65 Browser works fine here on two focal devices. Maybe something went wrong when installing. I would try to install again. First without wipe, if that doesn't help, maybe again with wipe.

Also check the logs Morph. Maybe that brings some helpful info up.

You could also test Sapot browser from OpenStore. But I guess that won't work either if all webapps don't work.

Just some suggestions. I hope one does help. 🙂

@Dunbrokin, I would suggest flashing with the installer. Since you don't know what version it is on now, and if you don't have any data on it you want to keep, I would also suggest ticking the wipe checkbox.

@ricardo65 Morph works perfectly fine for me on OpO. Even YouTube works. Have you tried reinstalling devel using the installer? Please don't use RC, it contains ancient images that are by the standards of development, obsolete.

@TheVancedGamer Sorry. I somehow mamaged to downvote your post. Fat fingers on a small screen. I have upvoted to remove the downvote

@Moem said in Installion with UPPorts installer runs fine but ....:

@BlondJamesBlond Which installation channel did you choose? I think the Focal channel is currently struggling, it might be good to start with Xenial for now.

I agree with that. Stay with 16.04 stable, that seems to work ok.

OK, it is the morning and I have resolved the issue thanks to this thread on the forum which linked me to this thread on Github.

So.... It looks like adb is disabled for recovery on 16.04 Halium Development and also is not working on Focal (20.04) development - bear in mind this is a 16Gb OPO and it works on the 64Gb OPO.

I flattened the device, i.e. formatted all partitions with TWRP and managed to get 16.04 stable to install. But alluding to the above, NO WiFI.

Followed the Github instruction, using a windows 11 machine.

Copied the text of the WCNSS_qcom_cfg.ini to a text file, but saved it as that title as an ini file and copied it to my adb folder.

I followed the commands:

adb devices # start the daemon and verify your phone is plugged-in adb shell # start a shell in the phone mkdir /persist # create a folder to mount /persist mount /dev/block/platform/msm_sdcc.1/by-name/persist /persist exit adb push WCNSS_qcom_cfg.ini /persist/ # send the file adb shell adb umount /persist # unmount /persist exit

There is an error - adb umount /persist should be umount /persist

Reboot and Wifi is working.

Thanks to all from the old thread and glad to see it still works.

@Lakotaubp said in Latest OS update killed my phone!!:

@scottbouch Volume up and power buttons =Fastboot
Volume down and power buttons=Recovery

If you go for the installer option DO NOT tick the wipe option if there is anything on the phone you want to keep. Bootstrap should be OK.

Thank you for the guidance! Vol down and power helped!

@prophanetes Welcome to life as we know it... yes, UT can be a little fiddly and a little finicky in some ways but we love it anyway. It's got quirks and personality. 🤗

@jezreel Other side of the planet... OPO is one of the easiest to install Ubuntu Touch.
First of prepare your workspace. So have a PC that has the Ubuntu Touch installer on it.
Install Android Studio - this gives you the latest fastboot and ADB drivers which are a requisite to install UT.

Ensure the OPO is running the latest version of Android.

On the phone, go to system, settings and about device. On the build number, tap it a few times till it tells you that you are a developer.
Then go into developer options and enable OEM unlock and USB debugging.

Assuming you are running windows (10/11) navigate to the folder platform tools:

C:\Users<user name>\AppData\Local\Android\Sdk\platform-tools

In the platform tools folder, right click on an empty space, you may have to do this twice, and select open in terminal.

Connect your OPO to the PC via a USB cable and ensure that you accept in the pop up box that gives permission for USB debugging (vital).

In the terminal you have opened in the platform-tools folder, type in:

ADB devices

You may have to put ./ in front of the ADB devices, depedning on which version of powershell etc that you have running as a terminal CLI

This command should detect your phone and give a string of numbers - good. If it doesn't ensure USB debugging is enabled and try again.

Once detected type in :

ADB reboot bootloader

The device will reboot to the bootloader (fastboot mode).

Once at the bootloader type into the terminal:

fastboot OEM unlock

Be patient, let it do its thing, it should then reboot and start up. Follow the prompts to set up Android again - this is important. UT won't install or run if the bootloader is locked, so ignore any warnings about device security.

Once Android has been set up, make sure Developer options is enabled and then ensure USB debugging is enabled.

With the device attached to the PC, start up the UT installer and follow the onscreen instructions. For the time being, choose 16.04 Stable on the drop down box and tick the "wipe data" box.

This is from my experience, but if it goes wrong, it is recoverable, but can be a bit complicated if you are not sure of the command line. It has worked for me 99% of the time, but the time it didn't, I had to reinstall the stock ROM and start again. I cannot guarantee it will work 100% and (disclaimer)cannot be held responsible for you bricking the device or losing data (back up any data before starting anything).

If you do want to go for it there is a wealth of information here, on the UBports site, YouTube and XDA-developers forum.

@moem Thank you, after some time using i might say that it is quite awesome, yet to try sim card capabilities

@ridinoh130 this would work for a regular Ubuntu installation, but not for Ubuntu Touch.

@mrt10001 said in oneplus one wifi does not work:

@domubpkm Yes that is the usual repair for wifi. The Other thing is to switch it on and off a few times.
@ricardo65 Is it a OnePlus One 16Gb? That was one that gave me a few headaches with wifi and the phone modem not installing.

is 64 gb

That is often what happens if the partitions are not what the installer expects them to be. But I don't think that can be the problem here, so it may be the port.

@emphrath OK 😀

@lakotaubp I will leave it on this channel for testing. It seems to be fine, but may not be the solution for everybody. What I did:

I thought the phone had Cyanogen 13.2, but oddly the boot splash screen said Android and not Cyanogen Mod. This should have set off alarm bells, however in device info it stated Cyanogen 13.2 and the build number was correct. I unlocked the device and installed UT which installed fine, but no WiFi.
2)Installed via Fastboot Cyanogen 13.2. Then installed UT, no WiFi. Wifi works fine in Cyanogen (Android).
3)Installed Cyanogen 13.2 again and again tried UT. Still no WiFi. Tried some commands in the CLI and it stated that the module was not loaded, giving the standard loopback address of 127.x.x.x. Installed TWRP, formatted data and erased the partitions. Installed Cyanogen 13.2 and tried UT again. Still no WiFi.
6)Installed TWRP and flattened the device again. Then installed OxygenOS. Tried UT again, no install.
7)Re-installed Cyanogen 13.2 and tried UT with the halium-development path. This worked.

Oddly as pointed out previously, the device is 16Gb , it does not show A0001 in the device info.