Hello
Flashtool can be downloaded on the Flashtool Homepage (on Installation tab)
As Flashtool was originally developped for X10, you can find a lot of information on the Original X10 Flashtool thread
Major update for 0.6.8.0 : Ability to now install CWM from Flashtool on locked bootloader for LT15/LT18.
Fastboot now works fine under linux
Major new feature :
- Fastboot toolbox for 2011 line devices.
- BL Unlock for X10 Mini/PRo and X8
Please post device related issues here in this thread
But there need to be special edit for x8
jit,xrecovery and other stuff for x10 will now work on x8
Changelog:
0.2.8:
[New] The device is autodetected by the flashtool at plug / unplug
[New] If you install xRecovery from flashtool, you can reboot into recovery from flashtool too (Advanced menu)
[New] You can now backup all /system/app content (Advanced menu)
[New] You can translate all parts of the Graphical Interface (look in x10flasher_lib/langs for samples)
[Upd] Firmware screen selection offers the ability to change the folder source containing ftf files.
[Upd] Clean task now has a notion of profile that can be imported/exported for sharing
[Upd] Customize is now APK Installer. This screen has the ability to choose the folder where apk files are
[Upd] Optimize should work for any device (X10, X10mini/pro, X8)
[Upd] xRecovery should work for any device (X10, X10mini/pro, X8)
[Bug] Flashing should not anymore hang if flash goes wrong. An error should be thrown and flash aborted
Watch this
hmmm...i hope it works, cuz i ever try use the optimize/xrecovery and it isn't work also stuck on boot...but if only for flashing it's work smoothly. i'm sure bin4ry will fixed it
regards,,,
cruizz said:
hmmm...i hope it works, cuz i ever try use the optimize and it isn't work
regards,,,
Click to expand...
Click to collapse
I hope too, I don't have any X8 so I can't test it ;-)
so... if we want to use flashtool, how and where to get the firmware?
I've tried it on latest SEMC rom. My phone was already rooted though and I had xrecovery installed. After you check for root you can optimize (will put on jit) and I also installed the new xrecovery.
works for x8
Edit: Install script don't work for xRecovery. It picks the right files, but the script fails.
Code:
09/054/2011 23:54:55 - INFO - <- This level is successfully initialized
09/055/2011 23:55:02 - INFO - Connected device : E15
09/055/2011 23:55:02 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
09/055/2011 23:55:14 - DEBUG - <- This level is successfully initialized
09/055/2011 23:55:18 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:18 - DEBUG - stderr :7 KB/s (101 bytes in 0.014s)
09/055/2011 23:55:18 - DEBUG - Pushing .\custom\root\checkperms to /data/local/tmp/runscript
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\checkperms /data/local/tmp/runscript
09/055/2011 23:55:18 - DEBUG - stderr :0 KB/s (11 bytes in 0.011s)
09/055/2011 23:55:18 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:19 - DEBUG - stdout :uid=0(root) gid=0(root)
09/055/2011 23:55:19 - INFO - Root Access Allowed
09/055/2011 23:55:25 - INFO - Installing xRecovery to device...
09/055/2011 23:55:25 - INFO - Remounting system read-write
09/055/2011 23:55:25 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:25 - DEBUG - stderr :10 KB/s (101 bytes in 0.009s)
09/055/2011 23:55:25 - DEBUG - Pushing .\custom\root\remount to /data/local/tmp/runscript
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\remount /data/local/tmp/runscript
09/055/2011 23:55:25 - DEBUG - stderr :15 KB/s (156 bytes in 0.010s)
09/055/2011 23:55:25 - DEBUG - Running remount as root thru sysrun
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:26 - INFO - Pushing .\custom\xRecovery\xrecoveryE15.tar.gz to /data/local/tmp/xrecovery.tar.gz
09/055/2011 23:55:26 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\xrecoveryE15.tar.gz /data/local/tmp/xrecovery.tar.gz
09/055/2011 23:55:26 - DEBUG - stderr :1611 KB/s (1270848 bytes in 0.770s)
09/055/2011 23:55:27 - INFO - Pushing .\custom\xRecovery\chargemonnew to /data/local/tmp/chargemon
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\chargemonnew /data/local/tmp/chargemon
09/055/2011 23:55:27 - DEBUG - stderr :120 KB/s (741 bytes in 0.006s)
09/055/2011 23:55:27 - INFO - Pushing .\custom\xRecovery\chargerE15 to /data/local/tmp/charger
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\chargerE15 /data/local/tmp/charger
09/055/2011 23:55:27 - DEBUG - stderr :350 KB/s (14364 bytes in 0.040s)
09/055/2011 23:55:27 - INFO - Pushing .\custom\xRecovery\sh to /data/local/tmp/sh
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\sh /data/local/tmp/sh
09/055/2011 23:55:27 - DEBUG - stderr :1012 KB/s (735308 bytes in 0.709s)
09/055/2011 23:55:27 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:28 - DEBUG - stderr :14 KB/s (101 bytes in 0.007s)
09/055/2011 23:55:28 - DEBUG - Pushing .\custom\root\installrecovery to /data/local/tmp/runscript
09/055/2011 23:55:28 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\installrecovery /data/local/tmp/runscript
09/055/2011 23:55:28 - DEBUG - stderr :56 KB/s (583 bytes in 0.010s)
09/055/2011 23:55:28 - INFO - Running installrecovery as root thru sysrun
09/055/2011 23:55:28 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - INFO - xRecovery successfully installed
hmm - 2nd time i ran the script it installed. it's the removal of the temp files that fails.
I'm happy anyways
work on any devices?
wow, that good news
thanks..
oisteink said:
I've tried it on latest SEMC rom. My phone was already rooted though and I had xrecovery installed. After you check for root you can optimize (will put on jit) and I also installed the new xrecovery.
works for x8
Click to expand...
Click to collapse
glad to hear that...ready to download
@airyz :semarange endi gan?
menuju TKP gan... ama ijin sedotnya..
what does iptimize do? Does it autoinstall jit v2 for x8? does it work? Thanks
A new version (0.5.0.0) of flashtool is here
What's new for X8 comunity : BL unlock for X8 added
Androxyde said:
A new version (0.5.0.0) of flashtool is here
What's new for X8 comunity : BL unlock for X8 added
Click to expand...
Click to collapse
Thanks!!!
Here is a small update that resolves the following issue :
Device not recognized correctly when plugged.
https://github.com/downloads/Androxyde/Flashtool/Flashtool-0.5.1.0-update.exe
After the 0.5.1 update there are still issues.
not detecting properly
v291
Code:
19/002/2011 01:02:08 - INFO - <- This level is successfully initialized
19/002/2011 01:02:12 - INFO - Connected device : E15
19/002/2011 01:02:12 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
v051:
Code:
19/001/2011 01:01:03 - INFO - <- This level is successfully initialized
19/001/2011 01:01:06 - INFO - Device connected with USB debugging on
19/001/2011 01:01:08 - ERROR - Cannot identify your device.
19/001/2011 01:01:08 - INFO - Selecting from user input
19/001/2011 01:01:13 - INFO - Connected device : E15
19/001/2011 01:01:13 - INFO - Installed version of busybox : BusyBox v1.19.2-cm71 bionic (2011-10-06 22:08 +0200) multi-call binary.
19/001/2011 01:01:13 - INFO - Android version : 2.3.7 / kernel version : 2.6.29-Alfs
19/001/2011 01:01:13 - INFO - Root Access Allowed
It is not see my phone automagically, need choose it.
edit:
v5 is looking for
buildprop=ro.product.device
recognition=E15
v291 was looking for
ro.product.model as far I remember
We need update build.prop or change e15.properites
Edited file attached.
@rav3n_pl
Wow, replaced the e15 properties without installing the 0.5.1 update and my e15 is
detectable by flashtool ....Thank you.
rav3n_pl said:
v291
Code:
19/002/2011 01:02:08 - INFO - <- This level is successfully initialized
19/002/2011 01:02:12 - INFO - Connected device : E15
19/002/2011 01:02:12 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
v051:
Code:
19/001/2011 01:01:03 - INFO - <- This level is successfully initialized
19/001/2011 01:01:06 - INFO - Device connected with USB debugging on
19/001/2011 01:01:08 - ERROR - Cannot identify your device.
19/001/2011 01:01:08 - INFO - Selecting from user input
19/001/2011 01:01:13 - INFO - Connected device : E15
19/001/2011 01:01:13 - INFO - Installed version of busybox : BusyBox v1.19.2-cm71 bionic (2011-10-06 22:08 +0200) multi-call binary.
19/001/2011 01:01:13 - INFO - Android version : 2.3.7 / kernel version : 2.6.29-Alfs
19/001/2011 01:01:13 - INFO - Root Access Allowed
It is not see my phone automagically, need choose it.
edit:
v5 is looking for
buildprop=ro.product.device
recognition=E15
v291 was looking for
ro.product.model as far I remember
We need update build.prop or change e15.properites
Edited file attached.
Click to expand...
Click to collapse
what is the value you have for ro.product.device ?
the recognition property can be a coma separated list of values.
for example on X10 I have :
recognition=X10,SO-01B,es209ra
the latest one (es209ra) is the value set by FXP team for CM7 on X10
Androxyde said:
what is the value you have for ro.product.device ?
the recognition property can be a coma separated list of values.
for example on X10 I have :
recognition=X10,SO-01B,es209ra
the latest one (es209ra) is the value set by FXP team for CM7 on X10
Click to expand...
Click to collapse
In build.prop we have "shakira"
anyone has checked out if on E15 BL unlock works at all with the latest update??
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>cd android-sdk
C:\android-sdk>cd tools
C:\android-sdk\tools>fastboot.exe -i 0x0fce oem unlock 0xFF6C0B6CABAA77A3
... INFOUnlock phone requested
FAILED (remote: Phone is already unlocked!)
C:\android-sdk\tools>
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
@x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
1869 KB/s (119636 bytes in 0.062s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
2338 KB/s (1085140 bytes in 0.453s)
Pushing su binary ....
2874 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
2491 KB/s (996704 bytes in 0.390s)
Making busybox runable ...
.
Pushing fake Backup
2304 KB/s (73728 bytes in 0.031s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.VIEW dat=com.sonyericsson.vendor.ba
ckuprestore/.ui.BackupActivity }
Error: Activity not started, unable to resolve Intent { act=android.intent.actio
n.VIEW dat=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity flg=0x100000
00 }
If all is successful i will tell you, if not this shell will run forever.
Running ......
05/040/2012 07:40:56 - INFO - <- This level is successfully initialized
05/040/2012 07:40:56 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:35:32
05/040/2012 07:40:56 - INFO - You can drag and drop ftf files here to start flashing them
05/040/2012 07:40:58 - INFO - Device connected with USB debugging on
05/040/2012 07:40:59 - INFO - Connected device : ST25
05/040/2012 07:40:59 - INFO - Installed version of busybox : N/A
05/040/2012 07:40:59 - INFO - Android version : 2.3.7 / kernel version : 2.6.35.7+ / Build number : 6.0.B.3.184
05/041/2012 07:41:02 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\.\devices\ST25\busybox\1.19.0\busybox to /data/local/tmp/busybox
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
05/041/2012 07:41:07 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
05/041/2012 07:41:07 - INFO - Running part1 of Root Exploit, please wait
05/041/2012 07:41:26 - INFO - Waiting for device. After 60secs, stop waiting will be forced
05/042/2012 07:42:30 - INFO - Forced stop waiting.
05/042/2012 07:42:30 - ERROR - The part1 exploit did not work
05/042/2012 07:42:30 - INFO - Cleaning files
I want to root my phone mainly to clean **** like facebook and other which eat ram in stock rom. After that all i dont have any icons from supersu/superuser in list. In bin4ry script nothing happen but its supposed to show backup and restore window i think.
The method works only on ICS
Tapatalked !
Ok problem solved i uploaded rooted kernel for gb. And now all works fine. Topic can be closed or go to trash, thanks for reply.
I try many others softwares and instructions that found on WEB, but no success.
This is my SRS log:
---------------------------------------------------------------------------------------------
---= SRS One-Click-Root v4.6 =---
11:24:25 - Starting ADB Server..
11:24:31 - Manufacturer: alps
11:24:31 - Model: S3
11:24:31 - Android Version: 4.0.1
11:24:32 - Build ID: ALPS.GB2.MP.V2.8
11:24:32 - Board ID: gaophone15_6628_gb2
11:24:32 - Chipset Platform:
11:24:32 - Getting OffSets.. : Not found
11:24:34 - Query Server for Best Method.. Found Rootkit: 4
----= Start Rooting Process.. Please Wait =----
11:24:34 [+] Testing exploit: root4 (please wait..)
11:24:37 [+] Device Reboot #1 (Wait till it's started)
11:26:50 [+] Executing root4 exploit Failed.
11:26:50 [+] Testing exploit: root4b (please wait..)
11:26:58 [+] Device Reboot #1 (Wait till it's started)
11:29:26 [+] Device Reboot #2 (Wait till it's started)
11:32:53 [+] Testing exploit: root5 (please wait..)
11:32:54 [+] Unlock your device screen, it should bring up restore mode.
11:34:36 [+] Press RESTORE button on device NOW! then wait...
11:35:08 [+] Device Reboot #1 (Wait till it's started)
11:36:38 [+] Executing root5 exploit Failed.
11:36:38 Auto Root Failed on this device.
11:36:38 Rebooting Device and try again...
---------------------------------------------------------------------------------------------
You can see that in time
11:32:54 [+] Unlock your device screen, it should bring up restore mode.
11:34:36 [+] Press RESTORE button on device NOW! then wait...
But my phone not automatic in RESTORE mode as waited.
Someone can help me? (sorry for my bad english)
Thanks
Try this one..
No need computer..
http://forum.xda-developers.com/showthread.php?t=833953
Sent from my Phone
---= SRS One-Click-Root v4.7 =---
12:09:38 - Starting ADB Server..
12:09:44 - Manufacturer: alps
12:09:45 - Model: e1901_v77_jbla668_fwvga
12:09:45 - Android Version: 4.1.1
12:09:45 - Build ID: e1901_v77_jbla668_fwvga_20130116
12:09:45 - Board ID: e1901_v77_jbla668_fwvga
12:09:45 - Chipset Platform:
12:09:45 - Getting OffSets.. : 0x8003 0x8005 (False)
12:09:47 - Query Server for Best Method.. Found Rootkit: 4
----= Start Rooting Process.. Please Wait =----
12:09:47 [+] Testing exploit: root4 (please wait..)
12:09:51 [+] Device Reboot #1 (Wait till it's started)
12:10:39 [+] Device Reboot #2 (Wait till it's started)
12:13:44 [+] Executing root4 exploit Failed.
12:13:44 [+] Testing exploit: root4b (please wait..)
12:13:44 [+] Executing root4b exploit Failed. (mount not found)
12:13:44 [+] Testing exploit: root5 (please wait..)
12:13:45 [+] Unlock your device screen, it should bring up restore mode.
12:13:54 [+] Press RESTORE button on device NOW! then wait...
12:14:05 [+] Device Reboot #1 (Wait till it's started)
12:14:17 [+] Remounting /system Filesystem as R/W..
12:14:18 Error: Failed to remount filesystem
Hello.
I need help with install ubuntu touch on nexus 72013(flo).After unlock bootloader and flash image, the device stuck on boot screen .I tried both stable and rc channel but i got the same problem.
Thanks in advance !
Sorry for my bad English.
https://drive.google.com/file/d/1w5M3mEuMc5CvdTW_vdJhiUGISGvux3ra/view?usp=sharing
this is log
Unlock boot loader
Code:
[email protected]:~$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0736dfd0 unauthorized
[email protected]:~$ adb devices
List of devices attached
0736dfd0 device
[email protected]:~$ adb reboot bootloader
[email protected]:~$ sudo fastboot oem unlock
[sudo] password for chip:
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader done!
OKAY [ 11.612s]
finished. total time: 11.612s
[email protected]:~$
Install image
Code:
[email protected]:~$ ubuntu-device-flash touch --channel=ubuntu-touch/rc/ubuntu --bootstrap
2018/04/16 11:45:41 Expecting the device to be in the bootloader... waiting
2018/04/16 11:45:41 Device is |flo|
2018/04/16 11:45:42 Flashing version 45 from ubuntu-touch/rc/ubuntu channel and server https://system-image.ubuntu.com to device flo
20.41 MB / 20.41 MB [=======================================] 100.00 % 3.25 MB/s
55.05 MB / 55.05 MB [=======================================] 100.00 % 1.92 MB/s
316.54 MB / 316.54 MB [=====================================] 100.00 % 2.83 MB/s
/home/chip/.cache/ubuntuimages/gpg/image-master.tar.xz
/home/chip/.cache/ubuntuimages/gpg/image-signing.tar.xz
/home/chip/.cache/ubuntuimages/ubuntu-touch/rc/ubuntu/flo/version-45.tar.xz
/home/chip/.cache/ubuntuimages/pool/custom-2369a9a834acd3c434fec12da7c59560797532e5a08f046fbe5b02857a8e4424.tar.xz
/home/chip/.cache/ubuntuimages/pool/device-1d88c67d0daa4d0403ebf3bdab8f0ac5c27f3cda3d4b45302ba4a021ec0f1a73.tar.xz
2018/04/16 11:47:58 Start pushing /home/chip/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2018/04/16 11:47:58 Start pushing /home/chip/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2018/04/16 11:47:58 Start pushing /home/chip/.cache/ubuntuimages/ubuntu-touch/rc/ubuntu/flo/version-45.tar.xz to device
2018/04/16 11:47:58 Done pushing /home/chip/.cache/ubuntuimages/ubuntu-touch/rc/ubuntu/flo/version-45.tar.xz to device
2018/04/16 11:47:58 Done pushing /home/chip/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2018/04/16 11:47:58 Done pushing /home/chip/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2018/04/16 11:47:58 Start pushing /home/chip/.cache/ubuntuimages/pool/custom-2369a9a834acd3c434fec12da7c59560797532e5a08f046fbe5b02857a8e4424.tar.xz to device
2018/04/16 11:47:58 Start pushing /home/chip/.cache/ubuntuimages/pool/device-1d88c67d0daa4d0403ebf3bdab8f0ac5c27f3cda3d4b45302ba4a021ec0f1a73.tar.xz to device
2018/04/16 11:47:58 Start pushing /home/chip/.cache/ubuntuimages/pool/ubuntu-d8d097dfc125dc91455594656762421ba6ac8fbf19524bfa07db1a879d0adee1.tar.xz to device
2018/04/16 11:48:08 Done pushing /home/chip/.cache/ubuntuimages/pool/custom-2369a9a834acd3c434fec12da7c59560797532e5a08f046fbe5b02857a8e4424.tar.xz to device
2018/04/16 11:48:19 Done pushing /home/chip/.cache/ubuntuimages/pool/device-1d88c67d0daa4d0403ebf3bdab8f0ac5c27f3cda3d4b45302ba4a021ec0f1a73.tar.xz to device
2018/04/16 11:49:03 Done pushing /home/chip/.cache/ubuntuimages/pool/ubuntu-d8d097dfc125dc91455594656762421ba6ac8fbf19524bfa07db1a879d0adee1.tar.xz to device
2018/04/16 11:49:03 Created ubuntu_command: /home/chip/.cache/ubuntuimages/ubuntu_commands200797069
2018/04/16 11:49:03 Rebooting into recovery to flash
[email protected]:~$
UPDATE ----------------------------------
I found the solution.The image file from https://system-image.ubuntu.com not working.Use image file http://system-image.ubports.com slove the problem.
Code:
$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --channel=ubports-touch/15.04/devel --device=flo --bootstrap --wipe
here is the guide to install ubuntu on nexus7 2012/2013
https://github.com/ChipTechno/2018-Guide-to-Install-Ubuntu-desktop-13.04-on-Nexus-7-2012-and-Ubuntu-touch-15.04-on-Nexus-7-2013