last day (15 days later) » 

03:16
Usage:
  ubuntu-device-flash [OPTIONS] <command>

Application Options:
      --revision=        revision to use, absolute or relative allowed
      --download-only    Only download.
      --server=          Use a different image server (default:
                         system-image.ubuntu.com)
      --clean-cache      Cleans up cache with all downloaded bits
      --tls-skip-verify  Skip TLS certificate validation
  -v, --verbose          More messages will be printed out

Help Options:
@NathanOsman i think the commands changed
Hmm... yeah.
ubuntu-device-flash -v touch
^--- maybe try that?
ill see what happens
@NathanOsman btw whatever happened to plasma active, was it completely replaced by plasma mobile?
Yes, as far as I know it completely replaces Active.
@NathanOsman yeah apparently it really doesnt go well with the nexus 5. maybe a 5x would work better
@nathan adb isnt recognizing my device :\
Which ADB are you using?
The one in the archives is incredibly out of date.
You're better off with the one from the Android SDK.
03:26
ah ok
03:50
@NathanOsman still isnt recognizing my device
Have you authorized the device?
You'll need to go into settings and enable developer options (on the phone).
Then enable USB debugging.
lol the thing has plasma mobile on atm
its rooted
In that case... no wonder ADB can't see it :P
so i need to put android back on first?
Maybe but there is one other thing to try.
If you can boot into recovery, there is an ADB mode somewhere in there, I think.
But if not, yeah, maybe reinstall Android.
ill try that
I see something called "adb sideload"
@NathanOsman options are "wipe dalvik cache and "wipe cache"
Sideload might work.
ill try it then
Try going to sideload and then see if ADB can see it.
In theory, it should.
03:55
List of devices attached
03cf409223c2cd4e sideload
@NathanOsman but then
2017/09/29 23:57:13 Expecting the device to expose an adb interface...
device cannot be detected over adb
after running ubuntu-device-flash -v touch
Hrm.
I have no idea then.
ill reinstall android
android kitkat!!!!!!!!!!!!
@NathanOsman brings back memories ;)
love it :D :D
the kitkat taskmanager on 4.4.4 was the best
@NathanOsman literally makes me want to flash my lg stylo 5 to kitkat
@NathanOsman still dont want to work. i turned on debugging
and i authorized the device
04:24
ADB can't see it?
@NathanOsman nah
@NathanOsman i tried the old and new
@NathanOsman maybe i should go to android studio and download the ktikat tools?
I doubt that would help.
@NathanOsman except that it did
04:29
But there is another route.
You could try MultiROM.
i dont want to because i only have 16gb internal
@NathanOsman is it possible to run ubuntu-device-flash using the adb from a directory?
Well, you could change the value of PATH.
what would I run?
04:31
export PATH=/path/to/folder/with/adb:$PATH
ok
james@server ~/Android/Sdk/platform-tools $ adb version
Android Debug Bridge version 1.0.32
james@server ~/Android/Sdk/platform-tools $ ./adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Installed as /home/james/Android/Sdk/platform-tools/adb
james@server ~/Android/Sdk/platform-tools $
still isnt working
@NathanOsman
What does this show?
echo $PATH
@NathanOsman nothing
oh i know what i did
gah
@NathanOsman now it works
@NathanOsman
james@server ~/Android/Sdk/platform-tools $ /usr/bin/ubuntu-device-flash -v touch
2017/09/30 00:39:23 Expecting the device to expose an adb interface...
2017/09/30 00:39:23 Device is |hammerhead|
Device hammerhead not found on server https://system-image.ubuntu.com channel ubuntu-touch/stable
james@server ~/Android/Sdk/platform-tools $
04:47
Oh right.
They don't provide the Nexus 5 images.
You have to switch the URL.
Hang on.
@NathanOsman i just fully rooted the phone
@NathanOsman btw im on linuxmint mate
05:09
@NathanOsman succesfully installed
thanks nathan
cool task manager

last day (15 days later) »