Develop Bugs

Unable to boot up after upgrade ROM to WM6

I follow instruction in http://forum.xda-developers.com/showthread.php?t=313486 but after hardreset.
My p800w is stuck in T-Mobile logo and version number. It can't continue booting up to windows mobile.
Question: How to flash ROM without ActiveSync?
How to recovery my Artemis?
Welcome any advice,
Thanks in advance.

Yea me to, mine is now a brick after that upgrade? No active sync connection possible and all I get now is the blue O2 start screen after the hard reset with the red writing and numbers in the top left hand corner..
Phone is an UK XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 02.67.90
OS 3.4.0.0
HELP!!!!!!!

yeah, I had the same problem and have created a thread for it already. unfortunately I got no useful replies, and it seems that I am stuck waiting for an official o2 ROM so that I can recover my Orbit.

It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???

motomob said:
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
Click to expand...
Click to collapse
I read in here that you hold the voice button and soft reset.

Decaf said:
I read in here that you hold the voice button and soft reset.
Click to expand...
Click to collapse
Correct and use mtty
Already see in the forum ....

Thanks guys and apologies for the spelling..I ran the Artemis_USPL before I tried upgrading to WM6 and again have been able to run it after with my new brick now with the phone in bootloader mode but still when I try and run the german ROM update a) it will only work with the german file which freezes @ 3%? This seems to be a known problem reading around and b )when I replace it with the smaller ROM file, 54MB the german one is 66MB, I originally tried to use it doesn't read the ROM file or the update utility doesn't want to read it. I reckon I might be able to get it back if I can get one of the ROM update utilities to read a good ROm file and send it to the phone.
I can;t find this MTTY program to sniff the USB port and return the code of if the USPL util wokred as I think that could be key to all of this.
Can anyone post a quick how to here for
1) install MTTY from somewhere
2) what command to run agaist the phoen to see if the USPL util worked and what values I should be looking for
3) another WM6 ROM version (that the update utils can read) download location I can download from to try and send to the phone using the German update util
Not asking for much am I but I desperately need my phone back WM5 or 6 in the next day or so so really can't send it off.
Thanks

Error message I recive at the 3% stage when using the German ROM and english update util.

use the file attach and read that :
http://forum.xda-developers.com/showthread.php?t=285112

Thanks but I'm not that cleud up on what commands I'm meant to be sending. It works in Bootloader mode I ge a response from the phone by send it a command. But even if I get a response telling me what the CID status is its not much help as I think ti shoudl have tekane BEBEs ROM by now as I've got the german ROMUpdateUtility sending that 54,272KB file to the phone but it stops after 3%. What are my options?

motomob said:
But even if I get a response telling me what the CID status is its not much help as I think
Click to expand...
Click to collapse
That's right. On older models MTTY was quite useful, but not on the Artemis. You cannot use it to read the CID status anyway. If you are not sure about the status, run the USPL tool, just to make sure.

I've already re run the USPL ROMUpdateUtility and it completes 100% okay in bootloader mode. But after I hard reset and then try and flash the WM6 BEBE ROM or any ROM German etc back onto it it either fails with the error code I posted up earlier or gets to 3% and fails.
What are my options at this stage? Does anyone have a link to another ROM I can try like the original WM5 O2 ROM or any other WM6 ROm that might work. I'm willing to give them all a try as it's just a useless phone right now and I haven;t sent it off as 1) I need it before the weekend and 2) As I can flash some ROMs with the USPL and others have done this no problem I really feel there must be a solution as I can still falsh the phone.

What can I say RTFM... I did it all right and I didn't have a brick, I missed out one small detail... loading on the ROM with the extended ROM. All now running and it does seem a little faster than WM5.
Thank you to all those that tried to help out. To the others that are still having probs.. Don't try and run the update in the middle of a busy day in the office whilst trying to manage 100 other things meaning you are probably missing out a line like me...
One question though how do I get back my O2 power and storage meters on the today screen back as I liked them and the WiFi seems to have a bug where when it is enabled and you click on the WiFi symbol up the top it only allows you to switch it on, when it is already on.. so you have to open up the COMM manager to switch it off.

