Trying to boot nexus 9

Carlo

Hi everyone, I was almost successful in building for nexus 9. I am stuck on the Google splash screen and can't proceed. I tried:

sudo ip link set enp3s0f3u2 address 02:11:22:33:44:55

But I got: RTNETLINK answers: Device or resource busy

So I decided to try with

telnet 192.168.2.15

But i got: no connection to host.

How can I get an error log?

I should also say that halium-install in my case was very fast but gave me no errors, so mabye is some bug related to that?

Thanks.

nero355

@carlo
Sometimes you need to bring a device DOWN first, then reconfigure it, then bring it back UP again to be able to use it!

Have you tried that ?!

Also please read my post in a different topic to avoid future issues : https://forums.ubports.com/topic/7116/ubuntu-touch-on-the-galaxy-s5-help/3?_=1639591933932

Carlo

@nero355 I've just tried and it did not work. Also I forgot to say that halium-install does not let me set the password.

I've managed to get some logs via journalctl:

dic 16 15:19:45 fedora gvfsd[8127]: Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
dic 16 15:19:47 fedora ModemManager[1074]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb1/1-2': not supported by any plugin
dic 16 15:19:52 fedora gnome-shell[2194]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
dic 16 15:19:55 fedora systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

Also I have no idea why it gets the wrong device.

Carlo

I got some more logs so you can see all that's happening:

dic 16 15:37:02 fedora kernel: usb 1-2: new high-speed USB device number 47 using xhci_hcd
dic 16 15:37:02 fedora kernel: usb 1-2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice=ff.ff
dic 16 15:37:02 fedora kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
dic 16 15:37:02 fedora kernel: usb 1-2: Product: Failed to boot
dic 16 15:37:02 fedora kernel: usb 1-2: Manufacturer: Halium initrd    gr8rFiV8US03C03C00
dic 16 15:37:02 fedora kernel: usb 1-2: SerialNumber: Halium initrd Debug telnet on port 23 on rndis0 192.168.2.15 - also running udhcpd
dic 16 15:37:02 fedora kernel: rndis_host 1-2:1.0 usb0: register 'rndis_host' at usb-0000:03:00.3-2, RNDIS device, c2:83:f6:73:cf:50
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.3123] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/28)
dic 16 15:37:02 fedora colord[1762]: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorMan>
dic 16 15:37:02 fedora systemd-udevd[9243]: Using default interface naming scheme 'v249'.
dic 16 15:37:02 fedora kernel: rndis_host 1-2:1.0 enp3s0f3u2: renamed from usb0
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9745] device (usb0): interface index 28 renamed iface from 'usb0' to 'enp3s0f3u2'
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9925] device (enp3s0f3u2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9941] device (enp3s0f3u2): carrier: link connected
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9963] settings: (enp3s0f3u2): created default wired connection 'Connessione via cavo 1'
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9999] device (enp3s0f3u2): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0024] policy: auto-activating connection 'Connessione via cavo 1' (bc8c336a-c799-33eb-833a-f38be331eca4)
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0035] device (enp3s0f3u2): Activation: starting connection 'Connessione via cavo 1' (bc8c336a-c799-33eb-833a-f38be331eca4)
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0039] device (enp3s0f3u2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0047] device (enp3s0f3u2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0142] device (enp3s0f3u2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0145] dhcp4 (enp3s0f3u2): activation: beginning transaction (timeout in 45 seconds)
dic 16 15:37:03 fedora avahi-daemon[982]: Joining mDNS multicast group on interface enp3s0f3u2.IPv6 with address fe80::aef4:93bf:a70f:ef26.
dic 16 15:37:03 fedora avahi-daemon[982]: New relevant interface enp3s0f3u2.IPv6 for mDNS.
dic 16 15:37:03 fedora avahi-daemon[982]: Registering new address record for fe80::aef4:93bf:a70f:ef26 on enp3s0f3u2.*.
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0363] dhcp4 (enp3s0f3u2): state changed unknown -> expire
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1035] dhcp4 (enp3s0f3u2): state changed expire -> bound, address=192.168.2.61
dic 16 15:37:03 fedora avahi-daemon[982]: Joining mDNS multicast group on interface enp3s0f3u2.IPv4 with address 192.168.2.61.
dic 16 15:37:03 fedora avahi-daemon[982]: New relevant interface enp3s0f3u2.IPv4 for mDNS.
dic 16 15:37:03 fedora avahi-daemon[982]: Registering new address record for 192.168.2.61 on enp3s0f3u2.IPv4.
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1055] device (enp3s0f3u2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1092] device (enp3s0f3u2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1095] device (enp3s0f3u2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1106] device (enp3s0f3u2): Activation: successful, device activated.
dic 16 15:37:03 fedora systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
dic 16 15:37:05 fedora ModemManager[1074]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb1/1-2': not supported by any plugin

