Renate

Only one way: Buy an unprogrammed SoC and have someone replace the one on your device. https://www.censtry.com/product/qualcomm/msm8905.html

I would guess that your PBL is not actually as big as indicated in `qualcomm_config.py` Just fudge that 0x1ffb0 to 0x18000 in that file.

I've no idea what you're asking, but NAND is a bit different from eMMC or UFS.

https://xdaforums.com/t/phone-doesnt-boot-even-in-edl-mode.4411915/post-88921909

We have no idea what happened. We need a log or something.

Add `--debugmode` to the command. It will write a log into a subdirectory "logs" that you will probably have to create first. When things are wacky you shouldn't be writing....

There are **so many** things wrong here. First, as I said, when you don't know what's going on, you should be trying **reads** not **writes**. "Yeah, but I don't need...

Please post this gpt_main0.bin Are you using the stock Qualcomm Window driver or the WinUsb driver installed using Zadig? No, this won't make a difference in how this works but...

> ... the tool started the provisioning but it stopped OMG, you **provisioned** your device? Smacks forehead. When you're neck-deep in mud you should definitely stop digging. Why don't you...

You realized that it was the **wrong** LUN? This is how people get in trouble. And as I said enough times already, don't even **try** to write until you know...