Help flashing new ROM please - Touch Dual, MDA Touch Plus ROM Development

I've installed HardSPL and want now to flash a new ROM but no matter which I try none work. Each time I try to use a new room I get an ERROR 260 connection error. How can I avoid this?
I've tried following the service manual for the Touch dual which describes how to flash from an SD card but I've had no luck with that either.
I've read adn reread these forums and don't know what to do next. Any help appreciated.
Stu

First make sure that you phone is Niki

The bootloader says NIKI200, SPL-1.16.Hard, CPLD-4. The current ROM is 1.35.110.06 and is T-Mobile branded.
I used the HardSPL from JockeyW but have not used his CID unlock. Do I need to CID unlock to flash a new ROM?
The problem seems to come when I run any RUU. I start with my phone booted into Windows mobile and with an activesync connection to my pc. I run a RUU and follow the instructions. I get to the progress screen, my phone boots to the tricolor bootloader screen. There is no flashing progress and then the RUU says connection error 260.
How do I avoid the connection error? Do I need to change the activesync connection settings before running the ruu?

try flash from bootloader (power off device, press'n'hold camera button, power on device) and run RUU utility

Related

Error Upgrading my HTC Tytn

I have tried many times to upgrade the Rom Image on my HTC Tytn (Cingular 8525) with no success. I am getting a 260 error with the program located at this link...
http://forum.xda-developers.com/showthread.php?t=293665
I did first run the unlocking application to unlock both SIM and CID before running the upgrade.
I followed all the steps exactly and have had no success...
The following might be effecting my attempt:
I am running my pc on Vista
I am syncing with Windows Mobile Device Center
I have tried to solve this problem for about two weeks. Can anyone help me?
Mrvanx has a guide on how to prepare Vista for flashing, you can find it here.
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Same problem
compwiz2008 said:
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Click to expand...
Click to collapse
Same problem here trying to change the radio version after changing the bootloader........
Connection alwayse lost just as said above.
Any help will be appreciuated
justx24
Use the RUU wrapper with the NBH file you want to upgrade.
I still have the same issue, even when using the RUU Wrapper and any nhb.
don't use vista
Ok, got one step furthur
I reached the point where the ROM Begins to update, which is VERY good...
The ROM update Reaches 1%, then waits for 20 minutes...
Then I get a 262 error and have to go through recovery, try again, with the same result.
i have same problem plz help thnx in advance
compwiz2008 said:
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Click to expand...
Click to collapse
Have you tried removing or adding a checkmark to the USB to PC in CONNECTIONS on your device? I remember having a similar problem when I installed Radio Rom 1.38 that my USB connection was lost with the pc . I am using XP when flashing so if you have no luck then do this on a XP machine.
Forgot to ask! What ROM are you trying to flash??
@compwiz2008 and ahmerpar
I read somewhere that running windows update will update WMDC........maybe give that a shot?
Maybe you can try to upgrade your ROM from your SD card.
Nope
Let me try that...
Still did not work
I'm probably going to just take my phone to a computer repair shop and pay them to deal with it, since I'm evedently doing something wrong.

Problem with RUU

