<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[New OnePlus One Issues on Fresh Install]]></title><description><![CDATA[<p dir="auto">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:</p>
<pre><code>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.&lt;anonymous&gt; (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:
</code></pre>
<p dir="auto">I have <code>adb</code> and <code>fastboot</code> installed and this thread (<a href="https://forums.ubports.com/topic/897/traing-to-install-in-oneplus-one/2">https://forums.ubports.com/topic/897/traing-to-install-in-oneplus-one/2</a>) didn't help, either. And then, I couldn't get the phone to boot past the <em>Powered by Android</em> screen.</p>
<p dir="auto">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 <a href="https://www.youtube.com/watch?v=Ste5tvCDMWE" target="_blank" rel="noopener noreferrer nofollow ugc">https://www.youtube.com/watch?v=Ste5tvCDMWE</a>. I then unlocked the bootloader, put on TWRP, and rooted just like this site (<a href="https://forums.oneplus.com/threads/oneplus-one-how-to-unlock-bootloader-install-custom-recovery-and-root.64487/" target="_blank" rel="noopener noreferrer nofollow ugc">https://forums.oneplus.com/threads/oneplus-one-how-to-unlock-bootloader-install-custom-recovery-and-root.64487/</a>) so that I now have, at least, a fresh install of Android. I grabbed the Windows UBPorts Installer from <a href="https://docs.ubports.com/en/latest/userguide/install.html" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.ubports.com/en/latest/userguide/install.html</a> 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 <em>fastboot</em> mode and reboots to <em>recovery</em> mode. However, just like this fella (<a href="https://forums.ubports.com/topic/2148/installing-ubuntu-touch-on-oneplus-one">https://forums.ubports.com/topic/2148/installing-ubuntu-touch-on-oneplus-one</a>), I can't get the installer to recognize  that my phone has rebooted to <em>recovery</em> mode and so there it sits for... hours maybe?</p>
<p dir="auto">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.</p>
]]></description><link>https://forums.ubports.com/topic/2504/new-oneplus-one-issues-on-fresh-install</link><generator>RSS for Node</generator><lastBuildDate>Thu, 21 May 2026 20:16:24 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/topic/2504.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 14 Mar 2019 23:18:35 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to New OnePlus One Issues on Fresh Install on Fri, 15 Mar 2019 08:00:20 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/boygenuis" aria-label="Profile: boygenuis">@<bdi>boygenuis</bdi></a> said in <a href="/post/18458">New OnePlus One Issues on Fresh Install</a>:</p>
<blockquote>
<p dir="auto">debug: Error: Command failed: adb -P 5038 shell echo 1<br />
error: device unauthorized.</p>
</blockquote>
<p dir="auto">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.<br />
then disconnect/reconnect the computer, you should get a popup to allow access for this machine. click OK and you should be in.<br />
As long as  <code>adb devices</code> shows error messages, you don´t need to try start installing UT.</p>
]]></description><link>https://forums.ubports.com/post/18466</link><guid isPermaLink="true">https://forums.ubports.com/post/18466</guid><dc:creator><![CDATA[flohack]]></dc:creator><pubDate>Fri, 15 Mar 2019 08:00:20 GMT</pubDate></item><item><title><![CDATA[Reply to New OnePlus One Issues on Fresh Install on Fri, 15 Mar 2019 07:11:55 GMT]]></title><description><![CDATA[<p dir="auto">You seem rather familiar with <code>fastboot</code> and <code>adb</code> so you also could give the new manual installation instructions a try.<br />
Click the "manual installation instructions" link on <a href="https://devices.ubuntu-touch.io/device/bacon" target="_blank" rel="noopener noreferrer nofollow ugc">https://devices.ubuntu-touch.io/device/bacon</a></p>
]]></description><link>https://forums.ubports.com/post/18465</link><guid isPermaLink="true">https://forums.ubports.com/post/18465</guid><dc:creator><![CDATA[Ingo]]></dc:creator><pubDate>Fri, 15 Mar 2019 07:11:55 GMT</pubDate></item><item><title><![CDATA[Reply to New OnePlus One Issues on Fresh Install on Fri, 15 Mar 2019 06:19:59 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/boygenuis" aria-label="Profile: boygenuis">@<bdi>boygenuis</bdi></a> This version of adb is probably best for Windows <a href="https://forum.xda-developers.com/showthread.php?t=2588979" target="_blank" rel="noopener noreferrer nofollow ugc">https://forum.xda-developers.com/showthread.php?t=2588979</a> 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.<br />
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.<br />
See how you go this time and come back here if there is still an issue or to tell us you have installed.</p>
<p dir="auto">P.S. versions 0.1.12 and 0.1.09 of the installer have also proved useful when others fail.</p>
]]></description><link>https://forums.ubports.com/post/18463</link><guid isPermaLink="true">https://forums.ubports.com/post/18463</guid><dc:creator><![CDATA[Lakotaubp]]></dc:creator><pubDate>Fri, 15 Mar 2019 06:19:59 GMT</pubDate></item></channel></rss>