Related
Hi Guys!!
While trying to upgrade my phone, this is what happened:
STEP ONE: Super CID
The first time it went wrong cause the ACtiveSync was not on to complete the final stage of tis step. So, I never got the "Unlocker" Application on my phone in order to unlock the phone. (What happened is that I probably forgot to put on the password after rebooting, so the ActiveSync never recognised the phone.
So, I decided to restart the step and I completed it successfully!!
STEP TWO: Hard SPL
This step went perfect!!!
STEP THREE: RADIO ROM
After the phone booted from Step Two, my laptop does not recognize the phone anymore!!!! The battery charging sign only appear for a few seconds then I get a pop up saying "One of your USB devices attached to this computer has malfunctioned and Windows does not recognize it". This means that the ACtiveSync cannot run. I have tried this on my Laptop and my PC but same results.
My phone looks ok though, so what went wrong guys? What are my options here?
Thanks
Start here
http://forum.xda-developers.com/showthread.php?t=286755
This is the thread you should have initially posted to, FWIW.
Good luck,
-pvs
EliasMH said:
STEP THREE: RADIO ROM
After the phone booted from Step Two, my laptop does not recognize the phone anymore!!!! The battery charging sign only appear for a few seconds then I get a pop up saying "One of your USB devices attached to this computer has malfunctioned and Windows does not recognize it". This means that the ACtiveSync cannot run. I have tried this on my Laptop and my PC but same results.
My phone looks ok though, so what went wrong guys? What are my options here?
Thanks
Click to expand...
Click to collapse
Your phone is not bricked. Congratulations on successfully CID unlocking and installing Hard SPL. Most with issues don't at least do the Hard SPL before they get themselves into trouble.
What version of Activesync are you using? Do you have enable advanced network compatibility checked on the start->settings->connection->USB tab of your phone? If so uncheck it.
If you are on AS 4.2 I recommend upgrading to 4.5. Also unplug the phone from your computer and reboot both devices then try to reconnect.
This problem is actually quite common and easily worked around. It can be frustrating though.
All is GOOD!!!
Zzan said:
Your phone is not bricked. Congratulations on successfully CID unlocking and installing Hard SPL. Most with issues don't at least do the Hard SPL before they get themselves into trouble.
What version of Activesync are you using? Do you have enable advanced network compatibility checked on the start->settings->connection->USB tab of your phone? If so uncheck it.
If you are on AS 4.2 I recommend upgrading to 4.5. Also unplug the phone from your computer and reboot both devices then try to reconnect.
This problem is actually quite common and easily worked around. It can be frustrating though.
Click to expand...
Click to collapse
Thanks Man, I managed to succesfully upgrade it!!!
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 TRIED EVERYTHING. I have bootloader screen but when i connect through USB it just says that device not recognized and nothing would happen. I even took the battery out for 2 hours... put in another phone charged to maximum and still same problem. Please if anyone could help.. i love this phone cant let it die like that.
hey body, check if you have installed ActiveSync on your PC if u r using WinXP, or if u have installed Windows Mobile Device Center on your PC if u r using Win Vista.
If not then install it according to the OS of ur PC then try to connect ur phone to PC again.
Or you may try to use another USB data cable?
skywalkerr said:
hey body, check if you have installed ActiveSync on your PC if u r using WinXP, or if u have installed Windows Mobile Device Center on your PC if u r using Win Vista.
If not then install it according to the OS of ur PC then try to connect ur phone to PC again.
Or you may try to use another USB data cable?
Click to expand...
Click to collapse
Hey buddy.... i have active sync installed but because of rom update the phone is stuck in bootloader. I want to demote back to wm5 but the phone wont get detected when connected via usb. Windows just detects it as unknow device and i cant load the roms without getting it detected. Please help.... anyone.. dont wana lose this phone
duderootz said:
Hey buddy.... i have active sync installed but because of rom update the phone is stuck in bootloader. I want to demote back to wm5 but the phone wont get detected when connected via usb. Windows just detects it as unknow device and i cant load the roms without getting it detected. Please help.... anyone.. dont wana lose this phone
Click to expand...
Click to collapse
Go Bootloader Mode, HOW? read my thread (in my signature ) and flash for PVtemp.
Enjoy ~~~
dioxda2 said:
Go Bootloader Mode, HOW? read my thread (in my signature ) and flash for PVtemp.
Enjoy ~~~
Click to expand...
Click to collapse
already done that before a hundered times
suggestion..
what prophet do you use.. 818 pro?
try this
1. device is on..in bootloader screen..
2. connect your device with usb cable to pc/laptop
3. press the comm manager button + soft reset button + green button (phone call button ) all at same time for few second
4. if done successfully, you'll get into splash screen
5. then flash with wm 5 rom or flash with any wm 6 rom. ( last time, for me i use korand 1st edition wm 6 clean rom & my prophet is restore to normal again)
* if step 3 doesnt work, press the camera button instead of comm manager button..(camera + soft reset + green buttons)
one last thing. did you have hardSPL your device? if so, hope it works
duato said:
what prophet do you use.. 818 pro?
try this
1. device is on..in bootloader screen..
2. connect your device with usb cable to pc/laptop
3. press the comm manager button + soft reset button + green button (phone call button ) all at same time for few second
4. if done successfully, you'll get into splash screen
5. then flash with wm 5 rom or flash with any wm 6 rom. ( last time, for me i use korand 1st edition wm 6 clean rom & my prophet is restore to normal again)
* if step 3 doesnt work, press the camera button instead of comm manager button..(camera + soft reset + green buttons)
one last thing. did you have hardSPL your device? if so, hope it works
Click to expand...
Click to collapse
Nice try !!
My further advises:
1. Use another USB cable and must use the rear panel USB port of your PC.
2. Then go to bootloader ( follow my steps precisely in my post 1) and plug to PC, on the left bottom of your Prophet screen
you should see the word "USB" shows up within 2 seconds.
3. then flash PVtemp downgrade to WM5, never fail!!!!!
duderootz said:
I TRIED EVERYTHING. I have bootloader screen but when i connect through USB it just says that device not recognized and nothing would happen. I even took the battery out for 2 hours... put in another phone charged to maximum and still same problem. Please if anyone could help.. i love this phone cant let it die like that.
Click to expand...
Click to collapse
Do u use 4.5 version of active sync ?
To get to bootloader mode, push power button and plug the cable to the PDA.
Thank ya alll mates but none of the above worked.... BUT... this is odd... the desktop where I had the device connected to ...is in my office...and i was tryin to update all at my home machine and nothing was working... even though i use AS 4.5 and i regularly sync but when it came to upgrading my home machine didnt recognize the device when in bootloader.. but when i connected back in the office all went well... thx alot buds.. happy flashing
duderootz said:
Thank ya alll mates but none of the above worked.... BUT... this is odd... the desktop where I had the device connected to ...is in my office...and i was tryin to update all at my home machine and nothing was working... even though i use AS 4.5 and i regularly sync but when it came to upgrading my home machine didnt recognize the device when in bootloader.. but when i connected back in the office all went well... thx alot buds.. happy flashing
Click to expand...
Click to collapse
Can you figure out what were your problems?
In order to share to all people here who are trying to help you...
Please shows feedbacks.... thanks ! ^_^
dioxda2 said:
Can you figure out what were your problems?
In order to share to all people here who are trying to help you...
Please shows feedbacks.... thanks ! ^_^
Click to expand...
Click to collapse
My problem was that I had done the HardSpl on another machine(office) and i was loading the ROM from another machine(home). All of the processess listed above are true but you have to be careful if you hardSPL your device from one machine then dont disconnect it from USB because thats what gave me all the headache. And the battery level is also important I would recommend atleast 70% power before u do the ROM updates.
duderootz said:
Thank ya alll mates but none of the above worked.... BUT... this is odd... the desktop where I had the device connected to ...is in my office...and i was tryin to update all at my home machine and nothing was working... even though i use AS 4.5 and i regularly sync but when it came to upgrading my home machine didnt recognize the device when in bootloader.. but when i connected back in the office all went well... thx alot buds.. happy flashing
Click to expand...
Click to collapse
Why not try to remove the ActiveSync of your home pc and reinstall it?
well, i never done that before..
so i guess its better to run all the upgrade using only one pc we always use..
another case solve..
duderootz said:
My problem was that I had done the HardSpl on another machine(office) and i was loading the ROM from another machine(home). All of the processess listed above are true but you have to be careful if you hardSPL your device from one machine then dont disconnect it from USB because thats what gave me all the headache. And the battery level is also important I would recommend atleast 70% power before u do the ROM updates.
Click to expand...
Click to collapse
Sorry, but your conclusion doesn't make sense at all. HardSPL is installed on your Prophet and has nothing to do with your PC or the drivers installed on that machine.
@rondol1
quite agree with you..
maybe duderootz only explain for what he think cause it
i think this device is so delicate
depend on how old have we been use the device, models, conditions etc..
keep me wonders
duato said:
@rondol1
quite agree with you..
maybe duderootz only explain for what he think cause it
i think this device is so delicate
depend on how old have we been use the device, models, conditions etc..
keep me wonders
Click to expand...
Click to collapse
I agree with you that is why I took the trouble to rectify. it should be unfair to let other users wondering with misbelieves.
In this case it is assumable that his homePC lacks some USB-drivers that his officePC does have. A solution could be to install AS 4.5 again on the homePC. In my experience, ActiveSync is a tricky app, especially when it has been updated from an older version.
And connection through bootloader-mode uses other drivers then a "normal" ActiveSync connection. It sounds as if those "non-ActiveSync" USB drivers are missing.
This same issue causes the Vista connection problems.
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.