Trying to boot nexus 9

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.