How to determine what went wrong

genifycom

I am using a new Nexus 7 2013 (WiFi)
PRODUCT NAME - flo
LOCK STATE - unlocked
which I purchased specifically for Ubuntu Touch.

I have now tried the UBports Installer 0.1.21-beta for Windows (USB cable directly attached to the Nexus 7) and Ubuntu 18.04.2 LTS running in a VirtualBox.

They both do not detect the Nexus 7 despite adb and fastboot correctly interfacing to the Nexus 7.

Is there a debugging log that I can trace what is happening?

Lakotaubp

@genifycom Try just using windows and this https://forum.xda-developers.com/showthread.php?t=2588979it worked for me. If not I think your better off with a live usb stick with Ubuntu 16.04 on it plus adb and fastboot

Ingo

The log is in ~/.cache/ubports/ubports-installer.log on Linux and %APPDATA%\.cache\ubports\ubports-installer.log on Windows.

If you are interested, there is sort of a pre-release of the installer at https://ci.ubports.com/blue/organizations/jenkins/ubports%2Fubports-installer/detail/PR-611/1/artifacts (linux) or https://ci.appveyor.com/project/mariogrip/ubports-installer/builds/21559497/artifacts (windows). It has more logging to better find out why installation fails. The changes included there will be in 0.1.22 but that is yet to be released.

Lakotaubp

Why no ZIP files?

genifycom about 13 hours ago

Just recently purchased a Nexus 7 specifically for Ubuntu Touch. Here are the details shown on fastboot

Just recently purchased a Nexus 7 specifically for Ubuntu Touch. Here are the details shown on fastboot

FASTBOOT MODE
PRODUCT NAME - flo
VARIANT - flo 32G
HW VERSION - rev_e
BOOTLOADER VERSION - FLO-04.08
CARRIER INFO - None
SERIAL NUMBER - 000xxxxx
SIGNING - Yes
SECURE BOOT - enabled
LOCK STATE - unlocked

Has anyone else successfully installed Ubuntu Touch on this specific device (with HW VERSION rev_e)?

UBPorts Installer (ubports-installer.0.1.21-beta.exe) never recognizes the device and manually selecting Nexus 7 (wifi) the installer does not proceed past the "Please reboot to bootloader".

ubports/ubports-installer.log says:

{"level":"debug","message":"Welcome to the party","timestamp":"2019-03-08T20:34:31.546Z"}
{"level":"debug","message":"Killing all running adb servers...","timestamp":"2019-03-08T20:34:32.625Z"}
{"level":"debug","message":"Using fallback platform tools!","timestamp":"2019-03-08T20:34:32.853Z"}
{"level":"debug","message":"","timestamp":"2019-03-08T20:34:33.100Z"}
{"level":"debug","message":"","timestamp":"2019-03-08T20:34:33.374Z"}
{"level":"debug","message":"adb shell: echo 1","timestamp":"2019-03-08T20:34:33.650Z"}
{"level":"debug","message":"Successfully downloaded devices list","timestamp":"2019-03-08T20:34:33.913Z"}
{"level":"warn","message":"Running latest stable version.","timestamp":"2019-03-08T20:34:34.299Z"}

"Command failed: ...\Temp\edb02a4d-570a-4d90-b599-a4da912530d9.tmp.exe -P 5038 shell echo 1\n* daemon not running; starting now at tcp:5038\r\n* daemon started successfully\r\nerror: no devices/emulators found\r\n","stack"

Since the installer does not work on either Windows or Linux (I have tried both), where are the ROM zips to manually install?

It is not a good idea to only have the installer option.

0

Lakotaubp about 13 hours ago

@genifycom Ubuntu Touch is not a rom. You only need the installer but the Nexus 7 can be a bit awkward. With Windows are you using https://forum.xda-developers.com/showthread.php?t=2588979 I installed with Windows and version 0.1.20 if the installer and it took 10-12 attempts. Try different usb cables, you can put the device into bootloader manually. Mine stuck after installing the UBports recovery and the cache had to be cleared before it completed.
On another note why start another thread on the same subject it only confuses the issue.

doniks about 10 hours ago

@genifycom can you adb? Independently of the recovery?

genifycom

@Lakotaubp Can you explain a little more please in saying that Ubuntu Touch is not a ROM. IIRC, LineageOS, for example, has an Android Custom ROM. I assume that this means that the booloader loads some Android and then the custom ROM?

So in the case of Ubuntu Touch, if you say it is not a ROM, then the bootloader loads the Ubuntu Touch Image directly and does not use any underlying Android components?

I have done plenty of work on Microcomputers (assembler) and Operating Systems. It is just the new terminology associated with Android that is confusing me.

I appreciate your help.

advocatux

@genifycom hi, Ubuntu Touch is not a ROM in the classic sense. The UBports recovery is necessary to make the installation work. You can't use TWRP for example to install some zip file, nor we can make such zip

Ingo

Looks like manual install instructions are coming: https://github.com/ubports/devices.ubuntu-touch.io/pull/15

genifycom

Cannot WGET the images

"C:\Program Files (x86)\GnuWin32\bin\wget" https://system-image.ubports.com//pool/ubports-b2daf85c2a255a0affc93d808e709697e472777de4bc189dd9128211db551469.tar.xz -O pool/ubports-b2daf85c2a255a0affc93d808e709697e472777de4bc189dd9128211db551469.tar.xz && echo "a1a0e2e7d5e2e242b11e7a2fabbabeaaffa7b62fa8b0b014f25b92e0ed888437 pool/ubports-b2daf85c2a255a0affc93d808e709697e472777de4bc189dd9128211db551469.tar.xz" | sha256sum -c --no-check-certificate

SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = C:\Program Files (x86)\GnuWin32/etc/wgetrc
--2019-03-15 11:35:32-- https://system-image.ubports.com//pool/ubports-b2daf85c2a255a0affc93d808e709697e472777de4bc189dd9128211db551469.tar.xz

Resolving system-image.ubports.com... 104.27.43.113, 104.27.42.113
Connecting to system-image.ubports.com|104.27.43.113|:443... connected.
ERROR: cannot verify system-image.ubports.com's certificate, issued by /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO Domain Validation Legacy Server CA 2': Unable to locally verify the issuer's authority. ERROR: certificate common name ssl388182.cloudflaressl.com' doesn't match requested host name system-image.ubports.com'. To connect to system-image.ubports.com insecurely, use --no-check-certificate'.
Unable to establish SSL connection.

Ingo

I guess it should be

"C:\Program Files (x86)\GnuWin32\bin\wget" --no-check-certificate https://system-image.ubports.com//pool/ubports-b2daf85c2a255a0affc93d808e709697e472777de4bc189dd9128211db551469.tar.xz -O pool/ubports-b2daf85c2a255a0affc93d808e709697e472777de4bc189dd9128211db551469.tar.xz && echo "a1a0e2e7d5e2e242b11e7a2fabbabeaaffa7b62fa8b0b014f25b92e0ed888437 pool/ubports-b2daf85c2a255a0affc93d808e709697e472777de4bc189dd9128211db551469.tar.xz" | sha256sum -c

i.e. the --no-check-certificate is an option for wget, no sha256sum