Can I revive this one ? (T-Mobile MDA Plus NL)

[Tutti-frutti]

Hello all,

I have an T-Mobile MDA (Dutch) that hangs in the bootloader screen after doing a wrong flashprocedure.
I tried to exit the boot loader screen with mmty and UNI_ExitBootloader, but that didn't work, so something is seriously wrong with the current rom data.

I tried to read (and understand) every similar topic on this forum to get a solution. They all point to procedures where I need to copy and run the (h)spl's, but that's impossible because I cannot boot the device.

I also tried to flash a shipped T-Mobile (NL) rom into the device. Unfortunately, the flash procedure hangs at 0% for a while and shows an error message ("connection error")

Is there a way to get this thing alive again?

More info:
Bootloader screen says:

NIKI200
SPL-1.16.0000
CPLD-4

T-Mobile MDA Plus (256MB rom) Dutch version

 

[Tutti-frutti]

Some more information...
I have now tried to flash RUU_Nike_HTC_NLD_2.09.404.1_Radio_NikeMR_1.65.28.25_signed_Ship now, and this one is NOT stuck at 0%, but displays the invalid vendor id error after 1%.
I think I need this "type" of rom update, but now for T-Mobile (Dutch), so I won't get a vendor id error. I currently have a CustomRUU with the Dutch T-mobile rom (which is stuck at 0% and reports an 'connection' error message)
I also tried to flash from sd card, but it doesnt start. Do I need to rename the nbh file, because the bootloader (before the rgb screen) says "no image file" ?

 

[Tutti-frutti]

I don't know what did the trick. But I have run mtty and entered the commands "set 16 0" and "set 14 0".
Then I tried to flash the Dutch t-mobile rom again, leading to the same error and a flash screen stuck at 0%.
I rebooted my device then .. and there it was.. a T-Mobile boot screen and a device that boots without any problem

 

[3lsheikh]

Thx Tutti-frutti you are king