Ok...I have been through all the posts about upgrading etc. I still have a problem and I'm sure that I'm overlooking something....but I can't figure it out on my own. Here is what is happening (it does the same thing with every RUU that I've used...the DST fix...upgrading to WM6....etc)
1. I run the RUU and let it go through its routine (extract files, verify info on pc, etc.)
2. I check the box that says I have read the readme and click next
3. The next screen appears and it has the following steps:
Connect to the USB cable (check)
Establish an ActiveSync Connection (check)
Disable standby and hibernation on PC (check)
Make sure batter is > 50% (check)
Then I check the box and click next
4. I pick the update and click on the update button
5. I verify that I want to upgrade my phone from ROM verion x.xx.xxx to x.xx.xxx and click next
6. The program tells me that I am finally ready to update...and if I am sure I want to proceed to click next...so I click next
7. As soon as I click next...the progress bar comes up on my pc and my phone goes into standby mode (no bootloader...just standby). The progress bar never moves.
8. After a minute or two the RUU give me the ERROR [260]: Connection
9. I reboot my device and repeat steps 1-8
10. I reboot my device and my computer and repeat steps 1 - 8.
Now if I leave my device connected to the usb and close out the RUU after it gives me the ERROR [260], and then run the RUU again...when it is first verifying the information on my pc (before it asks any questions and before it tells me to connect my device) it will throw the device into bootloader mode. If I try to keep running the RUU while the device is in bootloader mode it give me the error that my device is not connected. I have tried and tried...maybe one of ya'll can help me. Thanks in advance
Chris
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
gerald_s said:
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
Click to expand...
Click to collapse
XP
No firewall
I tried to flash the WM6 from AT&T I assume its beta
and no did not install the Olipros bootloader
Ok...I think I found out how to do this...Ya'll can tell me if I'm screwing something up.
I go through all the steps listed above until it gets to the progress screen. When it gets there I manually put the the device in bootloader mode (Power, side ok, and reset). Once I do this...the progress bar starts moving. I will let you know if this works...
Hmmmm
Its not the way it should work but if it works its ok
You should have installed Olipros HardSPL first and then try to flash an official rom. If its working then something with your download is wrong.
What ROM is on there now?
Has the phone been CID unlocked?
Oli's CustomRUU is better, you may want to unpack the ROM and put the NBH in a folder with Oli's RUU and then do the upgrade.
BTW, gerald_s is right, you should not have to do that... what you may want to do is put the phone in Bootloader mode manually (while not connected to the PC), then plug in the USB, then start the RUU. That helps some people with 260 error.
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
You may be trying to flash a rom that includes the radio rom. What is your device? Is it possible that your device is a new x01ht with radio 1.14 and radio bootloader 0182? If yes, then you will get this error when you try to flash a rom with this method because during the flash it will be disconnected by the radio bootloader because it is not overwriteable. If you flash using the NBH file on the microSD, it will skip past radio and radio boot and just flash the other parts of the file.
mikebraeuer said:
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
Click to expand...
Click to collapse
If you are running windows XP, just connect the card to the computer, open MY COMPUTER, right-click the removable disk that is your microSD and then click format. Default in windows xp is to format using FAT32 filesystem which is perfect.
The thing is... if you dont know how to format a drive in Windows, should you be flashing your device yourself?
Which Solution???
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Wantoknow said:
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Click to expand...
Click to collapse
Have you tried flashing with your microSD?
Kevbodian said:
Have you tried flashing with your microSD?
Click to expand...
Click to collapse
I forgot to tell that, I had flashed through extra memory card yet, and could be done!
But I wanna flash ROM against CustomRUU through MS Active Sync as I had used before. Can you help me
i have a problem very similar to Chris. when i check the box "yes activesync is syncronised", and then the progressbar shows up and the phone goes into standby.
i've turned standby of in powermanagement options.
my os is XP
i use active sync v4.5
and this is first time i try this.
i've read something about this bootloader, i can get there but then i cannot sync with active sync. so i kinda stuck.
have been searching the forums and this was the same problem as mine but i don't understand your solutions.
//KufrA
--Problem solved--
i did all things without activesync,
1. start phone in bootloader
2. do the install
3. wait 0% to 100%, and done.
is there a problem with active sync or why do i have to do anything with it at all?

[Resolved]: Stuck at Bootloader 1.06, titan_exitbl.exe isn't working.

