ROM update mishap

[schup]

Hello,

in my infinite stupidy I updated my rom on my G4 QTEK 9100 with faria's WM6 rom without the use of shelltool (found the 5-step guide afterwards :S).
Anyhow, it went wrong and I ended up installing the original ROM again from QTEK (WI_DT_NLD_2180706_106_020710_Ship.exe).
Installing the original rom went well and my device is running again with no problems using the QTEK ROM, so I thought I'd give it another shot using the guide this time around. Only problem is, the shelltool displays my rom as this:

blversion: crossbow
device: wizard
language: wwe
brand: HTC
CID: n/a
ROM: n/a

instead of the correct information from the QTEK ROM I installed, which is a WM5 ROM in Dutch (and which works properly) :S.

My guess is that some part of the faulty installed ROM is lingering somewhere in my device :). Does it really matter and can I install the faria rom again using the shell tool (following the steps in the guide offcourse). Or do I have to fix my device properly first (in some way) before I can give it another go?

Any advice is appreciated.


***edit: feel free to move this thread if I misplaced it, didn't really know if I had to post in the upgrade, WM6 or this forum. ***

[dr_tracker]

I am not an expert, but will try to help you a bit. Reading around a guide by Mfrazz, he advises to install the original ROM before using a custom one, this because it might be possible to be some leftovers lurking around, just like you said.

I would do a hard reset then install the original ROM again, test it and if necessary repeat the process until everything is working like it should. Then after that try again the custom ROM you want to install.

This is just my opinion, maybe some of the guys that REALLY know this stuff can come up with something that works better.

[schup]

I had the original ROM installed before I tried the one from Faria. Afterwards my device didn't boot properly anymore, so I already did a hard-reset before installing the original from QTEK again. So I don't really know where shelltools gets the faulty information from. So your advise doesn't really help, but thx for the help anyways.