Related
I have rom 4.00.16 from the kitchen, and i wanted to upgrade the radio.
I had ver. 5.15 and i downloaded the radio upgrade from xda.ie (the first one that apeared in a google "xda radio upgrade" search.
Since it didn't tell me the radio version i was going to upgrade i installed it to the xda, and as soon it finished installed the xda self-soft-reseted and asked me for mim password, i have entered it and it started to do the upgrade by itself and got stuck at 10% for several minutes and frozee there.
I have already soft-reseted, hard-reseted, but without sucess my xda wont boot the OS, only displays the "not for sale" screen with the following info:
G
R
4.00.16
Click to expand...
Click to collapse
Help please!!!!
I dont have a sd card reader!!!!
Any other possible workarounds???
you can help me here or by my msn messenger: [email protected]
I'm stuck with out a mobile phone.
You have to have a card reader to fix it. There is no other way. You have to upgrade OS (using SD card method) and then try installing radio upgrade again.
I have already done that.
Now i can boot the xda (pressing the volume button) but as soon it starts making the upgrade it says it fails (at 1%)
The worst part is that the xda isn't charging (or it doesn't assume it's charging and that's why it doesn't continue with the upgrade).
I've already tried to copy the gsm soft from a working qtek 1010 using the bootloader gsm to sd method, but no sucess since nothing happens (i insert the serial cable on the xda but mtty.exe doesn't react or recognize the xda - any possibel mistake i'm making here???).
Help most wanted, since i can't afford at this time to pay for a motherboard replacement - this is my only solution according to the qtek technical support here in Portugal (and hey, thanks a lot for your time )
Anyone can please suggest any possible solution?!?!?!?
You can feel free to use my msn: [email protected] to contact me...
I will pass some licenced software to the person that can help me solving my problem!!!!
TIA
Maybe this thread can give you any help :?: :?: http://www.xda-developers.com/forum/viewtopic.php?t=2489
Why it tries to run upgrade upon boot? When I flashed my OS there were no files under start up folder to run upgrade executable. I suggest boot your XDA and remove everything from Startup folder
My main problem is that i can't get the xda to charge (or at least assume it's charging the led is always off).
Isn't there a way to crack the rsu to avoid him to check battery status an carry on with the upgrade (cracker's welcomed )??
I think that would solve my problem
I can boot the OS by pressing the volume key (already changed to several OS's to see if one coulde handle with the charging problem.)
And i can sync with my desktop.
But i cant upgrade via programme A.
Programme B installs on the xda but when it reboot's it stop's at 1%
I now have a original o2 3.17.3 and my bootloader is 5.15
I've seen that in the bootloader we have the chance to backup the gsm rom to a SD card! But how to restore it??? If anyone can make such a backup and has a way to restore it can you please share it with me???
As i said i don't have the money to exchange my motherboard (that's the answer from QTEK'S support i've got (great guys thank's again for your time)
I've arranged a conmceptronics sd/mmc/ms/sm/etc.../etc... card reader.
So if one finds a way of backing up the gsm rom, copy it to the sd and zip it using the rom tools here available could you please send it to me???
Thanx in advance
Another thing:
with this rom installed if i go to backlight settings it wont turn off the backlight.
Hi,
I need urgent help
Qtek Support here in Portugal gave me a qtek unit for a few days to see if i find a way to recover mine without replacing the motherboard.
I have the following material:
-1 working qtek 1010
-1 damaged xda
-usb cradle
-serial cable
-sd card reader
-1 128mb twinmus sd card
-charger
-etc...
What can i do to solve my problem
Please help
TIA
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
any one?...my $300.00 paper weight needs help
is there anything i can do with wallaby bootloader....i dont have anything else.................
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Yes, $300.00 paper weight !
you could get it fixed (hardwire repair)
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where Im @
(i had the I had it cradled, connected to usb & power during it all)
Yeah, that's exactly what I did. I noticed you did a hard reset, which is also what I did. That may have been the death blow.
First of all, do not do ANYTHING in the Wallaby bootloader. If you start messing around in there, you're done.
Plug your phone into the power cord (even though the battery won't charge now, the phone will stay powered if you keep it plugged in).
Try to get the RSU files for the version you initially upgraded from (6.18 for the default T-mobile, or maybe 4.21 like I had from a 4.00.05 ROM upgrade package). Load those files into the Windows directory and then try running them.
Just FYI, I did a hard reboot and changed ROMs several times. I also messed with all kinds of GSM settings in the bootloader. In the end, my phone was toast. Unrecoverable. Fortunately, I got mine from T-mobile and they did an exchange. With my new phone, I'm just gonna wait for the official RSU before I try changing it
ok...too late about the Wallaby thing, that was the 1st thing i was messin with, wen i first loadit it it said "wait" 4 a looooong time, then finally said "gsm error"....but i started playin with it, an tried every option on there, but nothing happened @ all.
2nd: i cant load any thing into windows, because the xda never boots up, just sits @ the 1st screen
so i figured im gona have to get a usb r/w and a SD card :shock:
should i use XDArit.exe or XDAtools.exe
im i gona have problems, i think i have Wallaby 5.17 :idea:
JUICEe said:
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where I'm @
(i had the I had it cradled, connected to usb & power during it all)
Click to expand...
Click to collapse
Ok you're still in good shape just try re-copying the files over and run RSUpgrade again, but what ever you do don't install the 4.21 Radio stack upgrade!
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Qman said:
JUICEe said:
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where I'm @
(i had the I had it cradled, connected to usb & power during it all)
Click to expand...
Click to collapse
Ok you're still in good shape just try re-copying the files over and run RSUpgrade again, but what ever you do don't install the 4.21 Radio stack upgrade!
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Click to expand...
Click to collapse
I figured that having it connected to usb was a bad idea, i just wasn't thinkn :roll: ...but how am i supposed to copy the files when i cant load up the XDA, and even when trying to connect to active sync, while the XDA is sittin, froze, on the boot screen- active sync doesnt recognize :|
Qman said:
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Click to expand...
Click to collapse
What ? I'm surprise!
JUICEe said:
I figured that having it connected to usb was a bad idea, i just wasn't thinking :roll: ...but how am i supposed to copy the files when i cant load up the XDA, and even when trying to connect to active sync, while the XDA is sitting, froze, on the boot screen- active sync doesn't recognize :|
Click to expand...
Click to collapse
At this point I suggest that if you have an PC card SD card reader reload
the OS and start over with the radio stack upgrade using the same upgrade method but this time upgrade to the AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH
...AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH[/quote]
IM NOT SURE BUT I THINK IT WAS 6.18
WILL THE ATT STACK WORK WELL ON MY T-MOBILE SERIVICE?
AND IM CONFUSED ABOUT HAVIN 2 HAVE TO COPY FILES TO THE SD THEN TO THE XDA...1ST, BECAUSE I NEVER USED AN SD W/R OR ANY OF THE SOFTWARE NEEDED TO USE IT, AND IF I RELOAD THE OS, CANT I JUST BOOT UP AND COPY THE STACK FILES THRU ACTIVE SYNC? OR WILL THE DEVICE STILL NOT BOOT UP ??
BTW:THANX :!:
JUICEe said:
...AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH
Click to expand...
Click to collapse
I'M NOT SURE BUT I THINK IT WAS 6.18
WILL THE ATT STACK WORK WELL ON MY T-MOBILE SERVICE?
AND I'M CONFUSED ABOUT HAVING 2 HAVE TO COPY FILES TO THE SD THEN TO THE XDA...1ST, BECAUSE I NEVER USED AN SD W/R OR ANY OF THE SOFTWARE NEEDED TO USE IT, AND IF I RELOAD THE OS, CANT I JUST BOOT UP AND COPY THE STACK FILES THRU ACTIVE SYNC? OR WILL THE DEVICE STILL NOT BOOT UP ??
BTW:THANX :!:[/quote]
Yes the AT&T radio stack will work on your T-Mobile and its the one I use and recommend.
As far as reloading your OS from the SD card its what we call the SD card boot loader method and is by far the best way to upgrade your OS. Do a search on this forum for more info.
Yes your device will boot but since your radio is blown Activesync most likely wouldn't connect.
HTH
ok, thanks again...i guess im off to buy the reader/writer, and the card, from walmart, or radio shack whichever is cheaper...( DO I NEED A 64MB CARD, OR CAN I GET A 32MB?)
I'll repost after halloween, since i gota go to sum partys an release all my xda induced stress with good old friend beer
btw, lol, my girlfrien seen my xda while i was tryin to repeadidly boot it up, & as it was froozen on the boot screen, i have "rom is cooking" bootimage, an she was all " i guess u did fry ur phone" :shock: :twisted:
....so with XDAtools OSImagetool, will i be able to copy the r stack?
is the target x:\windows\
that easy?...god i hope :?
Yes you'll need at least a 64MB SD card.
BTW Fry's had one on sale earlier this week for $22.00.
HTH
re radio stack upgrade
I've been following this thread re radio stack upgrade to TMO. I have RS6.18.00 currently and see 6.24.00 at yorch.net's web site under upgrades. Questions:
1. Do you copy the 4 upgrade files to the /windows folder on the PDA to run the upgrade?
2. My phone is working fine with ROM4.00.21 and RS6.18.00, should I upgrade my radio stack to 6.24 or wait another month or two for TMO's offical build?
Kind of nervous given the threads I've read. btw, I bought a SD card reader/writer & flashed ROM via bootloader/XDATools method. Worked well.
Craig
Re: re radio stack upgrade
cshields1 said:
I've been following this thread re radio stack upgrade to TMO. I have RS6.18.00 currently and see 6.24.00 at yorch.net's web site under upgrades. Questions:
1. Do you copy the 4 upgrade files to the /windows folder on the PDA to run the upgrade?
2. My phone is working fine with ROM4.00.21 and RS6.18.00, should I upgrade my radio stack to 6.24 or wait another month or two for TMO's official build?
Kind of nervous given the threads I've read. btw, I bought a SD card reader/writer & flashed ROM via boot loader/XDA Tools method. Worked well.
Craig
Click to expand...
Click to collapse
I suggest upgrading to the AT&T Radio Stack first it has a higher upgrade success rate IMHO or just wait on the official T-Mobile lease.
As fas as how do you copy the files over, you can use Activesync Explorer or use your PC's SD card reader to copy them to your SD card then copy them from there.
HTH
back & hungover...
so i got me a sd reader & the card.....copyed 4.00.16 to it (b4 had 4.00.05 i think) loaded it via wallaby, everything looked fine (except my battery was practically dead, i had to race to get it off the charger reset and put it back on the charger) so the os was copyed fine, and wallaby told me to cold reset (that did mean a "hard", no?)...so i hard reset it, then after a few mins i stuck the pin bak in the lil ass hole, and nothing happened :evil: so i put it bak on the charger, an the boot screen appeared, with a new image and on bottom of screen it sed 4.00.16 ..........but then it just sat there, like b4 and wut i noticed, that i didnt mention b4, is wen its booting up, 1st shows the "4.00.16" then sits there for like 2 minutes, then pops up a "G" & "R" above the "4.00.16" respctivly.....
and i left the device on charger 4 a while, and tried to hard reset again and still wont boot after 2nd pin push :?: :?: :?:
and another thing i didnt mention b4, wen loadin wallaby, it sez gsm error, or did i mention that
i had an idea, maybe to install an older os 3.xx.xx??? but it seams the problem is the gsm wont load, or isnt ther, or damaged, i dont know, how can i load a working GSM on it :shock:
Hiya Peeps!
Ive seen various posts etc about the XDA and upgrading to WM2003. But whats the best method. Is the Siemens download good and working for this device?
I cant seem to find anything on any of the O2 sites with an "offical" o2 release.
Any guideance from those that know
Thanks!!
upgrading Siemens SX-56 to WM2003
Using the Siemens-provided upgrade program hosed my XDA and I had to send it back to Siemens to have them reflash it.
I was however able to use the OSImageTool program from this Web site to upgrade just the operating system (from my own experience and from what I've read on several sites, it's the radiostack upgrade that screws up the Siemens upgrade program).
I executed Siemens' upgrade program so that it unzipped its files into a new folder, but then I stopped the program and pointed the OSImageTool to that new folder to find the upgrade files.
best of luck -
ts
P.S. whatever you do, be sure to turn off the phone part of the XDA before beginning any kind of ROM upgrade. The first time I upgraded, my phone rang just as the process began and I ended up having to use bootloader and an SD card to get things working again!
I put the WM2003 .nbf file on my SD card and started the bootloader. But being new, what do I do after the bootloader has started? It's on screen showing Wallaby Bootloader V5.22 and at the bottom of the screen is "GSM OK." Now what? :shock: :?: Did I do something wrong?
I put the WM2003 .nbf file on my SD card and started the bootloader. But being new, what do I do after the bootloader has started? It's on screen showing Wallaby Bootloader V5.22 and at the bottom of the screen is "GSM OK." Now what? :shock: :?: Did I do something wrong?
The bootloader V5.22 seems not to recognize the .nbf files on the SD cards. You have to flash your bootloader first to make it 5.15 or 5.17 then use the SD upgrading method for a new ROM.
Since updating to the T-Mobile Rom for my XDA, nearly everythiung has gone wrong.
And when I tried to downgrade it.... Nothing happens.
I used to use a modified Program A to upload it to my phone but it continues to say that the USB devide gets remotely stopped. the only thing that I can think is that my phone is cancelling the upgrade/downgrade.
I have also tried using a copy of the XDATools program to try and:
Upload another Rom.
Copy the rom to an SD card so I can use the bootloader method.
Change the Bootloader so I can use the SD card method.
None of there are working.
Help :-(
I really want to go back to the ATT rom, it might have the annoying thing with the sound but at least it doesn't mess up as much, doesn't format my SD/MMC cards and lets the alarms actually work for me.
if i'm not wrong, it seems you upgraded using the TMO exe file which updated both ROM & RSU.
check ur boot loader version, if it's 5.22 or higher, i think you need to dowgrade to 5.15 ... use the exe file that comes with the XDAtools in the binaries directory .. its name is fixbootloader.exe .. it should update ur boot loader to 5.15 by which you can use XDAtools or the SD method.
Tried that. I do have XDA tools on my machine and used that program but my CDA still has the bootleader of 5.22
And both of my machines don't like trying to update my XDA :-(
This Rom is the most annoying one I have tried mainly becaise now I can't go back to even my original one that I backed from the XDA when I got it.
Am I stuck with this ROM?
omg, i think i am having the same problem. In my case, since ive installed the new rom, i cannot sync with activesync, well very slow anyway. Activesync on my pc stops responding for a while and suddenly it says connected. However when i then run the executable created by the kitchen, it just flashes a command line window for a second.
When I try XDA-toolz with an nbf file, i get the following message:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
Click to expand...
Click to collapse
Please someone help, because i am really stuck now.
I checked, my bootloader is 5.14, so that shouldnt be the problem, perhaps i need to reinstall activesync, or perhaps lumpistefans kitchen cooks up bad roms. :?:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Biso007 said:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Click to expand...
Click to collapse
I dont understand how i can have a wrong rsu? I didnt update it , as far as i know , i just updated the pda part. I only saw programme A.
Activesync does recognise my xda, because i can synchronize and explore my device. It does however take a long time before activesync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling activesync, this didnt help.
prowling said:
ActiveSync does recognise my XDA, because i can synchronize and explore my device. It does however take a long time before ActiveSync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling ActiveSync, this didnt help.
Click to expand...
Click to collapse
If there is something wrong with the RSU it will defeinitly slow the USB performance, not neceassary by wrong RSU flashing ... otherwise, check the pins of your cradle or the 22-pin connector of the XDA ... maybe one or more pins are bent or weared.
Tried upgrading the radiop stack and although the reception is slightly better... It still won't let me upload,
and its a new cable too :-(
Oh well looks like I am stuck with it.
Another way to upgrade firmware
Are there other ways to upgrade the bootloader from SD card from within the device or even to upgrade the OS from within the phone itself?
You know... as a last alternative?
You can use SD reader/writer from the PC using XDAtools ... once the .nbf file is on the SD card, use the normal SD flashing method.
Or you can use another XDA device from a friend to copy the file to your SD card
I am having the same problem. I have TMO 4.01.16 and since I installed I can't down/upgrade my ROM through EXE or XDA tools, it says my device isn't connected, but I can still connect with Active Sync and all that jazz
ha ha
I can fix all your problems!
How?
Finally got it to work, Although it was a little bit of effort to do so.
I went back to the kitchen and downloaded a NB1 cooked rom with the "B" Signature. Then I basically ran the TMobile Setup again...
Once the setup files were on my computer I overwrote their .NB1 file with the one I just cooked.
But.... I forgot to change the file for the Radio Stack.
The machine worked except for the phone and as something is still stopping me. *it was my first reboot* It wouldn't let me use a new radio stack.
Ended up that i kept on going in to the bootloader and eventually turned my radio off altoghether before trying an update.
Now I am back to a decent rom... (Cooked and modded version of the ATT Wireless rom) and I am almost really happy.
Now to figure out how to stop the annoying sounds starting off really low.
But til then... I'm 90% happy
Thespus2002 said:
How?
Click to expand...
Click to collapse
Use the Sd Method flashing!!
Tmobile roms won't let you upgrade from the usb, here's the link and it will guide you how to flash your device from the SD good luck
http://forum.xda-developers.com/viewtopic.php?t=3274
The way I described.. I had to use the USB method.
my current bootloader (6.22) will not allow me to boot from an SD card.
And XDATools will not allow me to downgrade it... Yet
on ur PC at \xdatools\binaries run this command: pnewbootloader.exe bootloader_5_15.nb0
Wish it was that easy. The phone still appears to be locked in the rom so I can't update the Bootloader. I keep getting a message that says.
Unable to flash in to offset, cannotg disable bootloader write protect.
i can't figure out how to put the bootloader 5.17 fix on the sd card using xdarit1, do i only put the diagnostics?? or do i also put the bootloader 5.17?? if so where can i get the bootloader file?? guys please help, i really wanna have my phone back :/ and oh, while trying to put only the diagnostics xdarit1 crashes and doesn't write anything, i'm using XP sp2 and some gembird all in 1 card reader to do that..
GUYS, MY XDA IS WOOOOOOOOOOORKING!!!!!!!!!!!!!!!! Thank You for your FAQs and everything!!!!!!!!!!!!!!!
It's so easy and helpful here.... ;-)
Stefan
Where can I get this FAQ ?
bad-dog said:
Where can I get this FAQ ?
Click to expand...
Click to collapse
What are you searching for exatcly? Most of the questions are answered here in the forum. You can also take a look at the Wallaby section in Wiki.....
Stefan
Wiki ? can I've a URL ?
I tried to upgrade my Qtek 1010 from 2002 to 2003 although I can't start it now. The windows stops on the loading screen.
I tried to use a few things like XDAarit and stuff, but I did it with MMC.
I didn't get any reply to my MMC question in the forum ( Post ). So I guess that is not the problem, that guy here said he used a FAQ I wanted to know where it is, maybe it might help me out.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
Never tried flashing with a MMC. Used everytime a SD-Card....
So I'm not sure, but I'm nearly sure that's your Problem....
So try getting a (at least) 64 MB SD-Card and try it again....
Stefan
Thanks dude, problem solved.
I'm pretty sure it wasn't the MMC problem but the Xdarit and my card reader. After taking a different card reader from my fathers PC shop and taking an SD card with a new xdarit. It all worked out just fine, Although I still got one issue, I'm trying to put 2003 and still it never works, I tried all kind of versions, only 2002 works great. Can you give me any hint ?
Don´t know where the problem is. Have you tried XDATools and the OSImageTool?
Stefan
I didn't but that shouldn't be the issue, because I can install 2002 and upgrade with active sync. which pretty much the same thing, in both ways it doesn't work. only pocket pc 2002 works fine.
bad-dog said:
I didn't but that shouldn't be the issue, because I can install 2002 and upgrade with active sync. which pretty much the same thing, in both ways it doesn't work. only pocket pc 2002 works fine.
Click to expand...
Click to collapse
I remember an other guy, who had the same problem. PPC2002 ROMs went fine, but all WM2003 didn't work. But i don't remeber if, and how he solved the problem. Maybe you take a search in the forum and contact him personally....
Stefan
Sure, thanks a lot ! I hope I'll find that topic