Help testing new legacy image

[NeoTheThird]

@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: https://wiki.ubports.com/wiki/UBports-Bug-Trackers

[flohack]

@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)

[wgarcia]

@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.

[ronnietucker]

@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.

[NeoTheThird]

@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.

[ronnietucker]

@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!

[sverzegnassi]

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.

[zubozrout]

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): https://github.com/MariusQuabeck/magic-device-tool
   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: http://people.canonical.com/~alextu/tangxi/recovery/recovery.img

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=https://system-image.ubports.com/ touch --channel=ubports-touch/legacy --device=arale
   (I had to specify the device as it didin't recognise it correctly.)

[wgarcia]

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.

[UniSuperBox]

@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.

[wgarcia]

@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....

[wgarcia]

Yes!, success!, I'm in the uBports ship with my BQ E5!

[flohack]

@wgarcia Congratulations!

[GIEMME]

Has anyone tested the Aquaris E4.5? My Aquaris I use as a main phone, so I have some fear of flashing the device

[bjm]

@wgarcia What is the restoration procedure?
should you install openssh-server on the phone?

[wgarcia]

What I did is the following. You do not need to install openssh-server, you just need to enable the ssh client in the phone. Get a shell with "adb" and execute this command:

android-gadget-service enable ssh

I also use an application called "net-info" to figure out the IP of my phone in the network where it is connected through wifi, say it is 10.60.141.170.

So before wiping out my data I make a copy in my computer of /home/phablet, say in a directory called bq-phone in your home:

rsync -avz - - delete -e ssh phablet@10.60.141.170:/home/phablet /home/myuser/bq-phone

This will create a directory called "phablet" in "bq-phone" with a copy of what you have in your phone. Of course you could do this I believe in a SD-card directly in your phone, in this case without "ssh".

Now, after reflashing the phone, I followed these steps:

1. I created a passcode and enabled developer mode
2. I accessed again to a shell in my phone and enables "ssh" again
3. I copied the public gpg key from my computer to /home/phablet/.ssh/authorized_keys. For this one I had to "adb push" to the phone the file (id_rsa.pub generated in the .ssh directory of my computer), and then append it to the authorized_keys file:
   cat id_rsa.pub >> .ssh/authorized_keys (this in the phone shell)
   Then I installed first net-info to figure out the IP of the phone again, so that I can use ssh.
4. I reinstalled all the applications that I had.
5. Then I used rsync to restore all the data in the phone:
   rsync -avz - - delete -e ssh /home/myuser/bq-phone/phablet phablet@10.60.141.170:/home

I restarted the phone and voilà!, everything looks exactly the same, but I'm running now the uBports image.

[wgarcia]

Sorry, in my explanation above, the gpg-key upload and appending to authorized_keys in the phone has also to be done when you first enable ssh to backup your data.

[WLBI]

@GIEMME
I just flashed my BQ E4.5 about 5 minutes ago and it works fine.
But be aware, all your data and contacts will be deleted, it's like a brand new phone from the factory.

I just downloaded the image, where the link to that image is on this site:
https://wiki.ubports.com/wiki/How-to-flash-existing-ubuntu-touch-devices-with-Ubports-images

I set the phone to developer mode and connect it via USB to my computer.

Then I enter in the Terminal:
adb reboot-bootloader
This takes some time, until the phone was in fastboot mode.
On the phone was ablack screen, where at the bottom is a very tinny like written "fastboot"
Then:
cd Downloads # where I stored the downloaded image
sudo ubuntu-device-flash --server=https://system-image.ubports.com/ touch --channel=ubports-touch/legacy --bootstrap --recovery-image=./recovery-krillin.img

After 3 minutes I can see in the terminal:
2017/05/15 16:53:16 Rebooting into recovery to flash

Then the phone reboots, which took some other minutes.
After it was initialized, you can see the phone booting and the ubports logo.
Phone is up and running..

[GIEMME]

@WLBI Thank You!

[sk]

I tested a little bit the mx4.

• WiFi: OK
• Camera: OK
• Flashlight: OK
• BT connection to Ubuntu Desktop: OK
• lockscreen notifications: OK
• phone crashes when App is allowed to use a device for the first time:
  • utorch: Phone crash when allowing access to camera service for the first time (worked after boot)
  • unav: phone crash when allowing access to navigation data for the first time (worked after boot)

Not tested: Phonecalls/SMS as the phone does not recognize SIM anymore (hardware defect)