[Android Software Development] mrmazak:
I have also similar finding. But discovered if I flash stock recovery back and perform factory reset in that, the /nvdata issue is solved

I have only just found this new version, so was not able to test it before, while still in beta. I am restoring to full stock so I can get you recovery log.

As far as just the display ui_print while flashing is. After the patch displays "done" the next line says "updateing partition information" followed by "unable to mount /nvdata file not found"

When factory re-seting in stock recovery, the displayed actions are

formatting /cache

formatting /data

formatting /mnt/vendor/nvdata ..... suspect this is the one that repairs it :)

Looking at the log it shows

- Target image: /dev/block/mmcblk0p2

when boot.img is really

/dev/block/mmcblk0p28 and has no ramdisk, it is only the kernel.

/dev/block/mmcblk0p2 is really recovery

UPDATE:

Oh , looking at the function "find_boot_image" it seems it was intended to use recovery as the target.

F1:/ # ls -al /dev/block/by-name
total 0
drwxr-xr-x 2 root root 800 2019-06-03 07:25 .
drwxr-xr-x 5 root root 1120 2019-06-03 07:25 ..
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 boot -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 boot_para -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 cache -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 cam_vpu1 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 cam_vpu2 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 cam_vpu3 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 dtbo -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 expdb -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 flashinfo -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 frp -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 gz1 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 gz2 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 lk -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 lk2 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 md1img -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 nvcfg -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 nvdata -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 nvram -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 otp -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 para -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 proinfo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 protect1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 protect2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2019-06-03 07:25 recovery -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 scp1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 scp2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 sec1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 spmfw -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 sspm_1 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 sspm_2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 system -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 tee1 -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 tee2 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 userdata -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2019-06-03 07:25 vendor -> /dev/block/mmcblk0p33
F1:/ #