So how did you fix it exactly? I have read this thread thoroughly and can't find out what you did!

ERROR[206] occurs while trying to update ROM to WM6
While tring to update ROM to WM6 on O2 XDA Orbit i encounter ERROR[206].
I wanted to attach the screen shot but dont know how to do that, but anyway what i am doing is i attached my pda to my pc via activesync using supplied usb cord. Everything goes well till i reach a screen where it says "You are now ready to update your ROM image...." and once i click next a progress bar apperas and my pda shuts and activesync exit's automatically and my pda tries to restart with RBG band and some text:RUU, IPL 1.25.0001, SPL 1.25.0000 and USB. And thats it after few seconds or a min i get the ERROR[206] and my pda hangs.
I dont know why Activesysn shutsdown ???
Just an additional in i want to tell that without installing activesync i am not able to connect/pair my pda with my pc. So do i need to install the drivers and then try or it doen't matter cause once i install Active sync i can connect the device.
Please help me with this....
Thanks

unable to load bootloader!!!!!!!!!!!!
HELP!!!!!!!!
I have HTC3300, tried to update rom, now its bricked. I tried to start bootloader by pressing the voicebutton and softreset but loads in t-mobile screen and hangs, im unable to start the bootloader.
Is this end of story or are there any other options to get the bootloader to start????
please help

Bootloader
I had a problem with my phone loaded touch flow 4 and cid unlocking, everything was fine then after a while it froze at boot up.
I look put the battery and did a hard reset, put it into bootloadeder mode, reflashed with a t-mobile rom does not need to be cid unlocked to do that.
Once origonal rom was working, cid unlock again, flashed back to touchflow 4.0 - sorted

Where did you got an tmobile rom from can you tell me. Mine is also freezing on booting almost once every day or so after I've upgraded to 4.0

Bootloader problem

I had SPL 1.30 and attemted to update to hard spl v7/spl 2.10
it didnt go through for some reason and it told of errors-from the start it said i should use sspl as it could not autodetect
the bootloader screen reads: Herm100
IPL-SSPL by Des
Herm100
SPL 1.09.ds
USB
when i try to update the rom it cannot autodetect, and tells me to use sspl, which doesnt work-it says check connection etc. and stays on the bootloader screen until i soft-reset
now i cannot update my rom's because of bootloader problems
-the device starts up and seems to work fine though-official htc europe wm6 rom 3.54
-activesync works properly
any ideas on what i should do?
i looked around on other peoples problems like this, but they seem to be stuck on the bootloader screen , but (fortunately?) i am not
thanks
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
i tried to solve by installing the o2uk official rom 3.54-it is a full upgrade not OS-only, this worked but i still cannot install normal rom's
when i try i cannot autodetect, and when i choose 2.02/2.10 new bootloader + Hard-spl it starts, gets to 1% and stops and resets phone saying there was an image problem
it now says spl 2.03
????
if i try installing the rom using sspl it goes back to the same problem as before (above) and the same bootloader screen appears (as above)
??????????

someone help please....any info at all would be appreciated

ditto..........

