[Xiaomi Mi Max 3 ROMs, Kernels, Recoveries, & Other] Uschinator:
I installed the 3.2.3-3 Version and everything worked.

But 5 Minutes after installation i got an update of MIUI:

miui-blockota-nitrogen_global-V10.0.1.0.OEDMIFH-V10.2.1.0.OEDMIFK-501936a04b-8.1.zip

It downloaded and went into TWRP and then i got an error:

============= prop ===============
ro.build.fingerprint=Xiaomi/omni_nitrogen/nitrogen:9/PQ1A.181205.006/nijel8@XDA12282118:eng/test-keys
ro.build.version.release=9
ro.build.version.incremental=eng.nijel8.20181228.211826
ro.build.product=nitrogen
ro.product.device=nitrogen
ro.product.mod_device=nitrogen_global
ro.miui.ui.version.name=unknown

mmapped 14 ranges
Failed to find file name: file_contexts
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsSource: Xiaomi/nitrogen/nitrogen:8.1.0/OPM1.171019.019/V10.0.1.0.OEDMIFH:user/release-keys
Target: Xiaomi/nitrogen/nitrogen:8.1.0/OPM1.171019.019/V10.2.1.0.OEDMIFK:user/release-keys
Source: Xiaomi/nitrogen/nitrogen:8.1.0/OPM1.171019.019/V10.0.1.0.OEDMIFH:user/release-keysTarget: Xiaomi/nitrogen/nitrogen:8.1.0/OPM1.171019.019/V10.2.1.0.OEDMIFK:user/release-keysVerifying current system...
Verifying current system...script aborted: E3001: Package expects build fingerprint of Xiaomi/nitrogen/nitrogen:8.1.0/OPM1.171019.019/V10.0.1.0.OEDMIFH:user/release-keys or Xiaomi/nitrogen/nitrogen:8.1.0/OPM1.171019.019/V10.2.1.0.OEDMIFK:user/release-keys; this device has Xiaomi/omni_nitrogen/nitrogen:9/PQ1A.181205.006/nijel8@XDA12282118:eng/test-keys.
E3001: Package expects build fingerprint of Xiaomi/nitrogen/nitrogen:8.1.0/OPM1.171019.019/V10.0.1.0.OEDMIFH:user/release-keys or Xiaomi/nitrogen/nitrogen:8.1.0/OPM1.171019.019/V10.2.1.0.OEDMIFK:user/release-keys; this device has Xiaomi/omni_nitrogen/nitrogen:9/PQ1A.181205.006/nijel8@XDA12282118:eng/test-keys.error: 3001
device name: /dev/block/bootdevice/by-name/system
Filesystem volume name: system
Last mounted on: /system
Filesystem UUID: 80d7658e-bc83-5223-b05c-e3df8761ba5a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem flags: signed_directory_hash
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extents sparse_super large_file huge_file gdt_csum dir_nlink extra_isize
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem os type: Linux
Inode count: 193920
Block count: 774155
Reserved block count: 7741
Free blocks: 104704
Free inodes: 189325
First block: 0
Block size: 4096
Reserved GDT blocks: 189
Blocks per group: 32768
Inodes per group: 8080
Inode blocks per group: 505
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: Sat Dec 29 19:23:38 2018
Last write time: Sat Dec 29 19:23:38 2018
Mount count: 50
Maximum mount count: 65535
Last checked: Wed Dec 31 17:00:00 2008
Check interval: 0 (<none>)
Lifetime writes: 94 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 86f5a40f-c0ba-58c9-a26c-9e2aa89a2691
Journal backup: inode blocks
Updater process ended with ERROR: 7
An assert failed. Please check the output above for more details.
I:Install took 0 second(s).
Error installing zip file '@/cache/recovery/block.map'
Done processing script file

Can anyone point me in the right direction? I know that i have to modify the update-script inside the zip file but i don't know which lines i have to remove...

---------- Post added at 07:44 AM ---------- Previous post was at 06:58 AM ----------

Ok, i fixed it by myself :)

Downloaded the full Update with 1.7GB instead of the OTA with 571MB and then the installationen went through.

Only thing i had to do afterwards was to reinstall magisk to get root back...TWRP survived liked promised :)