I guess using system-image-cli from the device instead of ubuntu-device-flash from a linux machine which has the decive attached through a usb cable makes it that the recovery image is not touched (altered) but I am not sure (I still try to understand the differences between system-image-cli and ubuntu-device-flash in what they do) - this is just a comment regarding what you said about the recovery image.
Thank you for your reply!
Through ssh I did
sudo system-image-cli -vvvv --switch ubuntu- touch/staging/ ubuntu
to install the latest staging image. I got the same result: stuck at unity-system- compositor- spinner.
But I got to ssh into it and run "cat /var/log/syslog" and I attached the result.
Then I switched back to rc-proposed with:
sudo system-image-cli -vvvv --switch ubuntu- touch/rc- proposed/ meizu.en
I guess using system-image-cli from the device instead of ubuntu-device-flash from a linux machine which has the decive attached through a usb cable makes it that the recovery image is not touched (altered) but I am not sure (I still try to understand the differences between system-image-cli and ubuntu-device-flash in what they do) - this is just a comment regarding what you said about the recovery image.
Thank you for any help on this!
mihael