Yes it is downloading 15GB and also some "useless stuff for other devices".
But this useless stuff is very small, maybe 50MB.

Your next step will be to find the device and kernel sources for your device and place them in the appropriate folders.
You also have to either download the vendor blobs or extract them from your phone.

It also helps to have the cyanogenmod sources for your device as reference. (another 30GB)

After these steps you can try to build Ubuntu touch for your device. There will be a lot of errors and you will have to solve them one by one

Please take a look at the Ubuntu porting guide: https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/#anchor3
Your device/huawei/angler/BoardConfig.mk will have a variable TARGET_KERNEL_SOURCE which has to point to your kernel sources.
The guide is a bit unspecific about the vendor blobs so i suggest to read the following: http://wiki.cyanogenmod.org/w/Build_for_angler#Extract_proprietary_blobs

Good luck

One problem you will run into is, that the vendor blobs that you have to extract from your phone are designed for android 6.0.0 or 6.0.1 while the source you downloaded with phablet-dev-bootstrap is based on android 4.something

I heard chances are high that this will not work together

The newest device is the meizu 5 pro. It was 'released' with ubuntu touch last week.
Sadly, you have to order it from a chinese shop.
I ordered it and am still waiting for it to arrive.

Hi Frano212,
I stopped working on the port. It does boot up into adb but graphics and so on are not working. It is very hard to get help, so i will just buy the new meizu pro 5 ....

@frantisheq That looks like a nice phone to me, never heard about it before. You might have more luck than me with this one as it is running KitKat
I got the Z1 booting into adb but that is all i achieved. Everything that relies on the vendor-blobs (like graphics, network ...) is not working. The reason for this is most likely the fact, that I only have vendor blobs for android 5.1.1 which don't match the Kitkat Android that is used in Ubuntu Touch.

I will not upload my sources as i don't know how to do that in a clean way but i would love to help you in getting your port booting to adb.

Since your phone is not supported by Cyanogenmod (that's where I got the kernel and device sources for mine) your best bet might be to use the device/kernel from the oneplus one. The SOC is the same, so booting (without graphics and so on) might work with those sources.

One problem you will have is, that you can't get the device tree sources for your device. One way to get around this is to dump your Android boot.img and extract the dt.img from there with the unpackbootimg tool.
Note: There is a difference between the 'device' folder in your build directory and the device-tree i am talking about right now. That is something that confused me in the beginning.
You can get an introduction to device trees here.

I am also a beginner at all of this but I would love to help, so let me know if you need help

Did you try to boot with the debug option removed from the cmdline?

I had the same symptom as you (systemd-udevd prints hundreds of messages per second until the phone reboots).
For some reason this only happens with the debug option set.

please compare this (with 'debug' and bootloop):
http://paste.ubuntu.com/14667442/
with this (no 'debug' and no bootloop):
http://paste.ubuntu.com/14667455/

Is it sufficient to flash only the boot.img to boot into adb?

I am asking this because i can compile the boot.img but there are still errors with the system.img and recovery.img. Now my goal is to test the boot.img alone just to see whether it boots or not.

One problem you will run into is, that the vendor blobs that you have to extract from your phone are designed for android 6.0.0 or 6.0.1 while the source you downloaded with phablet-dev-bootstrap is based on android 4.something

I heard chances are high that this will not work together

Please take a look at the Ubuntu porting guide: https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/#anchor3
Your device/huawei/angler/BoardConfig.mk will have a variable TARGET_KERNEL_SOURCE which has to point to your kernel sources.
The guide is a bit unspecific about the vendor blobs so i suggest to read the following: http://wiki.cyanogenmod.org/w/Build_for_angler#Extract_proprietary_blobs

Good luck

Since there is few feedback to your question I will write all things that i noticed in your log:

• You have 'androidboot.hardware=dior' on your cmdline. I saw 'androidboot.hardware=qcom' very often for qualcom devices.

• Your logs say your device is loading udev rules from /lib/udev/rules.d/ but ubuntu-touch-install is copying the udev file to /usr/lib/lxc-android-config inside the system.img.

• The log has this line: 'Machine: Qualcomm MSM 8226 (Flattened Device Tree), model: Qualcomm MSM 8926 H3-LTE' but your Xiami Redmi 4G seems to have an MSM8928 SoC. (three different numbers here)

Yes it is downloading 15GB and also some "useless stuff for other devices".
But this useless stuff is very small, maybe 50MB.

Your next step will be to find the device and kernel sources for your device and place them in the appropriate folders.
You also have to either download the vendor blobs or extract them from your phone.

It also helps to have the cyanogenmod sources for your device as reference. (another 30GB)

After these steps you can try to build Ubuntu touch for your device. There will be a lot of errors and you will have to solve them one by one

First guess:
Did you name your udev file '70-dior.rules' ?
(you also have to change the rootstock-touch-install file to get it copied to the device)