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
adb push WCNSS_qcom_cfg.ini /persist/ # send the file
adb umount /persist # unmount /persist
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.
@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:
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:
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.
@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.
@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.
The OnePlus One has the hardware for 4G, but UBPorts doesn't have VOLTE support in the OS, so voice calls will not be carried on 4G (LTE). Perhaps it'd still work with the stock firmware, updated as much as possible, of course, but I'd feel too dirty if I tried that.
@dobey Yes, I will make a video in the next few days to illustrate this. The desktop mode and input method of Ubuntu touch are very important, which will affect its promotion to a certain extent. Now my oneplus one cannot use the desktop mode, and there are some problems with the input method, which makes it difficult for me to promote it to others.