Develop Bugs

When installing WM6, ActiveSync auto disconects. What to do?

Hello everyone.
I have just bought my Hermes (AT&T 8525) after one year of planing so. It came with WM5. I downloaded some of the ROMSs, radio and bootloaders commented here. I tried reading all the vast infromation in this forum and the wiki, but still having a problem.
THE PROBLEM IS AS FOLLOW:
When I start the flashing process, using HTC_TyTN_WWE_3[1].54.255.3_6275_1.48.00.10_108.exe or RUU_Hermes_CINGULAR_WWE_3.1.57.502.1_6275_1.48.00.00_108
... everything goes well, until the progress bar appears in my PC. When it appears, ActiveSync in my PC closes and my Hermes goes to stand by (the lcd goes off) so I cannot complete the installation process.
The phone works pretty well and I'm really amazed for all its capabilities. But still, I'm stucked with wm5.
Why do you think this happened?
PS: I flashed the radio (1.51.00.10) and bootloader (HARD SPL v7). My ROM version is 2.15.502.3. I use "ActiveStink" to sync my files without problems.
Any advice will be more than welcome!!

I'm no expert but that appears to be normal behaviour!
ActiveSync is only used at the start of the process. After a few files have been transfered, Activesync is closed and a different link is established. If you just leave it for a short while longer, a progress bar should appear on the Hermes too.

Yes, ActiveSync will disconnect. The RUU takes over the connection. Have you let it sit - sometimes it takes a minute for the progress bar to move.
Have you consulted www.mrvanx.org for help on the flashing?

todd_jg said:
Yes, ActiveSync will disconnect. The RUU takes over the connection. Have you let it sit - sometimes it takes a minute for the progress bar to move.
Have you consulted www.mrvanx.org for help on the flashing?
Click to expand...
Click to collapse
I'm having the same problem - always have. The message tells me that I'm disconnected and that I should check my USB connect etc. I left that box up there for about 15 minutes. Now I've closed the box and have waited several minutes with no activity. This is pretty aggravating. Thanks for any help.

try turning off your antivirus aplication. thats work for me flashing my tytn to wm6.

I've done everything.... I guess
Hi...
Yes, I consulted the www.mrvanx.org, excellent tutorials.
I flashed without problem the radio and bootloader. The progress bar started to "progress" and everything was fine. The only problem I have is flashing the WM6.
I don't remember where, but I readed that flashing the bootloader "Hard SLP v7" causes my HTC not to accept any Oficial WM6 ROM. The article said that I only had the chance to flash a coocked or modified ROMs. Is this true?
If not... what else can it be? I also closed all my applicacations including the antivirus, goback, disabled the internet connection, the logictec mouse center, etc. and nothing, the same as Chicoh happens to me.
"Error 260: Connection... check the USB cable bla bla bla."
Should I restart in safe mode to do the flashing?
Should I try to install a modified ROM?
Have in mind I've tried three different official ROMs: WWE, Cingular and spanish.
Thanks to all the comunity!!!
Saludos desde México!!

Greetings -
I had a similar problem and couldn't get the thing get going. My solution was to load it from the SD card. This worked flawlessly.

liquidsilver said:
Greetings -
I had a similar problem and couldn't get the thing get going. My solution was to load it from the SD card. This worked flawlessly.
Click to expand...
Click to collapse
I'm trying that as we speak. I have a good feeling about this. I'm a little concerned that I didn't think of it though. Makes perfect sense - Skip the middle man.
UPDATE: Crap. No luck. Thanks all the same though. I'm not giving up.

What OS are you using, xp or vista? My vista 'top had the same problem wouldnt flash for the longest time and i had to use my xp.
However, it does work now. Not entirely sure why.

Now I had success!!!
Hello my friends.
It seems that the article I readed days ago detailing that after flashing the Hard SPL v7, I could only install a modified ROM, not an official one from HTC or Cingular.
I downloaded Black Satin and installed it without any troubles. The entire process lasted only 3 minutes!!!
I wanted to have an official ROM, don't ask me why, and never tried the "other" ROMs that are actually excellent!!! some apps that were on WM5 are not in WM6, which is kind of sad, but if there's something that I love of WM Smartphones is that I can download and install whatever I want or develop it if it doesn't exist!!!
By the way, I use Windows XP Pro.
Thanks for all the support!!!
PS: Before flashing the Hard SPL v7, I tried installing the cingular WM6, but didn't make it. That's why I readed almost all the pages and threads here in xda-developers and found that flashing a new bootloader was a very good idea. The rest of the story is known by you.

