Cannot install ubuntu touch on BQ M10 ubuntu edition

A Former User

Thanks, I have tried the appimage before and I have swapped cables and usb ports.
At the moment I have 0.1.20-beta from mariogrip refreshed. Although the pop-up prompting a refresh comes every time the installer is launched.
Typing adb devices returns 'list of devices attached' and I can't see anything! Should I ?

A Former User

@Lakotaubp I unistalled ubports installer and downloaded the appimage which I ran from my downloads folder.
Still no go.
I've also seen an example of what the adb devices command returns when it recognises something so I guess it is not seeing the tablet?
Tried two cables and usb ports. Going to look for another cable now...

Lakotaubp

@ziggutas Try the link in my post the latest installer is 0.1.21. Yes you should see your device in the adb list. check you have correct adb tools installed. You should also have had a small dialogue box pop up asking you to grant permission for the pc to access the m10. Try that and see what happens

Lakotaubp

@ziggutas that permissions box was hard to find. I never did on Ubuntu I had to use Linux Mint. Please try the telegram group for help on that I just cant remember how to sort it on Ubuntu at the moment. check how to grant adb permissions on Ubuntu on the net. I really think that is your problem. Sorry can't help further just now back off to work. Will be here later if your still stuck

Marathon2422

sounds like you are not getting adb connecting,you should get a small window appear in the top right corner asking to ALLOW connections to your pc .
it will be explain in support ,in one of the previous m10 posts

Lakotaubp

@marathon2422 Agree. @ziggutas use the search feature on the forum to find m10 adb permission post

A Former User

@lakotaubp @Marathon2422 , Thanks. Looked at the M10 post and tried that. No change. But I notice on the github page (link in earlier reply) some troubleshooting info for linux:

If the device not detected, you might be missing udev-rules.

See if cat /etc/udev/rules.d/51-android.rules exists and contains the rules below. If not, add them to the file and run sudo service udev restart.

I ran the command and it returned: No such file or directory.

Lakotaubp

@ziggutas https://forums.ubports.com/topic/1385/bq-m10-hd-adb-does-not-work
https://forums.ubports.com/topic/767/can-t-flash-my-bq-m10-fhd-with-ubports/4
have a read they might help. there are other adb post on the forum have a search back again later

Marathon2422

Just a thought ,once you get developer mode ,on, and get the allow box clicked on ,you should reboot,before you run ubports installer

Lakotaubp

And don't connect the device before the installer is running and asks you too

Pulsar33

Pulsar33 said in UBports for BQ E5 : all you need to know:

What succeeded (with UBports-installer and Mint 18.3 64 bits) : (for BQ E5 Ubuntu Edition)

Power on the BQ E5 and set Developper Mode (SystemPreferences/About/DevelopperMode)

Open a Mint terminal and type adb devices : this launches the adb daemon. No device found

Connect the BQ E5 (always powered on) to the desktop

Type adb devices once more : the device is listed

A question appears on the BQ E5 with a key : you have to grant the connexion

At this point, launch UBports installer : quick automatic detection !...

The installer displays a "Switch to UBports" option : select it then install

The BQ E5 is switched to Bootloader Mode automatically

Then follow the indications (the password requested is the one of your desktop, not the one of your BQ)

12 files Downloaded (the first one is long with ADSL), then 13 files pushed to the device (quicker)

Then the device reboots and installs the files (about 5 minutes), then reboots once more running UBports
You're done !

Why should it be different for BQ M10 Ubuntu Edition if you do exactly the same ?
Best regards. Pulsar33

A Former User

@Lakotaubp Tried what I could from the two links. Nothing changed. Made sure to run installer before connecting. No detect. @Marathon2422 I hadn't tried rebooting the tablet after selecting developer mode and connecting to installer. Tried that, but nothing changed. @Pulsar33 followed your steps to try and see if device would be listed, but no, it's not.

