[Nokia 8 ROMs, Kernels, Recoveries, & Other Develop] datorprofessor:
:) Thank you for your tool version 0.6 and the fix you have done!

I succeeded to downgrade to oreo 8.0 just for fun and will upgrade again.

Also I have medium-bricked once and suddenly the Qualcomm qhs-usb mode appeared in windows devicemanager.exe and :good: thanks to your tool I could restore to an image with help of the binary qsahara, and my .mlf rom and programmer_ufs_firehose_8998_ddr.elf included in rom here June 2018 NB1-488B-0-00WW-B04

This is my flashing log

OffTopic:

This is another subject! But in next step, directly after this subject and the needings for the understanding, what will happen with all critical partitions, and most, will the Qualcomm EDL 9008 mode, if it is saved-data on the UFS-storage or if it is a separate chip on the motherboard. Because my another working, is not getting in Qualcomm 9008 mode

While I was happy with the repair, because I had several other Qualcomm 9008 software without luck.

-I was curious and, after my succeeded operation thanks to your tool,

-I flashed official TWRP version twrp-3.2.3-1-NB1 and inside twrp I hardbricked my phone by

flashing a rom-payload-for-sideload, and (I remember now, that data-partition wasn't decryptet, inside twrp-recovery the signs/letters in filemanager showed upp very weird) This thread verify differences and maybe the reason of the hardbrick

- this payload was extracted with another tool/python-script and

-something was wrong with the system.img when I tried to fastboot it :D not sure

-And that payload was before unzipped from i sideload-zip-file January 2019 Pie. From here or from another deep link, the same ->

Then payload-dumping with help of this tool and this and not this tool

Warning: directlink 1,5 GB.zip

And my phone is a solid rock stone, hardbricked. No Qualcomm, not even with EDL cable. I am afraid I have overwritten critical partitions, or if I have downgraded up and down with an incompatible bootloader, because with this EmergencyDownload bootloaders get overwritten if not modding the firmware before flash and shirinkin away unwanted partitions (It could also break if you handpick different img-partitions as I did too,.

One theory is that the bootloader from May 2018 was different unlock-key, and since I downgraded the Nokia 8 ta-1012 very hard, maybe the bootloader cannot initiate with wrong unlock-key. I need to start a new thread for this subject and research how to give life to the Nokia 8!

1- My first question is, which partition is critical to initiate qualcomm EDL-mode if i.e. system/boot/recovery is not found?

2- Can I fastboot erase specific-partition to trigger EDL Qualcomm-mode by auto as it happened once when I flash-bricked before? I mean erase specific-critical bootloader or something else like hyp-partition?, abl-partition?, xbl-partition?, nvdef-partion?

I am prepared to remove the display and connect USB from PC at these "service points" copper test backdoor on the motherboard, as a last resort. Need new thread for this.

Small update, I succeeded to get into EDL 9008, simply by removing (it will cost me new display), and also by removing the ribbon-cable/hdmi cable. And alsoby shortcut power-cable, by lifting and pulling back the power-connector that is placed besides display-connector.