Hi Folks,
I'm stuck in the tri-color screen for bootloader 1.06.
I have DCD 3.2.0 w/3.42.02 radio on the XV6800 and was trying to upgrade to radio 3.42.30. My system is Vista 32-bit.
I ran the Titan Relocker and it put SPL-1.06.0000 back onto the device and was planning on then putting 1.2 onto it.
Running titan_exitbl.exe says "Cannot open USB port. Please make sure, that USB connection in ActiveSync is disabled."
Unfortunately it is now stuck and even after ending the Sync Center service I can't get titan_exitbl.exe to pull it out of the Boot Loader.
Ideas? Thank you!
I could fire up an old XP laptop and try it from there.
Loaded ActiveSync 4.5 on an XP laptop, disabled USB connections, ran titan-exebl.exe and the device is booting now.
I'll continue on and see what else I can screw up.
Loaded SPL 1.20
Loaded 3.42.30
Loaded SPL 2.40
Device is back to working! Off to see if GPS is back after being lost with 3.42.02.
titan-exebl.exe
Where can I find titan-exebl.exe? Google doesn't turn up any results other than here?
titan_exitbl.exe
Never mind... just located it on my own hard drive!
Cheers!
Stuck on Bootloader
OK... I've tried titan_exitbl.exe, and it still doesn't work.
Here's my problem in chronological order:
1. I've been having a few problems (bugs) in my current custom ROM (PPC Kitchen 3.49 version), so I decided to re-flash to a stock ROM, see if the problems were fixed, and then try to flash back to a custom ROM.
2. I tried flashing to the Sprint 3.35 ROM. The RUU showed the progress bar on both my PC and the phone. But at 0%, I got a message saying "an error has occured" - or something to that effect.
3. I decided that the error was because I was running a custom ROM, and Sprint didn't like that. So I ran the Titan Relocker utility, thinking this would cure the problem.
4. I followed the steps on the screen and then got a message saying the relocker utility had completed successfully. The phone rebooted and went into the tri-color bootloader mode.
5. I retried the Sprint 3.35 ROM update, but got the same connection error, and the progress slider would never move from 0%.
6. I decided the phone had locked up and performed a reset with the stylus. The phone rebooted and went back into bootloader mode. The screen shows "TITA100 SPL-1.06.0000"
7. And that's as far as I've gotten. I've tried several hard resets using the buttons and the stylus together. I've tried removing the battery and reinstalliong... but the phone just goes back into bootloader mode.
I've tried both titan_exitbl.exe and UNI_Exitbootloader.exe, and neither utility seems to help. I get a message saying that "All data was sent... the phone will reboot now... please check your screen". The phone's screen blinks for a moment, and then returns to bootloader. Nothing can get it anywhere else.
I've tried different USB cables and ports. Activesync won't detect it, but the utility update software does.
When I run the Sprint 3.35 ROM update utility, I get an error at 11% saying "invalid vendor ID" and the update refuses to run. I tried to run the Titan Re-locker utility again, but it requires an ActiveSync connection. I've tried both enabling and disabling the USB connection in ActiveSync, but that seems to make no difference. The utility simply says no USB connection is available. The ROM update utilities will detect the device via USB - they just refuse to work with them.
I also tried running a DCD Tital 2.1.0 Bell ROM. The progress slider freezes at 0%, and then I get a message saying the RUU has encountered communication errors during the update. I've been through the recovery process the utiity suggests about a dozen times... it sill returns the phone to the bootloader screen.
So I'm getting pretty frustrated... does anyone have any ideas?
Try changing your spl back to 2.40.
Throwing it back into the tri color screen again and flash the sprint stock 3.35
But put it on the root of a fat32 formatted micro sd card in the flavor of under 2gb.
Just run the exe from your computer it will extract the files from the exe to some location on your computer, normally the ruu update folder.
There will be a ruu_sighned.nbh file locate it and copy it to the fat32 formatted card rename it TITAIMG.nbh
Let the phone boot into the bootloader and it should detect the file on the sd and update the rom for you, by stating loading ......
Then will prompt you to update press power key.
Sense you are not on sprint don't let the first time custimizations run ... pull battery once you get to your mobile today screen on first boot...
Use active sync or the sd method to update your rom to whatever you wanted originally.
Most full updates from carriers the ones that flash both the radio and rom will run regardless of the boot loader thats on the device.
Happy flashing
Just thought I'd toss in here that GPS does work, but I have to use GPS Viewer to get a lock on the satellites first.
softwind said:
OK... I've tried titan_exitbl.exe, and it still doesn't work.
Here's my problem in chronological order:
1. I've been having a few problems (bugs) in my current custom ROM (PPC Kitchen 3.49 version), so I decided to re-flash to a stock ROM, see if the problems were fixed, and then try to flash back to a custom ROM.
2. I tried flashing to the Sprint 3.35 ROM. The RUU showed the progress bar on both my PC and the phone. But at 0%, I got a message saying "an error has occured" - or something to that effect.
3. I decided that the error was because I was running a custom ROM, and Sprint didn't like that. So I ran the Titan Relocker utility, thinking this would cure the problem.
4. I followed the steps on the screen and then got a message saying the relocker utility had completed successfully. The phone rebooted and went into the tri-color bootloader mode.
5. I retried the Sprint 3.35 ROM update, but got the same connection error, and the progress slider would never move from 0%.
6. I decided the phone had locked up and performed a reset with the stylus. The phone rebooted and went back into bootloader mode. The screen shows "TITA100 SPL-1.06.0000"
7. And that's as far as I've gotten. I've tried several hard resets using the buttons and the stylus together. I've tried removing the battery and reinstalliong... but the phone just goes back into bootloader mode.
I've tried both titan_exitbl.exe and UNI_Exitbootloader.exe, and neither utility seems to help. I get a message saying that "All data was sent... the phone will reboot now... please check your screen". The phone's screen blinks for a moment, and then returns to bootloader. Nothing can get it anywhere else.
I've tried different USB cables and ports. Activesync won't detect it, but the utility update software does.
When I run the Sprint 3.35 ROM update utility, I get an error at 11% saying "invalid vendor ID" and the update refuses to run. I tried to run the Titan Re-locker utility again, but it requires an ActiveSync connection. I've tried both enabling and disabling the USB connection in ActiveSync, but that seems to make no difference. The utility simply says no USB connection is available. The ROM update utilities will detect the device via USB - they just refuse to work with them.
I also tried running a DCD Tital 2.1.0 Bell ROM. The progress slider freezes at 0%, and then I get a message saying the RUU has encountered communication errors during the update. I've been through the recovery process the utiity suggests about a dozen times... it sill returns the phone to the bootloader screen.
So I'm getting pretty frustrated... does anyone have any ideas?
Click to expand...
Click to collapse
please i have this problem how to fix this?
Please state your exact problem and what you did to cause it. Including all versions of rom and radio and bootloader.
drewcam888 said:
Please state your exact problem and what you did to cause it. Including all versions of rom and radio and bootloader.
Click to expand...
Click to collapse
Thanks!!! Ok, i cant remember eactly what is the v radio but i think 3.35 or 3.42 i cant remember exactly it's one of these. the SPL 1.06 Locked i cant unlocked i cant use titan_exitbl.... the SD update doesnt work stuck on loading.., i cant update from pc stuck 0% then Recovery Error help me. I My phone is bricked? Sorry for my english....
Did you try to install 2.4 unlocker?
drewcam888 said:
Did you try to install 2.4 unlocker?
Click to expand...
Click to collapse
Yes, i try from SD and nothing stuck on loading... from windows with RUU nothing 0% stuck and then UPDATE ERROR[262] now i don't know to do
2.4 doesnt use sd and it is run from a .exe. Make sure you aren't trying 2.47. Are you sure you tried this?
drewcam888 said:
2.4 doesnt use sd and it is run from a .exe. Make sure you aren't trying 2.47. Are you sure you tried this?
Click to expand...
Click to collapse
Ok, but how run from windows? If i cant connect via activesyncs the phone is on SPL mode i cant out of that and the msdos windows say "No device conected" when press enter from windows i cant unlock. Any idea? I'll try 2.47 but how run from windows with the phone en SPL Mode?
Please read. I said run 2.4 not 2.47. Put the phone in bootloader and it should say usb at the bottom. Then run 2.4 .exe unlocker. I think it should run without using activesync. And by spl mode do you mean the phone is in the bootloader.
drewcam888 said:
Please read. I said run 2.4 not 2.47. Put the phone in bootloader and it should say usb at the bottom. Then run 2.4 .exe unlocker. I think it should run without using activesync. And by spl mode do you mean the phone is in the bootloader.
Click to expand...
Click to collapse
Look i cant run Hard-SPL-MFG (Olipro 2.40 Unlocker) because when i run the Bat Or MSDOS Windows say "No device connect" question me if i want retray copy the file.
Ok so i guess it needs activesync. About your only option is to install a pregps rom so the phone will boot and then you can reflash the custom rom. Below is a pregps Verizon rom and radio that will work for 1.06 bootloader. Called rom 2.09.
http://forum.ppcgeeks.com/showpost.php?p=834294&postcount=4
drewcam888 said:
Ok so i guess it needs activesync. About your only option is to install a pregps rom so the phone will boot and then you can reflash the custom rom. Below is a pregps Verizon rom and radio that will work for 1.06 bootloader. Called rom 2.09.
http://forum.ppcgeeks.com/showpost.php?p=834294&postcount=4
Click to expand...
Click to collapse
No luck, method A SD Card Loading.. then cheking... then show a number corner 00028002 and say down Not allowed.
Method B, via PC and RUU then ERROR INVALID VENDOR ID.
Any idea? Thanks bro.
I think my phone is bricked... noway load the rom... i've tried load bootloader unlocked via SD last option and nothing!! damn this is so