adb version:Android Debug Bridge version 1.0.36
Revision 1:7.0.0+r33-2

I've added the udev-rules suggested in the troubleshooting section for linux on this git hub page
https://github.com/ubports/ubports-installer/
but as I'm starting to get slightly out of my depth here...I'm not certain I have done that correctly. Is it correct just to copy and paste those rules as they are presented on that page?

Lakotaubp

@ziggutas Can you try on another pc laptop just to get permissions up from adb? Or if you have a spare usb stick you could create a bootable Linux mint drive and run that on your pc just to get adb permissions up. daft question just to check oem is unlocked ? but the installer would have picked that up. try resetting your device and seeing if that helps.
Before that stop adb on you pc adb kill in terminal. reconnect your device type adb devices and watch the screen on the m10 closely does the dialogue box show.

@advocatux can you shed any knowledge on this

A Former User

@lakotaubp Thanks again for all the help. I'm going to have to put it to one side for a day or two; work is getting in the way!Plenty of things to try in your last post and there is no such thing as a daft question when you're talking to me ;).I'm not sure how to check if oem unlocked; isn't that for android devices? Mine is ubuntu edition m10-15.04 (OTA-9.5), no updates possible...I think.

Will try laptop first, reset device next, Mint after.

Lakotaubp

@ziggutas Sounds good. The installer should sort out OEM unlock but it can be done from the terminal as well. Good luck let us know how uttered goes

A Former User

@lakotaubp Tried connecting device to laptop but no response from adb devices.
Presumably I should still have tablet in developer mode before connecting? Should I have installer running also? Anyway, I tried with and without installer; no joy.
Resetting the device made no difference.
Running Linux Mint 19Cinnamon on usb stick I tried to adb, nothing, and tried running ubports-installer (appimage) and connecting device; nothing.
I'm curious to know what would be the set up for trying OEM unlock from terminal?

Lakotaubp

@ziggutas first run his in the terminal to check your adb

sudo add-apt-repository ppa:phablet-team/tools && sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

Then connect your tablet and type adb devices you should see your m10 and or see a dialog box to grant permission

You may have done that already, anyway
sudo fastboot oem unlock
should do the trick

A Former User

@lakotaubp Ran the commands; already had the latest versions. Tried adb: nothing.
Sudo fastboot oem unlock got nowhere. Just 'waiting for any device'.

Plugged my phone in (bq e4.5, ub touch 15) typed adb devices and it was listed straight away with a pop up window on phone screen also. So pc side of things appears ok.

Tried once again running ubports-installer and choosing device manually but failed at the prompt to press vol and power buttons to go to bootloader. Tablet always ends up rebooting normally to the 'bq powered by ubuntu' screen.

This makes me think something may have changed in the tablet the very first time I pressed vol,power and installer appeared to be working bu then got stuck at recovery mode and would go no further...?

Lakotaubp

@ziggutas after switching off the power and vol down buttons held together don't give you fastboot ?
if you start the installer without the tablet connected wait till its running then connect the M10 its not detected? even if you choose the device yourself and install options? does it ask you to put it into fastboot/bootloader manually (power and vol down buttons together). The tablet wont go into it just trying to get things straight in my head

A Former User

@lakotaubp Sorry for the confusion, I'll try to describe the situation more clearly.
I've just looked back to my first post at the top of this thread. It describes the problem I'm having quite accurately.

Now the situation is- if I start installer, then connect tablet, it is not detected.
If I choose device myself and install options it takes me forwards to point where it asks me to put it into bootloader manually by pressing buttons...but the tablet fails at this point.

Holding power/vol up for a minute results in black screen for awhile , quick vibrate, 'bq powered by ubuntu' regular start up screen. And this cycle just continues if for as long as you hold the buttons continuously.

The black bootloader screen on the tablet only came up that one time before I asked for help. Never since.

Thank you so much for all the time you are giving this; I'm starting to feel guilty!