-
@UKPhil If you want to get back to the original Ubuntu touch that file is on the Bq website. If I remember correctly all the info was also on the Ubuntu Forum pages under the touch section it would be sometime back now but was still there. That thread has alsorts of info and links inti.
I guess you've tried different usb ports and cables on your pc/laptop think a usb 3 port was mentioned. I often have device not detected etc messages from my Ubuntu laptop if I us the wrong port or knock the cable. Sorry if this is blindingly obvious. Or is the micro usb damaged on the tablet as I think you had issues charging it as well. -
@UKPhil There is also the telegram group for the MDT. You could always ask a question on there for more specific info
-
Thanks guys, I tried again today and on both the M10 tablets I get the same returned 'Device not found'.
I checked all ports on my laptop and still nothing. I even used a few cables and nothing. I thought that it may be the cable but it I was not connected, I would not be able to see my folders.
This is where I stop:
Flashing legacy channel
Please press Power and Volume Up (+)
wait until your tablet is in recoveryselect 'reboot to bootloader' and confirm by pressing the power button
You should see '=> FASTBOOT mode...' in the lower right corner
Is your tablet in bootloader/fastboot mode now? [Y]
- I press y and Return and get the following:
Detecting Device
Device not found
Back to menuThis is where it all stops....
I have the tablet in Developer Mode and idle set to never.
-
@Lakota Thanks for the link, I followed the steps in ('cant get my M10 fhd to take the flash) so I downloaded the img into downloads and then executed the following in my laptops terminal:
sudo ubuntu-device-flash --server=https://system-image.ubports.com/ touch --channel=ubports-touch/legacy --bootstrap --recovery-image=/home/uklaptop/Downloads/recovery-frieza.img
The output that I get here is this:
root@uklaptop:~# sudo ubuntu-device-flash --server=https://system-image.ubports.com/ touch --channel=ubports-touch/legacy --bootstrap --recovery-image=/home/uklaptop/Downloads/recovery-frieza.img
sudo: unable to resolve host uklaptop
2017/09/19 21:52:44 Expecting the device to be in the bootloader... waiting
2017/09/19 21:52:44 Device is |frieza|
2017/09/19 21:52:44 Flashing version 12 from ubports-touch/legacy channel and server https://system-image.ubports.com/ to device frieza
28.19 KB / 321.93 MB [] 0.01 % 46.90 KB/s 1h57m7s2017/09/19 21:52:46 Waiting for device to enter recovery mode ...
2.47 MB / 104.46 MB [__] 2.36 % 42.74 KB/s 40m43sFailed to enter Recovery -
Can you please use
sudo strace -f -o /tmp/ubuntu-device-flash.tr ubuntu-device-flash
and upload the resulting file somewhere, or send it to me and I will put it on my webserver for review.
-
Sorry this is above what I can help with. I'm sure someone here will have the info. Try the Ubuntu forum touch section there is advice on this on there on flashing to ubports and back again andon github. I don't remember having any issues so lacking advice. I think there is also another thread on this forum about thus issue but again not sure where try searching m10 andsee what comes up. Will have a nose around myself later. Last bit of blindingly obvious info the image your trying to flash is the one for the m10 fhd. I'm sure it will be but you never know. Apologies if this is more hinderance than help.
-
@guru This is the output that I get:
sudo strace -f -o /tmp/ubuntu-device-flash.tr ubuntu-device-flash
sudo: unable to resolve host uklaptop
Unknown command `ubuntu-device-flash'. Please specify one command of: core, personal, query or touch -
@Lakota Thanks, I look forward to getting UBPorts on my M10's
-
@UKPhil Lokate where the command 'ubuntu-device-flash' is exactly and call it with full pathname. ANd ofc you must add all the other flags you posted.
-
This post is deleted! -
I have exactly the same result than UKphil when using the same command Line for m10 fhd migration :
Waiting for device to enter recovery mode ...
2.47 MB / 104.46 MB [__] 2.36 % 42.74 KB/s 40m43sFailed to enter Recovery
Please if someone finds a solution, send us the infos -
@H+ said in Unable to install UBPorts on bq M10:
I have exactly the same result than UKphil when using the same command Line for m10 fhd migration :
Waiting for device to enter recovery mode ...
2.47 MB / 104.46 MB [__] 2.36 % 42.74 KB/s 40m43sFailed to enter Recovery
Please if someone finds a solution, send us the infosHow long is the time frame between 'Waiting for device to enter recover mode ...' message and the 'Failed to enter...' message?
As I said two days ago, I would use the tool 'strace' to sniff-up what is exactly the problem. If the above time is long enough, let's say some 10 secs, one could fire up the tracing from another terminal session, if not one must launch the full command below strace.
-
For me, it takes around 2 min ,just the time to completely download the file , then ´failed to...´
At the same time on the screen tablet, 10s after the start it exits from fastboot to return on thefastboot ,recovery menu -
Maybe a simple sollution: Have you tried to download and flash the recovery manually and the flash with ubntu-device-flash ommiting the bootstrap and recovery from the command???
Some Pro 5 users had similar problem and were able to flash it that way. -
@H+ said in Unable to install UBPorts on bq M10:
At the same time on the screen tablet, 10s after the start it exits from fastboot to return on thefastboot ,recovery me
This si the same for me. I think it is doing something when it goes back to the fastboot screen, but nothing happens. I initially thought it may be due to the battery being low, but this still happens on a full charge.
-
@Stefano said in Unable to install UBPorts on bq M10:
Maybe a simple sollution: Have you tried to download and flash the recovery manually and the flash with ubntu-device-flash ommiting the bootstrap and recovery from the command???
Some Pro 5 users had similar problem and were able to flash it that way.This is totally new to me, can you step me through how to do this. I have had a look and I wonder if it is running this command in my laptop, that had the tablet connected to it?
-
Just looking at this site Install Ubuntu nd it is talking about enabling read/write. Is this something that we may need to do in this situation to get the image on out M10's?
In the Andriod systems you have to enable developer move and then "Enable USB Debugging" or the laptop cannot see the device. I know there is no Enable USB Debugging option in Touch, but if it is not enabled in Andriod, this would cause the issues we are having here. Strange.
-
This post is deleted! -
@Marathon2422 Looking at the links that you have supplied, does the device need to be unlocked, or is this just Andtiod?
You unlock the device by typing:
fastboot oem unlock -
@UKPhil said in Unable to install UBPorts on bq M10:
@Marathon2422 Looking at the links that you have supplied, does the device need to be unlocked, or is this just Andtiod?
You unlock the device by typing:
fastboot oem unlockUnlock makes it go to orange state.
Perhaps you could try to do this:
@jamesp said in Can't get the M10 FHD to take the flash:
Solved the problem by installing latest bq UT with bq:s own flash tool. After that i enabled developer mode and UBports installer detected M10 and this time it started installing it and got to the last point where it was supposed to flash device, but yet again was stuck with "installing Ubuntu update"
But then in bootloader i gave the old command:
sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=frieza
--channel=15.04/stable --bootstrap --recovery-image=recovery-frieza.imgAnd UBports finally installed to M10 succesfully.
Here you can download bq firmware and if you don't have Ubuntu version use code: ML000555 to download it.
http://www.mibqyyo.com/en-download/categorias/aquaris-m10-fhd-ubuntu-edition/
But all is not well! There still is this weird ~3min delay with the splash screen before UBports boots? bq ubuntu booted instantly. Is this a bug in UBports firmware or are there still some weird issues with my M10? Everything else seems to work just fine.
But i would recommend to postpone UBports installation to M10 until those super annoying bugs are fixed.