Error 202 Hard-SPL Update

I am very frustrated with my HTC Touch Diamond as I am trying to update it to Hard-SPL yet when it's plugged into the computer (with active sync running) and I follow all the directions very closely, I go to update the phone and it doesn't show any activity on the phone, the progress bar on my computer screen shows 0%, then it eventually pops up with a message saying Error 202. This is a connection error, yet I am positive that the phone is plugged into the computer. Please HELP!

Hello, Did you run SSPL first? You can only flash hard spl when sspl is active it is a black screen.

I have a Telus HTC Touch, does that make a difference on whether or not this will work?

your diamond is cdma. these only work with gsm.

so by the word 'these' in the last post, you mean that the Rom updates won't work?

I don't think SPL has to do anything with CDMA or GSM. Some ROMs have an option in the phone settings to choose either GSM or CDMA.
ryanseyz: Make sure you have a factory ROM ready before trying the cooked ones here so when things happen unexpectedly, you always have a choice. Next, there are 2 versions of SPL here, try both. Make sure you install EnableRAPI.cab and CertSPCS.cab installed on your device.
Regards,
Carty..

anyone has a solution for this yet? I'm experiancing the same problem with my Touch Pro, can't seem to get it to work.
I installed both files like mentioned above but still give error 202.
The funny thing is it does recognize the current version of my rom (stock).
Greetings,
Phyrax

Phyrax said:
anyone has a solution for this yet? I'm experiancing the same problem with my Touch Pro, can't seem to get it to work.
I installed both files like mentioned above but still give error 202.
The funny thing is it does recognize the current version of my rom (stock).
Greetings,
Phyrax
Click to expand...
Click to collapse
The same here with my mda compact iv. I've tried all versions of the RUU of hardSPL with no result (error 202). When I update the official rom of t-mobile (1.93) with the RUU, there isn't a connection problem and everything goes well.
My device is not simlocked, but i suspect it has a security lock or something like that.

Hello, I have the same problem with a HTC Diamond : error 202 and everything is connected, hotsynched, etc.
Did anyone find a solution ?

anyone??? im having the same problem..

I'm having this issue as well, any solutions?

The same problem
I have a HTC Touch Diamond and have the same problem.
I don't know what i have to do to fix this problem.

I have got the same problem. Add I have problem with align screen, so I can't run any cab on device. Looking for any advice..

i have a htc mda basic ....same problem...any solution...please help....

I'm not sure, but if i'm not wrong i had the same 202 error code last time i tried to reflash original (stock) spl, for warranty reasons. I solved the problem flashing stock spl (from hspl 1.93 olinex) with the phone conencted to activesync: run sspl-manual.exe from the device (previously copy sspl-manual on the device): the phone will go to black screen; than run the normal romupdateutility.exe from pc, and follow ordinary instructions.
Hope this could help.

Dudubai said:
I'm not sure, but if i'm not wrong i had the same 202 error code last time i tried to reflash original (stock) spl, for warranty reasons. I solved the problem flashing stock spl (from hspl 1.93 olinex) with the phone conencted to activesync: run sspl-manual.exe from the device (previously copy sspl-manual on the device): the phone will go to black screen; than run the normal romupdateutility.exe from pc, and follow ordinary instructions.
Hope this could help.
Click to expand...
Click to collapse
Thank's..., this solution work for me...!!!

For me too !!! working now !

Thanks it work!

Thanks !!! It works !!!

HTC S620 updating issue...

Hi,
I've searched over this forum and cant find an answer to what I need so I figured I would post.
I have a HTC S620 (sim free) and it has WM5 on. I would like to upgrade to WM6. (not 6.1 yet.) I have looked over this forum and found lots of stuff on how to do it and I have tried 2 different ROMs and also watched the you tube video.
When I use the official wm6 ROM, (even before I have tried to install the ROM) my phone gets to the white screen stage and then disconnects which means the ROM installer doesnt work because the phone isn't connected.
I have also tried to isntall the kavana 6.1 version and the ROM installer comes up with an error code which says the model isnt compatiable.
The wm6 official upgrade looks more promising if any one has any solutions? although any solutions would be very welcome.
thanks
James.