I can see that the device is not booting and also when I try to connect via telnet the connection is dropped by the device.

nero355

@carlo
I am not sure if it's applicable to this situation but usually you have to Remove Modem Manager when you are messing around with phones and flashing them on a Linux based system : Have you tried that ?!

Carlo

@nero355 I have not yet tried that. How should I do it?

nero355

@carlo
It was mentioned here when I was flashing my BQ phone back to the old Canonical Ubuntu Touch so that I could use the UBports Installer to flash the UBports Ubuntu Touch version : https://docs.ubports.com/en/latest/userguide/install.html#install-on-legacy-android-devices
It links to : https://web.archive.org/web/20180118130643/http://www.mibqyyo.com/en-articles/2015/09/16/ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5/
So just do this :

sudo apt-get remove modemmanager

Or any of the following options : https://askubuntu.com/questions/216114/how-can-i-remove-modem-manager-from-boot
With my favorite beeing this one :

sudo apt-get purge modemmanager

It should delete it completely without anything of it left on your system!

Good luck!

Carlo

@nero355 I tried but got same error, but I may be onto something. I run halium-install in verbose mode and I got this error:

D: Chosen rootfs is ../ubuntu-touch-android9-arm64.tar.gz
D: Chosen android image is ../GSI/system/var/lib/lxc/android/android-rootfs.img
D: Chosen release is ut
D: Compress images before pushing: false

I: Writing rootfs into mountable image
Formatting '.halium-install-imgs.Jb3Is/rootfs.img', fmt=raw size=3221225472
mke2fs 1.45.5 (07-Jan-2020)
Discarding device blocks: done                            
Creating filesystem with 786432 4k blocks and 196608 inodes
Filesystem UUID: 80532b4d-daba-4b3e-a4ca-92c1846aaa89
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 


gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
I: Cleaning up

So the problem is that, other than the boot image, nothing is being flashed. I have no idea of how to fix this though.

EDIT: ubuntu-touch-android9-arm64.tar.gz Was corrupted LOL, I am in pain.
EDIT 2: Now halium-install is really flashing the image. Will update you as soon as I try booting it up.

nero355

@carlo said in Trying to boot nexus 9:

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

That look a bit like the bunzip2 issue I had with my Jolla Sailfish ROM : The tar -x command counts on the file to be gzipped but it was bzipped so I got Error 7 in TWRP over and over again!

Can you unpack/repack the file into a regular .tar file and edit the associated scripts to refer to that new file by any chance ?!

Carlo

@nero355 It "worked" but still not booting. Mabye some depencencies are missing.

NVriezen

@carlo You can connect through telnet right?
If you can, do dmesg there and drop the output in a pastebin.
Then drop the link here so we can watch along what happens during boot.

Carlo

@nvriezen No, telnet does not work (host closes the session)

NVriezen

@carlo said in Trying to boot nexus 9:

@nero355 It "worked" but still not booting. Mabye some depencencies are missing.

What worked exactly then?
Did the flashing return without errors?

If so, maybe something went wrong with making halium-boot.
Make sure that when running the kernel configuration test there are no red lines popping up.
If there are, even though the script says no errors were found, you need to fix them.

Carlo

@nvriezen I will try again. The script is not returning errors found anymore so I will look for red lines

Carlo

There is a thing I didn't see the first time. When I run breakfast flounder it sayes: Trying dependencies-only mode on a non-existing device tree. What does it mean?

NVriezen

@carlo said in Trying to boot nexus 9:

There is a thing I didn't see the first time. When I run breakfast flounder it sayes: Trying dependencies-only mode on a non-existing device tree. What does it mean?

I get that same message. As far as I know that doesn't matter and you can just ignore it.
If no other errors are popping up then the only thing I can recommend is going to the Telegram group and ask for help there.
They already helped me out twice when I really was stuck and didn't have any clue anymore.

NVriezen

@Carlo Did you apply the hybris patches btw?
You definitely need those and may solve the issue if you haven't applied them yet.

Carlo

@nvriezen I did. Thanks for the help btw, I will ask on telegram and post the answer if I find it

Carlo

@carlo I surrender for now. Probably some dependencies are missing.