New OnePlus One Issues on Fresh Install

boygenuis

I finally decided to try UT on my Sandstone A0001 OPO this week. First, I attempted this with my Ubuntu box, but could never get past the error message:

debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
debug: Error: Command failed: adb -P 5038 shell echo 1
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
debug: adb shell: echo 1
debug: Running platform tool exec cmd adb -P 5038 shell echo 1
at ChildProcess.exithandler (child_process.js:217:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Socket.<anonymous> (internal/child_process.js:342:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at Pipe._handle.close [as _onclose] (net.js:510:12)
debug:
debug: adb shell: getprop ro.product.device
debug: Running platform tool exec cmd adb -P 5038 shell getprop ro.product.device
debug:
debug: getprop: A0001
debug: adb shell: cat /etc/system-image/channel.ini
debug: Running platform tool exec cmd adb -P 5038 shell cat /etc/system-image/channel.ini
debug:

I have adb and fastboot installed and this thread (https://forums.ubports.com/topic/897/traing-to-install-in-oneplus-one/2) didn't help, either. And then, I couldn't get the phone to boot past the Powered by Android screen.

So, now I'm trying to use my Windows 10 machine and I put CM11 on again via the OnePlus Recovery Tool, as seen in this vid https://www.youtube.com/watch?v=Ste5tvCDMWE. I then unlocked the bootloader, put on TWRP, and rooted just like this site (https://forums.oneplus.com/threads/oneplus-one-how-to-unlock-bootloader-install-custom-recovery-and-root.64487/) so that I now have, at least, a fresh install of Android. I grabbed the Windows UBPorts Installer from https://docs.ubports.com/en/latest/userguide/install.html and started the process. The installer doesn't recognize my phone automatically, but I can add it manually and the installer at least flashes while my OPO is in fastboot mode and reboots to recovery mode. However, just like this fella (https://forums.ubports.com/topic/2148/installing-ubuntu-touch-on-oneplus-one), I can't get the installer to recognize that my phone has rebooted to recovery mode and so there it sits for... hours maybe?

Should I be updating to CM13 or CM15 before installing UT? Or, should I install another OS on my CM11 so that I can then move to UT? Have I given enough info? Can someone provide some help? Maybe I just haven't found that one page to explain the thing I'm missing.

Lakotaubp

@boygenuis This version of adb is probably best for Windows https://forum.xda-developers.com/showthread.php?t=2588979 Recheck dev mode is on, MTD marked and oem unlocked. I installed on Win 10 with version 0.1.20 of the installer also try a usb2 port. Also have a few usb cables handy to try. Start the installer and wait till you need to connect the phone, if you can select the wipe option.
I think my OPO took 40 mins in all to complete. If after a while nothing is happening you can restart the installer without issue. Mine stuck after Ubports recovery was installed and I had to restart the installer.
See how you go this time and come back here if there is still an issue or to tell us you have installed.

P.S. versions 0.1.12 and 0.1.09 of the installer have also proved useful when others fail.

Ingo

You seem rather familiar with fastboot and adb so you also could give the new manual installation instructions a try.
Click the "manual installation instructions" link on https://devices.ubuntu-touch.io/device/bacon

flohack

@boygenuis said in New OnePlus One Issues on Fresh Install:

debug: Error: Command failed: adb -P 5038 shell echo 1
error: device unauthorized.

Device Unauthorized means that your phone forbids adb access. You have to solve that by enabling developer mode (the usual 7 touches on the kernel version, was it that one) and then allow usb debugging, and optionally also allow OEM unlocking the bootloader.
then disconnect/reconnect the computer, you should get a popup to allow access for this machine. click OK and you should be in.
As long as adb devices shows error messages, you don´t need to try start installing UT.