jameskelsall said:
Hi,
I've searched over this forum and cant find an answer to what I need so I figured I would post.
I have a HTC S620 (sim free) and it has WM5 on. I would like to upgrade to WM6. (not 6.1 yet.) I have looked over this forum and found lots of stuff on how to do it and I have tried 2 different ROMs and also watched the you tube video.
When I use the official wm6 ROM, (even before I have tried to install the ROM) my phone gets to the white screen stage and then disconnects which means the ROM installer doesnt work because the phone isn't connected.
I have also tried to isntall the kavana 6.1 version and the ROM installer comes up with an error code which says the model isnt compatiable.
The wm6 official upgrade looks more promising if any one has any solutions? although any solutions would be very welcome.
thanks
James.
Click to expand...
Click to collapse
James,
How long have you had BT Anywhere as they have all been WM6 since over a year ago? Should bare any difference anyway, the phone will stop active sync when it goes white anyway.
You should be able to upgrade to WM6.1 without any hitches with following the "Upgrade to WM6.1" you should do this before hand http://forum.xda-developers.com/showpost.php?p=2807194&postcount=485 if getting error message "mind you may help if know what the message is?"

Hi cheers for the reply. It's not a BT one, its actually a second hand one off ebay so I assume its pretty old. Its just branded as HTC...

jameskelsall said:
Hi cheers for the reply. It's not a BT one, its actually a second hand one off ebay so I assume its pretty old. Its just branded as HTC...
Click to expand...
Click to collapse
Wow i must have been reading something totally different to posted lol
Still go with previous post to flash WM6.1 if you want to upgrade to WM6 you need to know what the original carrier of the phone is does it have a carrier plas on load?
Mind you i'd flash to WM6.1 if i was you as it's an advancemet far greater than WM5 to WM6

Hi again,
I've just tried the kavana 6.1 ROM following all the instructions you've said. It got as far as the white screen (through the DOS programme) and then it lost its USB connection which means the ROM installer wouldnt work as it couldnt find a connection. I'm running windows vista.
thanks

jameskelsall said:
Hi again,
I've just tried the kavana 6.1 ROM following all the instructions you've said. It got as far as the white screen (through the DOS programme) and then it lost its USB connection which means the ROM installer wouldnt work as it couldnt find a connection. I'm running windows vista.
thanks
Click to expand...
Click to collapse
When the whitescreen launches WMDC will stop sync and the computer takes over via it's own driver, did you leave it there with the white screen or just disconnect Dash when WMDC disconected?

ive yet to change a rom on vista because of the lack of ativesync which is really dumb

stylez said:
When the whitescreen launches WMDC will stop sync and the computer takes over via it's own driver, did you leave it there with the white screen or just disconnect Dash when WMDC disconected?
Click to expand...
Click to collapse
I left it there with the white screen, didnt touch any USB connections or anything. When I did this, the windows sound sounded (as in when something is disconnected) and the green light went off on the phone and the ROM installer wouldnt run because it says the phone is disconnected...Cheers for your help btw
James.

Isn't there a center key press on the d-pad in there somewhere? Are you doing that?

Hi guys, I've managed to resolve the issue and im all sorted now. Just used a different USB port. Thanks for your help

[Q] Touch Diamond :: permanent reboot :: bootloader update back to Stock SPL imposs.

Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers

same problemm
Same problem. Any help?

tekata said:
Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers
Click to expand...
Click to collapse
Any chance to MTTY? Might help, just guessing...
Or try to flash a new radio ROM as the wifi hardware might be stuck in a state that is unknown to the drivers. Flashing a radio is supposed to reset hardware but I may be wrong.
Really guessing here but symptoms shows relation to radio hardware.
Cheers,
Cina.

sspl
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.

