Hi,

just to let you know this problem has been solved for me by upgrading to 20.04 base (OTA-3). I had to re-enable developer mode after the upgrade.

For some reason device is weirdly named by lsusb, but transfering files works again, adb shell too.

@maceda said in Bricked BQ Aquaris M10 when installing:

I'll try to migrate it to the last version as soon as I have some experience with that.

Let us know how it goes! Personally I'm not comfortable installing anything if it can´t be done with the installer.

@augi Welcome to the forums.

You can, but it would mean remounting the root filesystem read/write, modifying your /etc/hosts file and then remounting the root filesystem read-only again.

Also your changes might be overwritten / reverted when you update the OS via the Settings (never use apt unless you know what you are doing)

The uAddBlock app in the OpenStore works in this way.

@YangTegap if it is stuck at the bootloader unlocked screen, all is not lost. It looks like you were not on the correct Stock ROM. The device has to be on Android 9 for UT to install. Go to XDA- developers forum and search for the correct ROM and you can flash it through fastboot.

If the device sticks at dm-verity, it usually means the battery is on its way out.

Link to XDA forum here.

Flash back to Android 9 and set it up, then start the UT install again.

@arubislander Thank you so much....that worked!

Thank you both.
I've figured out what the issue is.
The Installer for MacOS has been compiled for Intel processors.
It does not work with the new M1 chip.
Either due to incompatibility with the new chip, or Rosetta is unable to work via USB Debugging/ADB for some reason.
When I tried to install using an old Macbook Air with an Intel processor, then the installation worked.

@djjonas13 said in Vaio TL10:

Estou querendo colocar em um Tablet Vaio TL10, o Ubuntu Touch, ele suporta?

"I want to put Ubuntu Touch on a Vaio TL10 Tablet, does it support it?"

No, that is not a supported device. You can see which devices are supported on the device page.

And please post in English in these forums, because that is the language that is spoken here. Thank you!

@arubislander Thank you!

@MrT10001, my deep respect! It worked!

Thank you so much!

@MrT10001 Thanks for the tip, much appreciated.

@PublicLewdness If you have got to Recovery, erase (format) the DATA partition and try again. It is common to say the device is unsupported in the Installer if you have the device at Fastboot. Just manually select it from the devices drop down box.

@DPITTI

Yes miatoll support wireless display on the devel channel as I pointed out in my first replay. This feature was implemented about month ago on the focal port. It is also available on the xenial port from long time.

@domubpkm

Hmmm... that's unfortunate. Though under Xenial (on my Nexus 5), i at least received a notification error. So i knew someone tried to send me something.

The problem now is i don't even get an error. So I won't ever know that a group message was ever attempted. And i can't ask the sender to send individually if i don't know that they've tried to send me something.

So this is a bit of a pickle... Hmmmm.

-Fizz

@Dunbrokin Seems like, as with your OP1 a reflash with the installer is warranted.

@danfro Lots of gain. Thanks.

Thanks for the replies. Bluetooth does work, it's just a matter of whether i can get regular system sounds from UT (for example, the Clock alarm) to work while connected to Bluetooth.

Getting Bluetooth phone audio to work seems to require both HFP and A2DP to be enabled. But doing so seems to force linux to try to send ALL sounds to the car, but only the phone sounds are being heard. To continue my example- when the UT Clock alarm goes off, there is no noise- neither from the phone or through the car.

I realize there is the car side to consider too, which is beyond the purview of the help boards. 🙂 But i was hopefull someone had some idea of how to resolve it.

-Fizz

@Fizz That is an interesting way of going about it. But I guess it works.

In general though, changing ownership / permissions of system files is not recommended, so be sure to change them back to what they were when you are done editing them.