What are the potential consequences of wiping the RPMB partition?

[CastorDYvaine]

I have a Motorola Moto E7 with an MTK Helio P22 (MT6762G) and I would like to know if there are any potential consequences of wiping the RPMB partition.

My plan is to wipe it and then restore a backup of it.
The reason for wiping is to wipe the key in it that prevents overwriting the partition.
The reason for restoring the backup is to enable decryption of a previous data backup with the file encryption keys stored in RPMB.

Below is the terminal output from when i tried to restore RPMB:

Port - Device detected :)

Preloader - CPU: MT6765/MT8768t(Helio P35/G35)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x25
Preloader - Disabling Watchdog...
Preloader - HW code: 0x766
Preloader - Target config: 0xe5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: BC2E5C468A6DA3C388CAA6AFE8B3738A
Preloader - SOC_ID: 92A648904266C0DE108F83F3429150BA3BA8E933B9C22433C2CB0F9354F3D9FB
Port - Device detected :)
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2152.bin
xflashext - Patching da1 ...
xflashext
xflashext - [LIB]: Error on patching da1 version check...
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DAXFlash - DRAM config needed for : 13014e47314a3952
DAXFlash - Sending emi data ...
DAXFlash - DRAM setup passed.
DAXFlash - Sending emi data succeeded.
DAXFlash - Uploading stage 2...
DAXFlash - Upload data was accepted. Jumping to stage 2...
DAXFlash - Successfully uploaded stage 2
DAXFlash - EMMC FWVer: 0x0
DAXFlash - EMMC ID: G1J9R8
DAXFlash - EMMC CID: 13014e47314a395238100f45c4f128f9
DAXFlash - EMMC Boot1 Size: 0x400000
DAXFlash - EMMC Boot2 Size: 0x400000
DAXFlash - EMMC GP1 Size: 0x0
DAXFlash - EMMC GP2 Size: 0x0
DAXFlash - EMMC GP3 Size: 0x0
DAXFlash - EMMC GP4 Size: 0x0
DAXFlash - EMMC RPMB Size: 0x1000000
DAXFlash - EMMC USER Size: 0xe8f800000
DAXFlash - HW-CODE : 0x766
DAXFlash - HWSUB-CODE : 0x8A00
DAXFlash - HW-VERSION : 0xCA00
DAXFlash - SW-VERSION : 0x0
DAXFlash - CHIP-EVOLUTION : 0x0
DAXFlash - DA-VERSION : 1.0
DAXFlash - Upload data was accepted. Jumping to stage 2...
DAXFlash - DA Extensions successfully added
xflashext - Generating sej rpmbkey...
sej - HACC init
sej - HACC run
sej - HACC terminate
xflashext - Setting rpmbkey: ok
xflashext - Derived rpmb key:75f789e88b01fee897aae8958aac79ba0329b1492e132a285e7f2f118fab849c
Done |--------------------------------------------------| 0.0% RPMB written (Sector 0x0 of 0x1000000) 0.00 MB/sxflashext
xflashext - [LIB]: Couldn't write rpmb at sector 0.

I have just noticed from the output that the cpu detected is different from that which is in the device however it does not affect the ability the backup/restore regular partitions.

[CastorDYvaine]

More info:

MTKClient only works with the device in brom mode.

If I restore only the userdata partition then the phone does not accept the correct password at first boot to decrypt the data.
I have tried restoring other partitions from the backup however I have not had any success.
If I restore all the regular partitions from the backup the phone does not want to boot and prompts to try again or factory reset.

I have tried writing the RPMB immediately after a factory reset in recovery however it still has the same error as in the log above.

How it all got to this was that I had used Lenovo RSA to restore the device firmware which also wiped the data using fastboot, I assume it may have also wiped the RPMB partition in the process.

If anyone has any questions or answers please let me know.

[CastorDYvaine]

Closed.
All I had to do was set the device up using the previous password then overwrite the data with the backup, after this I was able to input the password to start the phone.