Synchronous Exception at 0x0000000000000000 while flashing prm_ptable.img


I replaced my UFS with a 128GB one, then I try to install debian on this new UFS, but I got this Synchronous Exception at 0x0000000000000000 after flashing prm_ptable.img.
My operation steps are as below:

Step 1:
./hikey_idt -c config -p /dev/ttyUSB0

For this step no any problem, it just downloads three images into Dram:
Config name: config
Port name: /dev/ttyUSB0
0: Image: sec_usb_xloader.img Downalod Address: 0x20000
1: Image: sec_uce_boot.img Downalod Address: 0x6a908000
2: Image: l-loader.bin Downalod Address: 0x1ac00000
Serial port open successfully!
Start downloading sec_usb_xloader.img@0x20000…
file total size 99648
downlaod address 0x20000
Finish downloading
Start downloading sec_uce_boot.img@0x6a908000…
file total size 23680
downlaod address 0x6a908000
Finish downloading
Start downloading l-loader.bin@0x1ac00000…
file total size 1081344
downlaod address 0x1ac00000
Finish downloading

Meanwhile, on my console, i got the fastboot shell.

Step 2: fastboot flash ptable prm_ptable.img
According to the Debian tutorial, I start to flash the partition table, but i got this error:

**downloading 24576 bytes **
** 24576 / 24576 bytes downloaded (100%) **
**Flashing partition ptable **
Synchronous Exception at 0x0000000000000000

who can tell me what is wrong? and how to fix this issue?

I suppose that maybe there is something wrong in previous downloaded three images. but i don’t know how to fix this.


please tell me where I can get these three files source code???
let me fix myself.


@jackyard For board recovery, I generally use this guide [1]. Here you can find the steps to generate l-loader.bin and partition table from source. I doubt the issue you are facing could be due to “sec_usb_xloader.img” or “sec_uce_boot.img” binaries. So I would firstly suggest you to try this guide [1].



I’m afraid HiSilicon do not release the source code for these binaries.


What’s the vendor for the new UFS chip?

The issue looks very much like Marginality with UFS chip change?


What’s the vendor for the new UFS chip?

Hikey960 has had to update UFS chip twice… but I think it was the
Hynix part that motivated code changes.