Hi,
I managed to blow away the ROM while trying to upgrade and now can not connect to the bootloader to download a new rom.
Here is my sorry story. I used the OS image tool to backup the ROM to SD and then started downloading the developers edition ROM to the device. During the process I lost the connection and could not reconnect again so I tried restarting the device. Now it has no ROM. So, I followed the instructions to get to the bootloader to restore the ROM from the SD card. No luck. The Bootloader is V5.22 so from what I read it means that the SD card had to be "keyed" to use as a backup. Next I tried the instructions to get to USB Flash mode. The screen says "connect USB cable now" but I can not get ActiveSync to connect so I can download a new ROM.
Any suggestions?
Ok I might be wrong here, but i don't think you need an active sync connection do upgrade the ROM do you?? Thought the upgrade tool kills the active sync connection??
Cannot connect to XDA
When I run the OsImageTool it comes back with an error "please connect your XDA to activesync. Whether this means the Active Sync program or just to put the XDA in the cradle I can't be sure. But either way I have the XDA in the cradle and Active Sync running, but it will not connect when I try to run the OsImageTool.
Your XDA is dead!
you could send it to me to let XDA life back!
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.
Hey everybody,
I'm new to this flashing as well...
I have a Tmobile US HTC HD2...
I installed the HSPL3 after getting the Windows Mobile Device Center...
It was installed successfully, but after that whenever I connect my HTC to my PC, I can hear the ding but my PC is not recognizing my device and there is no connected icon on the HTC as well.
I tried all the USB ports and nothing worked. Without connecting my device to the PC you know you can't flash any roms as well...
Any help please...
sureshkgopalan said:
Hey everybody,
I'm new to this flashing as well...
I have a Tmobile US HTC HD2...
I installed the HSPL3 after getting the Windows Mobile Device Center...
It was installed successfully, but after that whenever I connect my HTC to my PC, I can hear the ding but my PC is not recognizing my device and there is no connected icon on the HTC as well.
I tried all the USB ports and nothing worked. Without connecting my device to the PC you know you can't flash any roms as well...
Any help please...
Click to expand...
Click to collapse
Are you trying to do this while your screen has the three colors?
If so....does it say USB at the bottom or serial?
not while bootlegger mode. I used that for installing the hspl3.
my pc didn't discover the connected device and there was no connected symbol (which you get on your hd2 on the top right side, next to 3G n/w symbol).
when I connect, it shows that as a mass storage device on my pc and the safely remove hardware sign shows up.
I hope this explains my problem.
settings menu all settings connections usb to pc tick active sync untick 'faster data' reboot the pc, reboot the phone. Should be fine.
Thanks Sam, it worked. Unticking the 'faster data', did the trick...
Thanks again.
I just got my phone back from repair and I'm trying to install HardSPL. The installer for some reason isn't able to tell that the phone is connected and even though the phone says "USB" in the bootloader, HSPL doesn't see it.
HSPL is just stuck saying "Waiting for USB..."
Any hints? I'm using windows 7
pkchips said:
I just got my phone back from repair and I'm trying to install HardSPL. The installer for some reason isn't able to tell that the phone is connected and even though the phone says "USB" in the bootloader, HSPL doesn't see it.
HSPL is just stuck saying "Waiting for USB..."
Any hints? I'm using windows 7
Click to expand...
Click to collapse
make sure u are conected to the internet for driver update
chek your cable ))
make sure that your usb connection is set to active sync (on your device)
I had already tried all of the above and it didn't work.
(with regards to the activesync thing, the HSPL installer automatically took my phone into bootloader mode. So I don't think there was any issue there)
In the end, I just went and used a different computer.
I have a laptop, and i had the same problem. My solution was to connect my phone through another usb port on my computer (main usb port) try it with the other usb ports.
Hope this helped you
sahus said:
I have a laptop, and i had the same problem. My solution was to connect my phone through another usb port on my computer (main usb port) try it with the other usb ports.
Hope this helped you
Click to expand...
Click to collapse
Hmmm interesting....
However, the same USB port on my computer works for flashing ROMs and Radios so I doubt that is the problem. In fact, I used the same USB port for flashing the NRG rom straight after I hard spl'd my phone!
My solution was to just use another computer.
Thanks for your response. Hopefully this thread might help some guy in the future in a similar situation.
However, the same USB port on my computer works for flashing ROMs and Radios so I doubt that is the problem. In fact, I used the same USB port for flashing the NRG rom straight after I hard spl'd my phone!
,
Click to expand...
Click to collapse
actually just cos a port works for flashing means nothing. you can flash and sync through case mounted ports and usb hubs, but hspl won't work on those same ports.
so as stated windows detects one att htc one in fastboot bootloader but will not detect my other one . windows makes a noise like it knows its being plugged in and it charges but it will not accept any commands on this other htc one im so confused at what the problem could be ? i have tried every htc cord and nexus 7 cord i have all work on one of them but none on the other ? could my usb port be broke and still charge the phone ? any advice or help would be greatly appreciated i usually know what im doing with htc phones so i will prob understand any ideas you think i should try in device manager it recognizes the one that works correctly but the problem ONE has yellow triangle and says
Unknown USB Device (Device Descriptor Request Failed) thats what it says in device manager for broken ONE. if you need more info let me know and please please please let me know if you know how to fix this on windows 8.1 i dont know why it recognizes one but not the other
Update after digging around in wondows device manager
windows has stopped this device because it has reported problems code 43 which is a hardware failure
so i guess i cant fix that huh makes no sense if i can boot recovery bootloader and rom
windows doesnt detect and adb doesnt detect
ac3kill said:
so as stated windows detects one att htc one in fastboot bootloader but will not detect my other one . windows makes a noise like it knows its being plugged in and it charges but it will not accept any commands on this other htc one im so confused at what the problem could be ? i have tried every htc cord and nexus 7 cord i have all work on one of them but none on the other ? could my usb port be broke and still charge the phone ? any advice or help would be greatly appreciated i usually know what im doing with htc phones so i will prob understand any ideas you think i should try in device manager it recognizes the one that works correctly but the problem ONE has yellow triangle and says
Unknown USB Device (Device Descriptor Request Failed) thats what it says in device manager for broken ONE. if you need more info let me know and please please please let me know if you know how to fix this on windows 8.1 i dont know why it recognizes one but not the other
Update after digging around in wondows device manager
windows has stopped this device because it has reported problems code 43 which is a hardware failure
so i guess i cant fix that huh makes no sense if i can boot recovery bootloader and rom
windows doesnt detect and adb doesnt detect
Click to expand...
Click to collapse
you have different hboot versions
here's the fix I used to make hboot >1.55 work on windows 8.1
http://forum.xda-developers.com/showthread.php?p=49131915
use the old dirty method it worked fine
http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072