Focal and Waydroid news for Lenovo X605

Luksus

Hey,

there are first working focal-builds for the X605.
Who want's to try it, needs to download the devel-flashable-focal:archive of the latest focal branch build, from this site:
https://gitlab.com/ubports/porting/community-ports/android9/lenovo-tab-m10-fhd/lenovo-x605/-/pipelines

And then flash boot.img to boot partition and ubuntu.img to system partition using fastboot.

I won't give instructions how to use fastboot. That is not for users who might fear a data loss or similar.

That said, you all may know, that booting the X605 can be a pain in the ass, when it once refused to boot.
So this can also be the result of flashing the focal builds.

What does not work

That list maybe continued.

~~WiFi only seems to work on first boot~~
Granting hardware-access-permission to apps does not work on first boot?!
Camera shows no image, can't take any photos/videos
~~lockscreen appears always upside down (seems like global issue to me)~~
once, after sleep, the display stayed black (maybe it has something to do with waydroid running in background), after reboot the device booted successfully again (yay!)

So there are still some annoying random quirks.

But there is also good news: Waydroid works :astonished_face:

Resonus

Hello.
I've got a X605L with 9, I tried the ubports installer, that failed.
Managed to figure out manually installing which seemed to work, but won't boot.
Manually installing I get a error at format:ext4 userdata
Everything else seems okay.

Then I tried flashing the ROW but when I run the qdl command I get
Waiting for EDL device
*** buffer overflow detected ***: terminated
Aborted (core dumped)

At which point I'm a bit lost. A little help?
Thank you.
Lee.

Luksus

@resonus said in Focal and Waydroid news for Lenovo X605:

I tried the ubports installer, that failed.

Do you maybe have the model with 2GB ram?

Regarding QDL:
Can you please describe the exaxt steps you took?

Resonus

@luksus Thanks for responding.

I've installed the qdl utility.
Tablet is a 3GB RAM - 32GB ROM version.
Pretty sure I'm not doing the qdl bit right. I've downloaded and extracted the ROW.
Installed qdl and run 'qdl prog_emmc_firehose_8953_ddr.mbn rawprogram_unsparse_upgrade.xml patch0.xml' from the top level folder of the ROW.

I get the error.
Waiting for EDL device
*** buffer overflow detected ***: terminated
Aborted (core dumped)

Even before I've tried to connect the Tablet. I've read all I can online about installing and using qdl. I'm running Ubuntu.

Lee.

Luksus

@resonus
So before connecting, the device needs to be turned off.
And when connecting hold both volume buttons pressed until qdl tool on pc starts to do something.

If you did it like that, maybe your qdl tool is broken. Did you install it through snap?

Resonus

@luksus Hi.
Yes, I did through snap.
I did get the Tab into edl mode, but connected or otherwise I get the same error.
Is there a step by step (idiots) guide to installing and using? Sure I've miss-stepped somewhere.
L.

Luksus

@resonus if you can, try to compile the qdl utility by yourself and use this version.
That worked for me when I had issues with precompiled qdl packages.
You can follow this guide:
https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md

Resonus

@luksus
Tried a couple of things, got the same error using the compiled qdl utility.
So I thought I'd try a different machine entirely. I have a spare Pi hanging around, gave it a fresh install and installed qdl and curiously got the exact same error.
Waiting for EDL device
*** buffer overflow detected ***: terminated
Aborted
At least I'm consistent!
L.

Luksus

@resonus I tried to write down my step on flashing the X605 here:
https://forums.ubports.com/post/71223

Please lets move the discussion there, if you have further questions regarding qdl.

muskist

@luksus
Thanks for the instructions!
Is it possible to do this on a 2GB-device? The device can't be booted to recovery if it's a UT-recovery. But is that even necessary?

Luksus

@muskist No, recovery is not necessary.
You can flash boot and system partitions on the 2GB version too.
You just won't get ever OTA updates for it.

muskist

@luksus
Thanks! I'll give it a try.

muskist

@luksus
Installed it and it booted!

How did you install waydroid? The old way:

sudo -s
mount -o remount,rw /
apt update
apt install waydroid -y
waydroid init

?

Luksus

@muskist no, waydroid is already installed.

just do sudo waydroid init or use the waydroid helper app.

muskist

@luksus
Thx!

muskist

@luksus
Sadly I get command not found when doing sudo waydroid init

Sure Waydroid is installed? Or is it not in $PATH?

Luksus

@muskist thats strange, are you sure you downloaded and installed the Focal build and not Xenial?
I am sure, that waydroid should be installed as default and accessible from the terminal.

muskist

@luksus said in Focal and Waydroid news for Lenovo X605:

@muskist thats strange, are you sure you downloaded and installed the Focal build and not Xenial?

Good question! I was able to install TELEports for 20.04 (v1.17.1) so I thought it's 20.04.

But UT Tweak Tool told me it's 16.04.7 LTS. And Waydroid didn't show up.

So I downloaded the artifacts.zip again from the link you gave above. I chose the latest one saying "passed" and "devel-flashable: archive". Maybe that's the wrong one?

EDIT: Just saw it: "devel-flashable:archive" != "devel-flashable-focal:archive" - sorry for the fuss! I'll try again.

Still wondering about TELEports v1.17.1 ...

Luksus

@muskist yes, the latest build is marked as canceled, but I just canceled the xenial build, you can still download the flashable-focal zip.

I know it is a little bit confusing.

muskist

@luksus
Unfortunately it doesn't work.

After flashing boot.img and ubuntu.img and doing fastboot reboot
the device gets stuck in a loop:

starting with vibration
showing the "Lenovo" screen for about 40 seconds
screen goes dark
starting with vibration
showing the "Lenovo" screen for about 40 seconds
...

I suppose you did it on a 3GB/32GB device?
Maybe it's the known unsuitability of the 2GB/16GB device.

I will stop trying unless you have another tip. But please don't waste your time on this! You're doing great work on the 3GB/32GB device (and I have one of those, too )!