P4000 stuck in bootloader

Just did the titan unlocker and now the p4000 is stuck in bootloader with these 2 lines:
TITA100
SPL-1.20.Olipro
i think i need some help
thanks in advance
Marc
edit:
RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_3.42.02_SPCS2.0 4_PPST_0619_Ship.exe >>> would flashing this ROM and Radio save me or my titan?
orangeworx said:
edit:
RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_3.42.02_SPCS2.0 4_PPST_0619_Ship.exe >>> would flashing this ROM and Radio save me or my titan?
Click to expand...
Click to collapse
yes..............
since i'm stuck in bootloader mode, how can i use the ruu update utility ?
i'm getting connectiong failed and only option is to exit utility
any ideas ?
if u are in bootloader connect the usb cable and the phone should say usb at the bottom, just open up the ruu update and it should work just fine
Error 264
update utility cannot connect to your pda
and it says USB on the bootloader screen
SPL is 1.20 olipro
take your SD card out if (with phone powered off) if u have an image on the SD card and retry
no SD card being used at the moment
edit: it seems now it is flashing...
let's say this does work, fact that i'm putting a sprint ROM on my telus phone is gonna be alright?
re-edit: crashed at 11% - invalid command error 290... RUU encountered a communication error
recovery
at 11%, titan reset and went back into bootloader mode, RUU crashed but gave option for recovery which was "successful"
retried the same RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_3.42.02_SPCS2.04_PPST_0619_Ship.exe
and crashed again at 11%
i think i killed my phone
i can't seem to do anything, not the telus wm6.0 ruu nor the one stated earlier...
is there a way i can revert to my previous SPL 1.04 ?
really appreciate the help @ 5:35 AM
got my telus wm6 to run and then decided to up to olipro 2.40
now it won't got past second splash...
radio is 1.32, rom is dcd 3.2.5
now from my understanding of what i've been reading is that i need to revert to olipro 1.20 to be able to flash my radio
and i can't do that since i can't get activesync.
any ideas ?
Get a SD card. Go to WIKI and following reverting to Stock. Then start over on flashing. I have done as you did and fixed the phone.
your phone sounds jacked up, how long is it stalling at 11%, r u giving it decent enough time?
redownload the latest sprint rom from htc america here:
http://216.139.227.226/RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_TITAN_3.42.02_SPCS2.04_PPST_0718_Ship.exe
let it run for at least 20 minutes before deciding it crashed...after 1st boot softreset before letting it run any customizations

