as soon as i try and flash the HSPL or a ROM it disconnects me from my usb connection, ive made sure numerous times that it is synced up before i start the flashing but as soon as they start it automatically disconnects me and the flashing doesnt work. Ive tried switching usb ports on my comp and nothings worked.... any ideas????
enter bootloader manually, when on coloured screen connect usb, wait for word serial to change to usb, and dont forget to right click and 'run as administrator'
thank you that worked so far, also its asking me which HSPL verson to install....
2.08. HSPL? or 2.08.0000?
it says my installed version is 2.10.0000
fbstud said:
2.08. HSPL? or 2.08.0000?
Click to expand...
Click to collapse
go on, have a guess, , is it the one with HSPL in the version, or the one without?, , , , , , ,
2.08.0000 is for returning to stock, you want 2.08.hspl
My first post!
And that last one above there made me chuckle, alot!
Sorry for posting on something almost a month old but it's the closest thing I can find to my problem.
So I've figured out I need HSPL to do any flashing, so i figured HSPL3 would be a good choice?
I'm currently on my boot screen and it says i have SPL- 1.42.0000, but the word at the bottom will not change from Serial to USB. I've got the HSPL3_PKG ready to run as admin when it does, but no change at the moment
Thanks for the help
forgive the dumb question, but the usb cable IS plugged in to the phone AND the computer, right?
haha yeh.
im on a laptop, there are 3 USB ports and i've tried them all.
there is one thing, one time when my phone was plugged in it started the whole windows device driver software thing, and then it said that it failed. could that be causing some sort of usb connection problems with my phone?
thanks alot, I see you're very busy!
is it something to do with my stock rom that ive not seen mentioned anywhere
1.43.206.4 (70315) WWE
?
:S
no, not the rom, but yea, the drivers not installing is probably it. You need to make sure that windows mobile device center (or active sync if you are on xp) is the latest version.
what you can try is, (after you have made sure you're on the latest wmdc version of course) with the phone connected, call up device manager, (on vista/7 , right click my computer, choose properties, device manager should be an option down teh left) find the entry for the phone (probably called unknown device, or something) and right click it, and choose update driver.
been trying to get hold of a WMDC download all evening but i think i'm hitting some server problem their end.
just checked the version i have, is 6.1.6965 and i think it was 6.1 i was after so i guess ill try and hook it up like you said above, will let you know...
damn 'windows has determined that the driver software for your device is up to date' think i have a plagued HD2 :S
wait, just reread you r fisrt post again.
When you start to flash it DOES disconnect, its supposed to disconnect.
Try this, enter bootloader manually, connect the usb cable (ignore what does or doesnt happen on teh pc) on teh phone, does the word serial change to usb? if it does, run your flash.
EDIT - oh, lol, you arent the OP, and i just read post 1, lol, ignore.
apparently i am missing some driver, Qualcomm CDMA or something like that... trouble is that i cant get a hold of it, theres a few threads on xda that mention it but no solutions.
normally, when a comp is asking for qualcomm drivers, it indicates a problem. Mostly it is when a tmous has been bricked, but occasionally other people have reported it. There aren't any qualcomm drivers that we know of. (Well, theres a thread that is titled qualcomm drivers, and does indeed include what appear to be drivers, but they wont install on windows.)
If i were you id focus on trying to find another pc to try it on. That way you will know if its a pc problem or a phone problem.
good call, i think ill opt for the trusty XP, just need to find that old laptop...
hopfuly you won't be hearing from me for a while.
i read that XP is more stable for flashing off of cos its more blunt, what do you think?
well, its certainly seems to cause less problems, especially HSPL'ing.
Good luck, and goodnight.
Related
So I recently downloaded the "RUU_Hermes_CINGULAR_WWE_2_1_[1].15.502.3_6275_1.40.30.00_108_Ship" ROM for my 8525, in hopes that it will provide me with a more stable pda/phone enviroment so that I may do the work I need to without having to hard reset every other day or so.
When I try to run the ROM install, I follow all the insturctions but when the update starts to run, it shuts my activesync connection off so the update can't run and throws back an error that it lost connection with the device.
Any Help Here? Thanks
PS: I love the idea of being able to use my 8525 for all my work and play needs, but if this update doesn't help make the device more stable, I will have to sell it for something that doesn't crash this much.
hey..iv got same problem.. i think it maybe cause we are using windows vista (thats the only information i can find about it).. i wanted to update ma rom aswell
I'm using XP Pro.
try running it on another system...if available...
anyone know the solution to this?!
OK, have you installed HardSPL ??
Check my SAFE WM5 upgrade guide, if you follow the procedures in there you should be fine.
Yeah, as far as stability goes most the wm5 roms out of the box aren't going to be the best. with any rom i use sktools to tune it up for performance/stability settings. It does this automatically so you don't have to find various registry keys. So don't think just because you are going to another rom everything will be okay.
Read the wiki, search the threads, you will find answers to all your problems.
As far as you not being able to connect what is your spl number? Also, have you tried hard reseting then connecting or trying another computer. I had the same problem when downgrading a black 2.5 with hard spl 2.1 ( i had to downgrade to send it back to cingular). I ended up just downgrading to the highest version of cingular rom which is branded AT&T. It looked like a pretty good rom but I did not play with it.
he does not need hardSPL(at least i dont think so) he is just runnning an update for another cingular ROM, its still the same CID...try running it on another system, i had this same problem and it worked on another system....
Malik05 said:
he does not need hardSPL(at least i dont think so) he is just runnning an update for another cingular ROM, its still the same CID...try running it on another system, i had this same problem and it worked on another system....
Click to expand...
Click to collapse
HardSPL will protect him against a faulty SPL flash if it occurs, a newer SPL is likely to be in the ROM update aswell as a newer radio possibly. Having the same CID doesnt matter because if the radio or SPL flashing procedure messes up it can create a bricked device VERY easily (corrupt SPL or even a corrupted CID/Radio BL). Besides if he already has HardSPL that would explain why the RUU doesnt reconnect when the device is in bootloader mode.
mrvanx said:
HardSPL will protect him against a faulty SPL flash if it occurs, a newer SPL is likely to be in the ROM update aswell as a newer radio possibly. Having the same CID doesnt matter because if the radio or SPL flashing procedure messes up it can create a bricked device VERY easily (corrupt SPL or even a corrupted CID/Radio BL). Besides if he already has HardSPL that would explain why the RUU doesnt reconnect when the device is in bootloader mode.
Click to expand...
Click to collapse
point well taken...=)
you mention, since he has already gotten HardSPL, why would that mean his device doesnt reconnect in bootloader?
put it in bootloader first and then run the update...
make sure you disable usb connections with active sync put your phone in bootloader and run the update might as well go with WM6 its a lot more stable than any WM5 rom i have played with .
OS crash
I run ROM install then computer shuts itself now my 8525 show hi true color with red/blue/white i tried to hard reset to solve but till hi true color what should i do?
trgrapsonu said:
I run ROM install then computer shuts itself now my 8525 show hi true color with red/blue/white i tried to hard reset to solve but till hi true color what should i do?
Click to expand...
Click to collapse
I've run there updates on my 8525. If the computer is shutting itself down, try another computer. This sounds odd. More of a computer problem then a Tytn Problem.
Malik05 said:
try running it on another system...if available...
Click to expand...
Click to collapse
=) have you even tried it?
I'm having a problem connecting ActiveSync over USB. When I first got the phone I was able to use that connection. Then I set up BT ActiveSync. I believe at the time I could use either USB or BT, but it has been a while. BT sync was so much more convenient for me that I haven't used my USB connection except for charging the phone.
Today I tried to get set up to upgrade the ROM, but ActiveSync doesn't seem to work over USB anymore. I turned off BT on the phone. When I plug it into my laptop's USB port the laptop makes a sound indicating it sees the connection. It makes a different sound when I unplug it. I also see the orange charge light come on on the phone. I usually charge the phone this way when I am on the road since I don't carry the wall charger with me.
I think at one point I installed a river that I fdound here to access the phone in bootloader moder. Other than veryfying the phone connected this way, I never did anything with the driver. IT has been so long that I don't remember the details. Could that be affecting the connection for ActiveSync?
I have made sure my firewall is inactive. In Windows XP Device Manager I see an HTC USB Sync device under Windows CE devices. Would it be safe to remove that device?
Any ideas how I can get USB ActiveSync to work again?
Is it totally crazy to try the ROM upgrade over the BT connection?
emuyshondt said:
I'm having a problem connecting ActiveSync over USB. When I first got the phone I was able to use that connection. Then I set up BT ActiveSync. I believe at the time I could use either USB or BT, but it has been a while. BT sync was so much more convenient for me that I haven't used my USB connection except for charging the phone.
Today I tried to get set up to upgrade the ROM, but ActiveSync doesn't seem to work over USB anymore. I turned off BT on the phone. When I plug it into my laptop's USB port the laptop makes a sound indicating it sees the connection. It makes a different sound when I unplug it. I also see the orange charge light come on on the phone. I usually charge the phone this way when I am on the road since I don't carry the wall charger with me.
I think at one point I installed a river that I fdound here to access the phone in bootloader moder. Other than veryfying the phone connected this way, I never did anything with the driver. IT has been so long that I don't remember the details. Could that be affecting the connection for ActiveSync?
I have made sure my firewall is inactive. In Windows XP Device Manager I see an HTC USB Sync device under Windows CE devices. Would it be safe to remove that device?
Any ideas how I can get USB ActiveSync to work again?
Is it totally crazy to try the ROM upgrade over the BT connection?
Click to expand...
Click to collapse
have you tried changing the setting on your phone "USB to PC"? I would try this first before digging to deep
slavetolustnyc said:
So I recently downloaded the "RUU_Hermes_CINGULAR_WWE_2_1_[1].15.502.3_6275_1.40.30.00_108_Ship" ROM for my 8525, in hopes that it will provide me with a more stable . . . When I try to run the ROM install, I follow all the insturctions but when the update starts to run, it shuts my activesync connection off so . . .
Click to expand...
Click to collapse
You may want to try using the Hard SPL v7 and then install your ROM. I did that and all went smooth as silk - six times now. I have been browsing ROMs to see which one suited my needs an personality, and it has been fun. You can find that on my FTP site at ftp://xda:[email protected]/xda_dlz/
This is a dynamic IP Address from a cable modem so two things are true
1. It is subject to change at any time.
2. It is not as fast as some of these speedy servers
But, I do know where it is.
shogunmark said:
have you tried changing the setting on your phone "USB to PC"? I would try this first before digging to deep
Click to expand...
Click to collapse
I had tried this yesterday and checked the Enable advanced network functionality box. Today I unchecked it and suddenly the PC saw a new USB device (HTC Sync USB, I think). It still wouldn't sync automatically so I manually executed /windows/repllog.exe. This time it connected.
Some observations:
- After the connection was established the the name of my 8525 was changed to something different (something like WM_ComputerName1, Where ComputerName is my computer's host name). I changed the name back and was able to re-invoke repllog.exe and sync with the old name.
- If I disconnect the USB cable from the phone and plug it in again ActiveSync doesn't connect until I manually run repllog.exe. It does work when I run the exe on the phone manually.
I went ahead and started the upgrade process after connecting by running repllog.
Executing the RUU file from the HTC site first put SPL 1.11 on the phone and left the phone in bootloader mode (with the tricolor screen). I left the phone with bootloader screen and followed the instructions (although by now ActiveSync had shut down so the part about the AS connection that the installer asked for was not true). The progress bars appeared on both the phone and the PC. It took a few minutes to complete, but the update was successful.
After the upgrade I was able to sync over USB without any problems. I am now syncing my contact from Lotus Notes and setting things up to my liking. Once I got over the USB connection problem everything worked fine!
Hi.
I am a bit embarrassed about writing this, I never thought I would make a brick of my Prophet during “upgrades”...
But here I am, with a phone that don't want to sync with any computer after I accidentally pressed cancel on an active sync dialog box asking for setup with a new device, during upgrade to the latest Touch VIII. Have upgraded several times with several different ROM’s before, but this time things went wrong.
If I choose to start my device normally, it goes trough the HTC screen and stops after the Qtek (HTC in Norway) screen listing the different versions of the hardware…
When I restart to boot loader (Cam button + reset) the 3 colours turn up ok, but when I put an USB cable in the device and the lower, left part of the screen shows USB, active sync will not recognise any new device no matter what I do.
I can still find the Prophet when I go to properties on the computer, but somehow active sync does not care about that.
Are there any way to use a program at the host computer to sync properly with the Prophet?
I would really appreciate any help that could rectify this problem.
Regards, Lars Norway
I believe the " WM6 Upgrade Guide" thread has the info you needed.
panda88 said:
I believe the " WM6 Upgrade Guide" thread has the info you needed.
Click to expand...
Click to collapse
Tried the info there without success...
The guide assumes that you have connection with ActiveSync, but I can not seem to get connection.
So, I really need some advice about how to make a connection to the computer I will make the programming from, when ActiveSync is not working properly.
Have tried to restart both the device and the host computer, have reinstalled ActiveSync, have tried to start the different roms without having a connection to A.S., but no luck...
Have realized my mistake and bought a new Prophet, but would still like to get the old one working again.
it has nothing to do with activesync.
Not sure u really understand the below statement from the thread I mentioned.
RECOVERING FROM ERROR IN STEP 8 WM5->WM6
1. Don't panic
2. Don't panic
3. Unplug the phone
4. Reset with stylus,and keep the Camera Button pressed.
5. A 3 color screen will appear(Bootloader Screen)
6. Connect your device with your PC,and run the NVID(no vendor) WM5 rom.
7. The device will be resetted after RUU(rom update utility)finishes
8. Repeat the WM6 upgrade,from STEP 5..
in case you can't NVID roms, you can still use those step1 roms mentioned by ROM gurus here.
panda88 said:
6. Connect your device with your PC,and run the NVID(no vendor) WM5 rom.
Click to expand...
Click to collapse
Well, the problem is that I am not able to connect...
As far as I understand, the only way to connect is by using ActiveSync?
Regards
connect = the cable between prophet and your pc. after that just run the rom update utility. just dun bother the activesync (does it sound logical to u to establish activesync in bootloader mode?)
OK, I have tried it, but will try on some different computers also.
Posting in a couple of hours.
Thanks for your help so far!
then wish u good luck. happy un-bricking.
OK, same as before.
Depending on which ROM I try, the following messages are the result:
Error [300]: Invalid update tool.
Error [274]: Connection (The update utillity cannot connect to your PDA phone.)
If I try the Touch VIII direct, it stops in Initializing for a while, and then a message appears with the text: Cannot connect to device, Would I like to try again?
Besides, in the welcome screen during the "ROMUpdateUtility_NV_G4.exe" in the Prophet_PV_Temp program, step nr. 2. asks me to ""Establish an ActiceSync connection with your PDA phone."
So, no change from yesterday yet...
are you using windows vistA???
Have only been using computer with XP Pro installed.
Anybody of the opinion that the connection tools built into Vista might do a better job?
hifiasylum said:
Have only been using computer with XP Pro installed.
Anybody of the opinion that the connection tools built into Vista might do a better job?
Click to expand...
Click to collapse
No, on the contrary. The best change you have is XP. Zeroed asked about Vista because it could be the reason of your troubles.
What I should do is just one detail different of what you have already tried:
Put the prophet in bootloader.
DISable "allow USB conection" in the conection-setting panel of ActiveSync
Connect your prophet with the USB cable
Run the NVID RUU again
If that is succesfull, you can upgrade to the WM6 ROM you like.
OK, will do.
Tried Vista just now, same errors and no luck.
Be posting in a minute...
OK, now I'm back.
Made a restart of the host computer, changed settings in ActiveSync, startet my device in Bootloader...
But unfortunately, no more success this time either.
Feel that the device must be more seriously defective/broken than others, this mishap happend at the end of the programming, when the 3 partitions were being written in the device. I was loading Touch VIII...
Anybody know if there is any more combination of buttons or reset methodes I could try?
Next step is to start opening the Prophet...
hifiasylum said:
OK, now I'm back.
Made a restart of the host computer, changed settings in ActiveSync, startet my device in Bootloader...
But unfortunately, no more success this time either.
Feel that the device must be more seriously defective/broken than others, this mishap happend at the end of the programming, when the 3 partitions were being written in the device. I was loading Touch VIII...
Anybody know if there is any more combination of buttons or reset methodes I could try?
Next step is to start opening the Prophet...
Click to expand...
Click to collapse
Sorry, I'm out of options...
OK.
Thanks again for all help and support.
Really appreciated!
Regards, Lars
hifiasylum said:
OK.
Thanks again for all help and support.
Really appreciated!
Regards, Lars
Click to expand...
Click to collapse
Just wondering if your computer detects prophet as a device at all? Does the normal plug device sound comes on when you plug in? Just a long shot, stick in a SD card and try with windows media player to see if it can sync or put files onto SD card. if so, get rom refreshed via SD card...
try few hard resets before you try this.
Not quite sure I understood what you suggested. I can get the device up in the host computers machine properties, but there is no way to get it up in any other program - like the Windows explorer.
Or are you saying that there is a way to boot the Prophet directly from a SD card? That would impress me!!!
hifiasylum said:
Not quite sure I understood what you suggested. I can get the device up in the host computers machine properties, but there is no way to get it up in any other program - like the Windows explorer.
Or are you saying that there is a way to boot the Prophet directly from a SD card? That would impress me!!!
Click to expand...
Click to collapse
This sounds dumb, but try restarting your PC, closing all apps running in background (including firewalls), restarting Prophet (with stylus in reset hole). DO NOT TRY TO USE ACTIVE SYNC. Boot into bootloader (Three colours screen), connect USB cable and flash QTEK lastest official, or Jesterz AKU 3.3 (I have found this ROM to have magical powers of unbricking.)
Good luck!
hifiasylum said:
OK.
Thanks again for all help and support.
Really appreciated!
Regards, Lars
Click to expand...
Click to collapse
Hmm this is wierd.I ran into problem earlier this month trying to flash a ROM but got stuck somewhere. So I followed the steps given in the sticky thread. Everything work smoothly. I am using XP SP2 and mine is a G3.
Let's make the assumption that your PDA is not faulty. Maybe you can try the steps again but this time :-
1. Change to another USB cable (or you may test the existing cable by connecting to a working pda)
2. Change to another USB port
3. Make sure you are not running any program that hogs the USB resource
4. If you are using USB hub, please don't connect using it. Make a direct connection to your computer.
that's all I can offer now...hope it helps.
hi
guys i am newbie in upgrading and tried to run athena wraper and it died and after searching forums i still cant find cure ok so here it is i can do hard reset but it dosent help no boot up it still gives me ring round joystick good news is i can get it to bootloader screen (or at least thats what i think ) its red green blue and white screen with usb or serial (depending on cable )
screen reads
ATHE100
IPL-V0.90
ATHE100
SLP-V1.20.Olipro
now can any one help me ??
how can i upgrade rom with out device being detected by active sync every time i run upgrade utility it just comes up with connection error
still no luck
hi
still no luck
do i need special drivres to detect device if its in bootloader ?
it dosent show any thing in device manager when i connect it while its in boot loader
on running upgrade utility it comes back with error 260 connection error saying cannot find device (i am stuck in bootloader)
any advices ??
please help !!!!
The fact that you can still enter the bootloader means that it is not bricked, so first advice would be, as is so well presented in the Hitchhicker's Guide to the Galaxy, "Don't Panic".
Enter bootloader without any SD Card or SIM left in the Athena.
Then, plug it to the USB port, and see if it goes from "serial" to "usb".
Then try to flash first the Black Dual PK ROM available on the forum (in the WM6 section), or an official ROM available from the Wiki, for instance.
hi
tried to flash it with both and came out with same error
260 connection cant find device
and i cant even see any changes in devicemanager but it dose goes serial to usb when i connect
and my pc is not detecting the device (just like that depressed robot from hich hikers guide to galaxy )
Do you have Windows XP or Vista ?
Ecraseur said:
Do you have Windows XP or Vista ?
Click to expand...
Click to collapse
xp (pc i am trying to upgrade i also have vista on other pc which i havent tried yet should i try that ?)
nop no luck in vista ether same error still no connection
both pc have netframework 2
activesync in xp and mobiledevice center in vista
but after connecting device nothing happens in device manager there is no new device
(could it be beacouse of faulty cable? )\\(noi have tryed 2 different cable )
is it worth getting cradle ??
No no. I think the problem comes from the flash utility that requires that the Athena be detected prior to flashing.
I know that with the Universal, some flashing utilities could force flashing when connecting the device already in bootloader mode...
So there must be an easy way to bypass the device detection and go on with the flash process. I'll try and find out, and maybe one of the gurus will cruise by and find it for ya in the meantime.
In the meantime, don't freak out and be patient. Your Athena's not bricked, probably the ROM that's screwed up. We only need to find a way to do that exclusively from the bootloader (chich I know is possible, that's the whole point of the bootloader ).
vijay5264 said:
nop no luck in vista ether same error still no connection
both pc have netframework 2
activesync in xp and mobiledevice center in vista
but after connecting device nothing happens in device manager there is no new device
(could it be beacouse of faulty cable? )\\(noi have tryed 2 different cable )
is it worth getting cradle ??
Click to expand...
Click to collapse
Hi
Try a hard reset ( Volume down+reset) and then get into the boot loader(Camera+reset~10seconds) then flash the PK dual rom. Don't panic, Your athena is hard spl patched therefore not bricked. If that not works down load the exact official rom for your device flash that then flash the PK dual rom. try Redownload the rom again.
Good luck
HeartOfDarkness said:
No no. I think the problem comes from the flash utility that requires that the Athena be detected prior to flashing.
I know that with the Universal, some flashing utilities could force flashing when connecting the device already in bootloader mode...
So there must be an easy way to bypass the device detection and go on with the flash process. I'll try and find out, and maybe one of the gurus will cruise by and find it for ya in the meantime.
In the meantime, don't freak out and be patient. Your Athena's not bricked, probably the ROM that's screwed up. We only need to find a way to do that exclusively from the bootloader (chich I know is possible, that's the whole point of the bootloader ).
Click to expand...
Click to collapse
hi
thankes i think u understood the problem it is utility which fails before even starting beacouse of no connection see if u can find any thing
and yes i tryed hard reset and then tryed to flash with project black rom and i have downloaded latest t mobile rom from oficeal website but as i said before it fails with connection error it starts up and box says ''verifying information on your pda fone please wait'' and minut later it comes up with error 260 connection error '' please check following
1 your pdafone is connected to usb cable /cradle
2 usb cable connected to pc
(wich is basicly same if you try to nrun upgrade with out connectind pda )
(and yes i have tryed it with 2 different cables and it dose change from serial to usb)
some ting intrestin i foun in orignal update utility faq
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
is possible because device is in bootloader ?
or am i doing some ting wrong?
Reboot your PC, make sure you are not using a USB hub, try it with each USB port on the PC.
Pantaloonie said:
Reboot your PC, make sure you are not using a USB hub, try it with each USB port on the PC.
Click to expand...
Click to collapse
good idea but dident work after 4 on board ports and 2 hub ports no joy at all
by looks of it upgrade utility is trying to read info from my device and could be failing for 2 reasons
1 it is not detecting device
2 info in pda is corrupted and could not get any info from device
well thats my theory but not really sure any suggestions??
Is your PC running XP or Vista? I got the impression reading the post that XP machine works better in unlocking. I think the info was posted by Olipro himself if my memory is right.
eaglesteve said:
Is your PC running XP or Vista? I got the impression reading the post that XP machine works better in unlocking. I think the info was posted by Olipro himself if my memory is right.
Click to expand...
Click to collapse
it is running xp the one i am working on now (i do have 2nd pc running vista 64 bit )
but i am doing unlocking in xp
all i want to find out is dose device needs any drivers or dose it gets detected if device is in bootloader ?
if thats the the case i dont see any new devices in xp devicemanager
No no, it doesn't. Couldn't find it for Athena, but don't have much time lately, alas.
Maybe you should PM one of the gurus asking how to flash a ROM straight from bootloader without having the device detected by WinXP. I believe there's a small, easy manipulation to make, but can't remember it for the life of me. :-S
HeartOfDarkness said:
No no, it doesn't. Couldn't find it for Athena, but don't have much time lately, alas.
Maybe you should PM one of the gurus asking how to flash a ROM straight from bootloader without having the device detected by WinXP. I believe there's a small, easy manipulation to make, but can't remember it for the life of me. :-S
Click to expand...
Click to collapse
i found this in wiki and first three posts are empty but followed the procedure and downloaded all three roms and still no joy error
''Problems using the Athena Unlocker - the Black Screen of Death
Using The Athena Unlocker tool (developed by Olipro) is a 3-stage process. Most users get through the first stage but as they start stage 2, get a black screen where their device becomes unresponsive and so cannot proceed with the unlocking. See these posts
http://forum.xda-developers.com/show...&postcount=169 or http://forum.xda-developers.com/show...&postcount=176 or http://forum.xda-developers.com/show...&postcount=226
It is always recommended that you first take out your MiniSD card. You can then follow the instructions below.
* Get one of the ROMs in this link and extract it http://forum.xda-developers.com/showthread.php?t=314672
* Get your device into bootloader (the three-colour screen; You can get there by pressing the Camera key + Volume key + Soft Reset at the same time)
* Connect your device to your PC (even if the PC shows no sign of recognising it, it does) and the SERIAL shown on the screen of your device will change to USB)
* Hit the ROM Upgrade Utility and upgrade your device.
* Once the upgrade is completed, configure your device (Calibrate screen, set time zone, etc).
* Now continue with the Unlocker, to the end.
It is important to complete the unlocker to the end or else you will miss out on flashing your radio, with a common symptom of your gps not working.
Good Luck and enjoy your improved device!
''
now i am still stuck will it make any difference if i try it in different xp pc other then the one i started the process ?(and screwed it up)
Please ensure all software firewall or IP filtering apps are turned off then reboot the PC. After rebooting, confirm the apps are not running and blocking anything. If you are unsure, then try it from a freshly installed XP.
Put the device in Bootloader mode and try it again.
lpsi2000 said:
Please ensure all software firewall or IP filtering apps are turned off then reboot the PC. After rebooting, confirm the apps are not running and blocking anything. If you are unsure, then try it from a freshly installed XP.
Put the device in Bootloader mode and try it again.
Click to expand...
Click to collapse
good idea
i have already tryed with firewalls and virus protection off but doing it in fresh xp might just work small question do i need to install active sync or is it not needed (any way ill try both first without and then with )
ill report back in about 3 hours (i know i am sad and havent got a life but its worth a try )
Yes, the wiki confirms what I thought but didn't voice out loud as yet (I was sure about it for the Universal, but not for the Athena): the upgrade utility doesn't *require* that it be Activesynced. That's, as I'd said, te whole point of the bootloader.
If you still have problems uploading the new ROM to your Athena after following the wiki thing, then it *does* mean that there is some external factor playing dirty, so the firewall to check (and some anti-virus software also scan network connections) indeed is a good idea.
Keep us posted, and I'm keeping my fingers crossed.
i posted this in the hard spl sticky thread but got no responses so i thought i would create a new thread.
Been reading through the forums for 3 hrs. i read the entire unlocker thread. cant find any info on this.
i own a htc x7501. i performed a hard reset, connected device to windows xp pc. synced with active sync 4.5. everything connected, i can browse files on the device. device definitely connected.
i took out the sd card, sim card remains. windows xp computer has all updates and service packs and antivirus disabled.
i ran athena unlocker version 3, downloaded today from unlocker thread. click step 1, it loads the RUU, i follow the steps, says upgrading from image version 2.19 to Hard-spl. i click next, says now upgrading and shows the status bar at 0%. after about 10 - 15 secs, windows pops up on computer screen and says "error 202: connection. please make sure your device is connected to your computer, check the cable, blah blah"
tried mulitple times, each time restarting pc and device. device still works as before, nothing changed at all.
any ideas?
come on guys, anything?
someone has to have a clue
what do you see when you get into the bootloader screen. Get into the boot loader by pressing down and holding on the camera button while sticking your stylus into the reset hole for a good 5 seconds.
it says:
athe100
ipl-v2.02
ATHE100
SPL-v1.10.0000
i followed the tutorial video in the unlocker thread, and on the video when the guy done step 1, it asks to install something on the phone, enablerapi.cab by the look of the video. i never get this, just says "connection error"
thx for your reply Eaglesteve, appreciate it
This mean your flashing was not successful yet.
I think you should first reflash your original ROM back to restore it back to working condition again first. Then repeat the step and keep the finger cross this time.
You do this by first going into the boot loader mode, then connect up the usb cable, and run the RUU (RomUpdateUtility) program of your ORIGINAL stock ROM.
Edit: Sorry, did you say that your device is actually still working? Then you don't need to reflash the original ROM.
Do you have .net Framework 2.0 installed with the services packs on your XP machine?
i think there might be a misunderstanding.
the rom is untouched. i cant complete anything. here is what i did from the beginning. new stock phone. performed hard reset. went through customisations as per normal. stock rom installed.
plugged device into pc running xp. active sync, connected and synced. ran unlocker tool version 3. press step one, unlocker minimises and open RUU. says checking device for version details, finds them, says image version 2.19. great, that shows it can communicate with device. i click next a couple times, eventually it gets to the status screen that shows percentage of flashing and a warning at the bottom that says, "be aware this might take 10 mins" or something like that. about 15 secs, nothing happens, then new window appears saying "error 202: connection, please ensure device is connected, check cable/cradle"
i click ok, RUU exits, unlocker reappears, and says step 1 complete.
make sense?
PashaK said:
i think there might be a misunderstanding.
the rom is untouched. i cant complete anything. here is what i did from the beginning. new stock phone. performed hard reset. went through customisations as per normal. stock rom installed.
plugged device into pc running xp. active sync, connected and synced. ran unlocker tool version 3. press step one, unlocker minimises and open RUU. says checking device for version details, finds them, says image version 2.19. great, that shows it can communicate with device. i click next a couple times, eventually it gets to the status screen that shows percentage of flashing and a warning at the bottom that says, "be aware this might take 10 mins" or something like that. about 15 secs, nothing happens, then new window appears saying "error 202: connection, please ensure device is connected, check cable/cradle"
i click ok, RUU exits, unlocker reappears, and says step 1 complete.
make sense?
Click to expand...
Click to collapse
Yes, indeed I misunderstood. Please see my revised post above.
yes .net framework 2 and 3 installed plus all service packs.
PashaK said:
yes .net framework 2 and 3 installed plus all service packs.
Click to expand...
Click to collapse
I wish I could be of more assistance, but I'm not sure why your connection does not stay firm throughout the process. Perhaps you could PM Olipro for assistance?
yeah i might have to. i was thinking about trying it from a server 2003 machine, in case it is something wrong with my xp pc. i also have a vista pc but i dont trust vista enought to do it.
you think server 2003 would be ok to do it from?
thanx for helping a fellow aussie out
PashaK said:
yeah i might have to. i was thinking about trying it from a server 2003 machine, in case it is something wrong with my xp pc. i also have a vista pc but i dont trust vista enought to do it.
you think server 2003 would be ok to do it from?
thanx for helping a fellow aussie out
Click to expand...
Click to collapse
No worries mate.
Perpahs you want to try a newly installed XP machine? You know what it is with older machine. After a while all kinds of stuff goes in to corrupt it. I vaguely remember a post where someone who did not succeed with an XP machine later got it workign with another XP machine.
I think it is not possible for Olipro to anticipate all the possible conditions which might affect the program.
So, give it another go with a different, cleaner XP machine.
Good luck.
thanx, i might try that tomorrow if olipro has no other ideas. this is a newly formatted pc. i format quite regularly, being a network administrator, i keep all my pc's very clean.
i will report back my results when i get this solved.
thanx again
PashaK said:
thanx, i might try that tomorrow if olipro has no other ideas. this is a newly formatted pc. i format quite regularly, being a network administrator, i keep all my pc's very clean.
i will report back my results when i get this solved.
thanx again
Click to expand...
Click to collapse
Your cable has no problem I assume? Do you have problem doing ActiveSync in normal use?
the cable is the same one i got with the device. hardly used. everything in activesync works fine. i can browse files. install programs, everything works as it should, except the unlocker
I had a very similar problem when i tried to make the WM6 upgrade...
The reason for the connection failure:i had my Ameo connected via an external USB-hub.Which worked perfectly when i just wanted to synchronise or browse files...but when i wanted to make the upgrade i got the same connection error at exactly the same point.
Sticking the cable DIRECTLY into one of the PCs USB-ports solved the problem.
Ok,last night i tried the unlocker myself.
I put the cable directly into one of the ports of my PC...and got that connection error!
Tried to reinstall WM6-which,as mentioned in my post above had worked...still connection error.
Disconnectedt the USB from my pc,and simply put it back in a different port.
WM6 installation worked,and unlocking the phone afterwards worked,too.
No connectin errors anymore.
So this definitely is some sort of USB connection error.
Just try different ports.
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
okeven said:
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
Click to expand...
Click to collapse
Try a different USB port first, fire the device into bootloader mode manually and see if the device is detected by windows as "HTC USB SYNC"........use a hardwired port NOT a USB Hub aswell.
I tried a different USB port. It is not being plugged in to an external USB hub. I went into the bootloader screen and my computer makes the sound that a USB device was plugged in and it does show in the device manager as "HTC USB SYNC". What now?
Now try to do an update, Sounds like a problem associated with the connection of the device to your machine...usually caused by messed up USB drivers or a conflicting program.
Just tried. Same error again. Tried restarting the computer and tried it again. No dice.
this is the answer
hey man, how u doing. I was getting those errors too, I actually have a Tilt, I got error 200, and 260 trying to change my rom, I was about to give up. then I tried something I didn't think of, I updated my device center software from Microsoft and then miraculously everything worked after that. If you have XP update your Active sync software to the latest one and everything should work after that. Hope this helps.
and one more thing, make sure you install HardSPL v1 (or later when its released) first before trying to install the ROM.
I don't think anything is wrong with your usb drivers
I had actually checked to make sure I had the most recent version already and I do. I cannot install HardSPL either, since it gives me error 260 there also.
Error 260 is an open port error... I believe you have already tried resetting your device, but have you rebooted your pc prior to this procedure... I am grasping at straws for you, since you said you have tried soft resetting to no avail... I believe MrVanx stated to put the phone in bootloader mode and try to run the update utility that way... It works for me...
Can you try this on a different pc? If so, does it work? I have a post on another forum that you might find interesting... I did not compile it on my own, but cannot recall where I got it from... anyway, the link is HERE...
Hope this helps you out...
I have restarted the computer multiple times. I just tried it on my laptop and that did not work. I can boot the phone to the bootloader, but how do I install it from there?
That should be the easiest part... once you have it in bootloader mode, connect it via usb and then launch the update utility...
I get error 260 doing that also. argh!!!
i know how u feel
i had your problem several times. you want to know how i fixed it?
i didn't...
first i tried everything you and the guys mentioned and... nothing. then it worked the next day by itself.
the second time i couldn't connect i was really mad because the errors came sporadically. i tried installing AS, uninstalling, hard resetting the device, changing usb ports, anything logical and illogical and it worked on changing usb ports (but not on the first change).
now i'm at my girlfriends, had no problems until i saw farias new rom and wanted to flash it. guess what connection error
p.s. i've read trough and trough, but i've found no solution
what version and OS?
okeven said:
I get error 260 doing that also. argh!!!
Click to expand...
Click to collapse
yeah, I thought u would dget that again. i don't believe the error is originating from your phone, its more from the computer. what operating system are you using and whats the version number for activeSync or MS Device Center you are using?
I had that error on my home pc and on my girlfriend's laptop prior to updating my device center software. My pc is running Vista ultimate x64 and my girlfriend's laptop is running Vista Home Premium x32. I'm on her laptop right now, the version of device center is 6.1.6965. when I get home I will see which version is on my computer, I remember seeing "beta" on the one I got at home, lol, I didn't know Microsoft sent out beta software through its msupdate.
okeven, someone replied with good suggestions to the thread that u accidentally started over in the kaiser forum. you might want to check that out
I have version 6.1.6965 also. It does not say anything about it being a beta version, but with Microsoft, isn't everything in beta stage?
I did try the "official wm6 AT&T" version. Upgraded just fine. Tried upgrading to another one. Failed with error 260. What is different with the official upgrade program compared to the unofficial ones. THAT is the problem.
help
hi guys,
i have the same problem always the code 260, and also, my tytn's screen become within light, and without any boot number, ni radio, anything appears, please help me,,
thanks,
Finnaly
Hi guys
I also have the 260 problem but i resolved it:
1º- connect pda and make a active sync connection
2º run RUU
3º the 3-color screen will appear and update will stop with the 260 message error. be sure you can install the "qualcomm cdma technologies msm driver" at this moment, by an internet connection.
4º after the driver is installed, the word "USB" will appear in the white strip of the 3 color screen;
5º run RUU again and that´s all!
I´ve tried it in windows 7 ultimate 32-bit
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
lxlx said:
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
Click to expand...
Click to collapse
Hermes use HERMIMG.nbh ... kovsimg.nbh is for Xperia X1 ..
Hi gys, I think that this is my first post, but I want to share some solution for with you. The most important think with "connection" errors is to have HSPL installed correctly. I was trying to install on my HD2 universal ones, like Hard spl v7 and 9, but problems occured. So after trying everything, I found HSPL (on this forum) just for HD2. After that, everything wass like a charm