Have you read Mr Vanx's guide to putting on the HardSPL and ROMs? It sounds like you have but it tells you what options to use when you're doing it (link in my sig)
Also, I strongly advise you to stop trying anything other than the official ROM until you get HardSPL on - you risk bricking it otherwise (I realise you probably know this but for anyone else, this can't be overstated).
Cheers,
Smiffy.

I try installing hardsplv7 olipro;
the only option i can choose is 'force using sspl' and when i choose and continue it gets stuck on the 'verifying information on your hermes' grey box, and then it says connection error [260]-failed, make sure you are connected etc.
i am connected properly via activesync (usb)

Are you using vista?
Did you untick "enhanced networking" under connections/usb

I had also problems with my Vista version. MrVanxX has the working solution. Check that if you do have Vista!

aameerp said:
I try installing hardsplv7 olipro;
the only option i can choose is 'force using sspl' and when i choose and continue it gets stuck on the 'verifying information on your hermes' grey box, and then it says connection error [260]-failed, make sure you are connected etc.
i am connected properly via activesync (usb)
Click to expand...
Click to collapse
Put the phone in bootloader and try it. Hold down the OK and Power button then press the reset button on the bottom, release the reset wait a moment and then release the OK and power button. Then try to proceed with the upgrade.

it does go into bootloader mode, and the screen appears and stays until i soft-reset
(i have unchecked enhanced enhanced networking in usb connections, but same result)
thanks for your efforts though
when i manually enter bootloader it reads:
Herm100
IPL-1.04
Herm100
SPL-2.03
When it enters bootloader through the ruu process it reads:
IPL-SSPL by Des
Herm100
SPL 1.09.ds
both times it only lets me choose hard-sspl in the hard-spl program and ends up with the connection errors documented above....

Are you using XP or Vista? If on XP have you setup a connection through active sync and not just a guest account?

i am using vista
but i've never had problems sending/recieving data, synchronisisng, flashing rom's etc. in the past

aameerp said:
i am using vista
but i've never had problems sending/recieving data, synchronisisng, flashing rom's etc. in the past
Click to expand...
Click to collapse
You've followed MRVANX's guide to the vista fix for WMDC?

success....thanks a million everyone

aameerp said:
success....thanks a million everyone
Click to expand...
Click to collapse
You're Welcome!

Problem with WMDC 6.1

Last night I decided to upgrade to 6.1 then flash Dutty's Rom. But whenever the device goes into bootloader mode WMDC gets disconnected and the flash can't continue.
I simply do a Soft Rest and everything is back to normal. I can Sync without any problems. Any ideas?

allan1 said:
Last night I decided to upgrade to 6.1 then flash Dutty's Rom. But whenever the device goes into bootloader mode WMDC gets disconnected and the flash can't continue.
I simply do a Soft Rest and everything is back to normal. I can Sync without any problems. Any ideas?
Click to expand...
Click to collapse
This is normal, if your device goes to boot loader, WMDC and ActiveSync disconnect and the system uses other USB driver to allow the flash to go. Take a look at device manager and see if there are one called HTC USB.... or samethink like that.
Can you post more datails about SPL, ROM version, etc...

I flashed Dutty's Rom a few days ago and have been having a few problems so I wanted to flash another. The IPL 1.04 and SPL 2.10 are fine. One thing I did notice was everytime I begin the device asks me if I trust this program. I haven't sen this before so it must be something on the Rom.

allan1 said:
I flashed Dutty's Rom a few days ago and have been having a few problems so I wanted to flash another. The IPL 1.04 and SPL 2.10 are fine. One thing I did notice was everytime I begin the device asks me if I trust this program. I haven't sen this before so it must be something on the Rom.
Click to expand...
Click to collapse
This can be caused by the SSPL choice in the CustomRUU. Try to choose only 2.10 and HardSPL, the SSPL option don't work right all the times in my Vista...

ok I flashed Schaps Rom and all going well. Like I said, it must be something with Dutty's Rom. Thanks for the help.

[Q] Need help!

Installed a rom on my tilt 2, or thought i did. phone now boots to windows and freezes. I can boot into bootloader screen and attempt to install other roms however it never gets past 0%.
When it tell me on the computer what image i have nothing appears for the phone image. its just blank. after a while the pda program with say there is a connection error and will rail installing the rom.
plz help =(

Genesis01 said:
Installed a rom on my tilt 2, or thought i did. phone now boots to windows and freezes. I can boot into bootloader screen and attempt to install other roms however it never gets past 0%.
When it tell me on the computer what image i have nothing appears for the phone image. its just blank. after a while the pda program with say there is a connection error and will rail installing the rom.
plz help =(
Click to expand...
Click to collapse
Did You HardSpl Your Phone First?

yes, however at first i thought my phone was cmda.....now i figured it is gsm. went through the process of hard-spl how can i be sure though?

Genesis01 said:
yes, however at first i thought my phone was cmda.....now i figured it is gsm. went through the process of hard-spl how can i be sure though?
Click to expand...
Click to collapse
Since You Can Boot Into Bootloader You Can Check Your SPL Version From There Check It Out & See What Is & Post What It Is Here.

just checked it again and the olinex isnt there anymore. sure that would be the problem. how do i go about fixing said problem?
spl-0.87.0000

Genesis01 said:
just checked it again and the olinex isnt there anymore. sure that would be the problem. how do i go about fixing said problem?
spl-0.87.0000
Click to expand...
Click to collapse
Follow The Instructions In This Thread ---> http://forum.xda-developers.com/showthread.php?t=550131

tried, the phone, even thought it is connected wont sync so the spl wont detect it and run the program

when i go to manual it will start but will hang at 0% until the comp says there was an error in connection =(

Genesis01 said:
tried, the phone, even thought it is connected wont sync so the spl wont detect it and run the program
Click to expand...
Click to collapse
Try Booting Phone Into Bootloader Screen Then Plug In Usb Cable Make Sure It Says Usb At The Bottom Of The Phone Screen Then Try To HardSpl Again.

Try Installing This Cab On Your Phone --> http://hpcmonex.net/roms/enablerapinew.cab Then Run HardSpl Again.

kk thank you, i will try. will post results as soon as i get them. Thanks again. kudos to you!

If your phone does not have the HardSPL on it, and it will not boot properly, you need to get it back into bootloader mode, wait for 'USB' to appear on the screen, and flash the stock ROM, then try again with the HardSPL program.
EDIT: To see what version of Rhodium you have, remove your battery and look at the sticker under there on the phone. you should see something like RHOD100, RHOD200, RHOD300, RHOD400, or RHOD500. RHOD100-300 is GSM. RHOD400 & 500 is CDMA. Make sure you flash the correct ROMs, radios, and HSPL for your device or you run the risk of bricking it.

[Q] How to revive a BlueAngel?

Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.

JiGSaW_HTC said:
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
Click to expand...
Click to collapse
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...

d-two said:
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
Click to expand...
Click to collapse
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL

JiGSaW_HTC said:
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
Click to expand...
Click to collapse
Please look here for install the right driver for windows 7 64x

d-two said:
Please look here for install the right driver for windows 7 64x
Click to expand...
Click to collapse
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?

JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
You have not read the tutorial right... you must install the driver manual!!!!

JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.

B-44 said:
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
Click to expand...
Click to collapse
If I press power and reset simultaneously, the screen goes dead for a second, then bootloader comes up again.
Tried disabling USB connection in WMDC (No activesync for Win 7), it changed nothing.
The nk.nbf is EXACTLY 32.769KB, so I don't know why it won't see it. With some versions it sees it but gives me an error 150 (RUU not designed for this device).
If by unzipped you mean extracted, yes, all the files (EnterBL.EXE, nk.nbf, MaUpgradeUt_noID.exe, etc.) are extracted to a folder, it looks the same as in D-Two's tutorial.
Unfortunately I don't have an XP PC. Will using a Vista laptop do any better, or should I use some kind of emulator of XP and update from there? If so, can you link me to one of those?

Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.

B-44 said:
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
Click to expand...
Click to collapse
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english

d-two said:
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
Click to expand...
Click to collapse
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.

JiGSaW_HTC said:
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
Click to expand...
Click to collapse
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:

d-two said:
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
Click to expand...
Click to collapse
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.

JiGSaW_HTC said:
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
Click to expand...
Click to collapse
have you use my updater?

d-two said:
have you use my updater?
Click to expand...
Click to collapse
Ignore my previous message. I just needed to reboot the computer. It updates now!! Thank you VERY VERY MUCH!! Finally I can use my PDA again Pressing Thanks button