Help please! Hermes (Orange SPV M3100) drops USB when entering bootloader

I need some expert help please! I have a Hermes (Orange SPV M3100) that I want to flash with a custom ROM but I am having a problem with ActiveSync losing the USB connection at the point that the device enters the bootloader screen. I am also unable to flash using the SD card method. I have flashed a Nike without any problems and I'm usually good with technical stuff so I think there must be something extra I need to do that I have missed. I hope that somebody can spare the time to help me solve the problem. Here are the details:-
I am trying to follow Mr Vanxs guide to flashing the ROM in windows Vista so that I can upgrade it from WM5 to WM6 and apply a custom ROM to load a new TouchFlo style OS. The first step in this process is to flash HardSPL using this guide but my problem with the USB connection won't let me do that. I have unlocked the device using Hermes Unlocker 3a so it is (or should be) SIM and CID unlocked and be SuperCID with HardSPL-1.40 (so maybe I can miss the Mr Vanxs HardSPL step?).
So, when I run the RUUWrapper.exe, choosing the Force option and accepting the messages I eventually get a prompt on the device. At this stage ActiveSync is connected. I click Yes on the device and it enters the bootloader screen which shows 'USB' on the tri-color screen but ActiveSync immediately drops the USB connection. The update then waits for a while then fails with Error 260. I have to do a soft reset to get the device out of the bootloader screen. When the device reboots the Activesync connection comes back to life.
I thought that I maybe don't need to HardSPL first so I tried just going straight to the ROM upgrade but I get the same problem.
Also, I tried following this link to flash using the SD card instead of USB but when I get to step 6 I don't see a confirm message - just the usual bootloader screen (it doesn't help that the screen shot doesn't appear on the link so I'm not even sure if I'm getting the correct screen). Any ideas?
I realise that an answer to this probably already exists somewhere on the forum but I have spent hours trawling through posts and I can't find it so I hope somebody has come across this before and can help me out.
Thanks guys!
Don't worry I solved it by rebooting my PC, skipping the HardSPL and flashing with an official ROM (HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108). I can now apply custom ROMs.

Categories

Resources