Hello, my solution to this was conductive interconnect of metalic parts as you can see here
://i.ytimg.com/vi/UUnH8O-1jII/0.jpg
(of course with http on the beginning, i'm not allowed to post links)
on the left with aluminium tape (sorry for image quality, found it on web).
It also seems that the sim card reader has to be conductively connected with the above em shielding.
Hope it will help

it´s a battery problem ... get a different one and your phone should be fine

Dreamtheater2003 said:
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.
Click to expand...
Click to collapse
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
@edefux
Do you already had such a case? I am not sure, if buying a new battery is economical enough only in order to try, if it works. I admit, it could be the battery. But running the phone with the charger switched on, should show if its the battery or not. I tried with charger on, but obviously this didn't solve the problem. Or do you mean, that in the battery there is some sort of "short circuit", that's confusing the Diamond no matter if the charger is on or not?
@DiamondFlower
Thanks for the suggestion. I'll give it a try, when I tried everything else
This will be the final try before burrying the precious Diamond.
Cheerz

MTTY.
tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
...
Cheerz
Click to expand...
Click to collapse
See this post for MTTY. This is the second post on Diamond ROM thread pinned for easy access anyway. Please search before you post!
If you can enter bootloader mode with VolDown pressed while reboot you're off to go. You can plug in USB cable and you can flash SPL, Radio or any new ROM. I assumed this based on your first post:
tekata said:
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
Click to expand...
Click to collapse
Cheers,
Cina.

it is a battery problem i´m 99,9% sure of it - i had the same case ... it was driving me crazy ... different roms, radios, but the problem persisted - luckily at that time i was working at a cell phone provider and could try different hardware, which finally brought me to the solution to switch the battery.

edefux said:
it is a battery problem i´m 99,9% sure of it...
Click to expand...
Click to collapse
Maybe I'm a bit unlucky, but I've got the 0,1%. Took a new battery, this didn't solve the problem though.

i´m sorry it didn´t work for you ... !

it's ok! it didn't work - actually I could have thought about it wont work: beforehand I sent the item to the mobile operator guarantee team and they returned it back - no warranty of course (due to olinex bootloader which I wasn't able to remove) and stating: Fremdeinwirkung/ Totalschaden (total loss). And because I sent it without battery and they obviously checked it ... suppose with a fresh or "good" battery. And it still didn't work for them, so...
I'll try to open it and see if there is some short circuit around the metal shielding. Maybe I'm lucky then.
Anyway thanks guys about the hints and suggestions!

tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
Click to expand...
Click to collapse
I'm not sure if its called sspl but you can run it from boot loader and it will black out your phone. after that you need flash the new bootloader.
I'm thinking its not a bootloader problem though...

[Q] Nothing from this site works on my phone

Morning,
I have tried countless times to upgrade my ROM, Custom RUU, task29, etc.... Everything ends exactly the same; Screen on the phone shows the multi color background with "USB" at the bottom of the page, then both my laptop and the phone show a status bar that never moves off of 0%. I let it sit for a while, then I get some form or another of a communication error. It wants me to perform a "Recovery" but that never works either. I always have the same results.
When I try to use the HardSPL file, I get an error that states "Windows cannot access the specefic device, path or file. You may not have the appropriate permissions to access them." It does not matter how I try it or "Run as Administrator" it still does not work.
When I connect my phone to the laptop, Activesync kicks in and establishes a connection, when the screen goes multi color with "USB" at the bottom, I hear the laptop ding as it does when a USB device is disconnected. I don't hear any dings as if it were reconnecting. I have tried this on 2 different Win7 machines and get the same results.
I would love to flash the ROM on this thing as it is over bloated with apps that I don't want/need/care to have! I know this phone has the potential to be very a very cool phone, so I am begging for help on this one.
I have succefully flashed the ROM on my old HTC Fuze phone with no issue at all. I have to wonder when I see the threads for doing this is over 2 years old if that has anything to do with it.
If anyone could please assist me in getting this sorted so I can open my phone up to new and different possibilities, that would be great!
Thanks
Joe
B 80
R 4.48.25.89
G 61.39tc.25.30h
D 1.59.67150

1. So your only problem is that you can't hardspl. Then why do you say that nothing from this site works?
2. Ask hardspl questions in the hardspl thread.
3. Try entering bootloader and then plugin your usb and perform a hardspl.
For further help, you should really ask in the hardspl thread

Lennyz1988 said:
1. So your only problem is that you can't hardspl. Then why do you say that nothing from this site works?
Click to expand...
Click to collapse
Yeah, the OP is really only having problems with HardSPL, and nothing else (not being able to run Task29 or a flash a custom ROM is due to not being HardSPLed). Why flame the entire website, and the thousands of ROMs, CABs, and other stuff that people dedicate their time and hard work to accomplish?
If you are using Windows 7, you should not be using Active Sync, you should be using Windows Mobile Device Center.
http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
This may be the problem. But HardSPL on Windows 7 is a known issue if you read the HardSPL thread. It works for some W7 user, and not for others. If this continues to be the case, your best bet is to find a XP machine and HardSPL from there. Other things, like flashing a custom ROM should work fine on your W7 machine (using WMDC).