Help testing new legacy image

  • Administrators


    Is there someone that want to help us test our new images?

    More info here:

    Please note that this will wipe your device and might have unexpected results since not all images are tested yet, we are working on a method that will keep your data, so if you want to keep your data, please wait until thats done

    Thank you!

  • @mariogrip I'm willing to help to test the image for the BQ Aquaris E5. But I will have to do it sometime this coming week when I have some time in case I need to reconfigure things. I will let you know.

  • Actually you can use rsync avz --delete /home/phablet <destination> to take a backup of the user folder. It should work pretty well, but no guarantees as usual. This could help to restore the previous state faster.

  • Where should bugs for the new images be reported?

  • I could help test the M10 FHD image.

    I did try running the ubuntu-device-flash command (with the M10 in recovery) but the command line just said 'waiting' and nothing happened. 😞

  • I'll test the image on Aquaris E5.

  • @NeoTheThird and where's the check list method ?

  • All good with the E5 image (^-^)b great work guys !

  • @Flohack Yes, I've used this in January when I got my phone back from reparation (well, before sending it and after getting it back to restore) and it worked pretty well. Is it true that if you have used the standard installation everything you installed is in /home/phablet? I believe so, as the above this directory everything is read-only.

  • @ronnietucker The FHD image seems to not work yet... Will post here as soon as there's news on that.

    I updated our bug tracker list:

  • @wgarcia said in Help testing new legacy image:

    you have used the standard installation everything you installed is in /home/phablet? I believe so, as the above this directory everything is read-only.

    The apps are somewhere else, and currently I did not find out a way how to backup the click packages or make a list of installed apps. But tbh I can live with having to reinstall the app itself as long as its data is here. @MariusQuabeck tells me however that /home/phablet is not everything needed for a full backup, so for sure we need a better method over time (system daemon + control GUI probably)

  • @Flohack Yes, I reinstalled the apps first, then I rsync my /home/phablet and rebooted, and the phone was as far as I can tell as it was before reflashing, apart from some configurations here and there that I had to redo.

  • @NeoTheThird - Ah. OK. Thanks for letting me know. I'll keep an eye out for a fix.

    I assume the bootloader screen is the text one with a menu and where you can move up/down with the volume keys? Just checking to make sure I'm on the right screen. 😄

  • @ronnietucker No, that's either the recovery or factory mode screen. It's a little confusing at first. I (on the M10 HD "cooler") found my way through it with trial and error... I hope to be able to write a more detailed guide soon.

  • @NeoTheThird - I was probably in the factory screen as I did see a setting for running tests on the various pieces of hardware (GPS, WiFi, etc.). Well, since the image doesn't work, I'm glad I was on the wrong screen then! 😄

  • Tested a bit of things for the BQ E5 (vegetahd) image so far:

    • Camera: OK

    • Microphone: OK

    • Display: OK

    • BT audio: OK

    • Wifi: OK

    • Apps install/Clicks: OK

    • Push notifications: OK

    • Sensors/Screen rotation: OK

    • Browser: OK

    • Gallery: OK

    • Clock/Alarms: OK

    • Weather: OK

    • ContentHub: OK

    I'm planning to run some further test from the Checkbox suite in the following days.

  • Hmm, Installation on MX4 seems a bit difficult, but that is possibly just because I can't boot any image from fastboot - and I never could.

    So here is a way to make this work (I wanted a clean install, so here is one way to do it):

    1. I had to use this tool to clean my device (albeit booting recovery failed):
      sudo snap install magic-device-tool --devmode
      magic-device-tool (choose arale, Ubuntu Touch installation and a clean install to wipe all data)
      It exits with error that it can't boot recovery, but that should be ok since it fashed some partitions before.

    2. Once cleaning is done, I flashed adb enabled recovery:

    3. After this I first had to boot into recovery and flash regular Ubuntu image for some reason as UBports image didn't work for me initially:
      ubuntu-device-flash touch --device arale --channel ubuntu-touch/stable/meizu.en

    4. Finally I booted into recovery again and executed the following command after which UBports image worked just fine:
      sudo ubuntu-device-flash --server= touch --channel=ubports-touch/legacy --device=arale
      (I had to specify the device as it didin't recognise it correctly.)

  • I'm trying to install the new images on a Bq E5. I'm able to get into fastboot mode in my phone, I connect the phone with an USB cable to my Ubuntu system (I'm running currently Ubuntu 17.04), but it seems that my Ubuntu system does not see my Ubuntu Phone. Nothing appears with "lsusb", and when I try the "ubuntu-device-flash" command, it says it is waiting for the device to be put into fastboot (which it is) and does nothing.

    Can I flash the image directly from the phone? I can upload (with ssh) the "img" file to my phone, so if I could I would do it directly there.

  • @wgarcia

    If fastboot devices doesn't detect your phone while it's booted to the bootloader, try a different USB port and USB cable. Ensure you're plugging in to a USB 2.0 port on your computer.

  • @UniSuperBox Thanks, it turned out I had changed to mtp only with the tweak toool, when I changed to USB I could mount the device and now I'm flashing the uBport image, crossing my fingers....

Log in to reply