I used the search function but it still isnt working for me. I picked up a locked 8525 from a guy off craigslist. Its stuck on the tri-color bootscreen. He said it worked fine until he took his sim card out and reinserted it today. he said he didnt flash the ROM or anything. I tried the wiki suggested fixes to no avail. I installed active sync and unchecked the allow usb connections and tried to reboot the phone. Nothing. It said it couldnt find my phone. Pulled the battery, reset, nothing. Please help. He gave it to me for $50 because it was stuck.
HERM100
IPL-1.04
HERM100
SPL-2.10.Olipro
mark1914 said:
I used the search function but it still isnt working for me. I picked up a locked 8525 from a guy off craigslist. Its stuck on the tri-color bootscreen. He said it worked fine until he took his sim card out and reinserted it today. he said he didnt flash the ROM or anything. I tried the wiki suggested fixes to no avail. I installed active sync and unchecked the allow usb connections and tried to reboot the phone. Nothing. It said it couldnt find my phone. Pulled the battery, reset, nothing. Please help. He gave it to me for $50 because it was stuck.
HERM100
IPL-1.04
HERM100
SPL-2.10.Olipro
Click to expand...
Click to collapse
Downloaded and tried to flash your stock rom? Or via the SD card method, can you get it into the bootloader?
Thank you for replying. I downloaded the WM6 upgrade directly from the HTC site. After I downloaded it to my computer and plugged in the phone to run the program it got to a point then said "ERROR, replace installer" something along those words. It appeared to me that the WM6 version from HTC was outdated or too old to be loaded. Its stuck on the 3 color screen so I assume thats the bootloader screen. I am going to try it again on a different computer at work this morning.
Downloaded the ROM from HTC. Plugged in the phone and got ERROR 260. Unplugged it and changed to another USB and same thing. Its as if the computer doesnt recognize the phone at all.
Nothing. Computer doesnt recognize the phone. Should I try downloading a ROM to a micro SD card then inserting it? Will it load on its own when inserted?
Whats the SPL on the bootloader (tri-colour screen)?
You need to have Hard SPL on your phone before you try to upgrade the os using the sd card method. If its Hard SPLed then the SPL should say SPL : 2.10 olipro.
Cheers...
ultramag69 said:
Whats the SPL on the bootloader (tri-colour screen)?
You need to have Hard SPL on your phone before you try to upgrade the os using the sd card method. If its Hard SPLed then the SPL should say SPL : 2.10 olipro.
Cheers...
Click to expand...
Click to collapse
Thats what it says SPL-2.10.Olipro. I tried the sd card method an it would say Update completed then when I did a softreset it jumped back to the bootloader screen. When I try the USB method, the computer cant connect to the device. Its not the computer because my colleague connected his iphone to the same port and it works.
i have just got one of these phones as a update from my poor poor xda2i.. as i wanted wm6
i had a prob with the pc not connecting, i was trying to connect to it using a powered usb hub, u have to use a usb port directly connected to your pc, with no hubs or extenders, this worked 100% for me, and you are using a pc running XP not vista? as the flashing software was only designed for 2k/xp, this was the same with my old xda2i
and pls dont mention *spit* the iphone *spit* in a xda forum!!! LOL
ha ha, I wont mention the "other" phone anymore. How do I tell if its a direct port and not a powered one? Yes, I'm using XP on both my computers.
mark1914 said:
Thats what it says SPL-2.10.Olipro. I tried the sd card method an it would say Update completed then when I did a softreset it jumped back to the bootloader screen. When I try the USB method, the computer cant connect to the device. Its not the computer because my colleague connected his iphone to the same port and it works.
Click to expand...
Click to collapse
OK, best thing to try is to see if theres bad blocks on the device.
Leave the device in bootloader, run mtty.exe and connect to USB.
use the command "info 8" to see if there are bad blocks....paste the output here for us.
downloaded mtty.exe and I dont have the USB port in the pulldown menu. Just com1 com4 ports
mrvanx said:
OK, best thing to try is to see if theres bad blocks on the device.
Leave the device in bootloader, run mtty.exe and connect to USB.
use the command "info 8" to see if there are bad blocks....paste the output here for us.
Click to expand...
Click to collapse
reloaded mtty.exe and went down to USB. Hit OK and a pop up said USB port can not open
I will try to find a picture of the screen its stuck on
This what my screen looks like. This is how I got the phone as well. It will flash a ROM but when I soft reset it, it goes back to this screen. I followed the WIKI guide for flashing via sdCard was great! I followed the instructions perfectly. I soft reset by pushing in the button on the bottom of the phone and thats it. Nothing else. What am I doing wrong? Also, mtty.exe says it cant open USB port. Do I leave those other settings alone?
mark1914 said:
This what my screen looks like. This is how I got the phone as well. It will flash a ROM but when I soft reset it, it goes back to this screen. I followed the WIKI guide for flashing via sdCard was great! I followed the instructions perfectly. I soft reset by pushing in the button on the bottom of the phone and thats it. Nothing else. What am I doing wrong? Also, mtty.exe says it cant open USB port. Do I leave those other settings alone?
Click to expand...
Click to collapse
hmm looks strangely like the image from my guide site??
tbh if you cant access the bootloader with mtty we cant help you....you most likely have bad blocks which is causing it not to boot.
mark1914 said:
reloaded mtty.exe and went down to USB. Hit OK and a pop up said USB port can not open
Click to expand...
Click to collapse
I bet you haven't disabled USB port on ActiveSync....
CRCinAU said:
I bet you haven't disabled USB port on ActiveSync....
Click to expand...
Click to collapse
Yes I did lol. I think you're right bad blocks and its no good. Could the usb plug on the phone be messed up?
mrvanx said:
hmm looks strangely like the image from my guide site??
tbh if you cant access the bootloader with mtty we cant help you....you most likely have bad blocks which is causing it not to boot.
Click to expand...
Click to collapse
ha ha yep got it from your site. Whats the newest version of mtty? I downloaded the first version I think.
if you cannot get your phone working and your willing to sell it i would gladly take it off ya hands, i bought a secondhand m3100 ad it looks like its been thought the wars, i wana ew case and screen, so if ya interested and can take a paypal payment for the right price of cause.
but i hope you get it up and running, as i love this phone
skeeve666 said:
if you cannot get your phone working and your willing to sell it i would gladly take it off ya hands, i bought a secondhand m3100 ad it looks like its been thought the wars, i wana ew case and screen, so if ya interested and can take a paypal payment for the right price of cause.
but i hope you get it up and running, as i love this phone
Click to expand...
Click to collapse
I may have to sell it for parts. Its super bricked. I have loaded 3 different ROMS, OS onlys, on sdCards to no avail. I tried 4 different computers and its still stuck in bootloader. I am about to run it over with my car
Related
well, i can't figure out quite what has happened.
i was attempting to install hard SPL v7 prior to upgrading to the latest LVSW 0423 ROM.
activesync was connected, i ran RUUWrapper.exe and it dropped the 8525 into bootloader mode as it usually does. for some reason, the RUU app was unable to verify the info on the phone, so upgrade failed and it quit. i reset the 8525, and it booted normally.
well...now USB appears to be dead. forcing the device into bootloader shows
Code:
HERM100
IPL-1.01
HERM100
SPL-1.30.Olipro
Serial
connecting the USB cable does nothing - the bootloader continues to show "Serial". i can reboot and all is fine, radio works...nothing else is wrong except there is no comm via USB. the device charges via USB just fine, whether the 8525 is powered on or off.
nothing in the hermes bricked wiki page matched up, as i have a working OS and a working radio...but i saw in another post that being stuck with "Serial" is evidence of a corrupt bootloader.
ideas? thanks!
Try running the RUU again. If it is still dead then try flashing via SD card.
jamiefiedler said:
well, i can't figure out quite what has happened.
i was attempting to install hard SPL v7 prior to upgrading to the latest LVSW 0423 ROM.
activesync was connected, i ran RUUWrapper.exe and it dropped the 8525 into bootloader mode as it usually does. for some reason, the RUU app was unable to verify the info on the phone, so upgrade failed and it quit. i reset the 8525, and it booted normally.
well...now USB appears to be dead. forcing the device into bootloader shows
Code:
HERM100
IPL-1.01
HERM100
SPL-1.30.Olipro
Serial
connecting the USB cable does nothing - the bootloader continues to show "Serial". i can reboot and all is fine, radio works...nothing else is wrong except there is no comm via USB. the device charges via USB just fine, whether the 8525 is powered on or off.
nothing in the hermes bricked wiki page matched up, as i have a working OS and a working radio...but i saw in another post that being stuck with "Serial" is evidence of a corrupt bootloader.
ideas? thanks!
Click to expand...
Click to collapse
change your usb cable
stukes said:
Try running the RUU again. If it is still dead then try flashing via SD card.
Click to expand...
Click to collapse
i tried running the RUU again, but since hard SPL v7 (and most of the other RUU updates) seem to require a working activesync connection - which i can't get withoutout USB - i've had no luck.
flashing via SD card is a great idea - didn't even think of that, thank you. i'm not entirely sure which nbh would be appropriate to flash in this situation though - a complete OS/radio/BL package or attempt just the hard SPL nbh file again?
pof said:
change your usb cable
Click to expand...
Click to collapse
sorry...should have mentioned i tried another cable. both cables i tried are verified good with another device, and both cables are able to charge the 8525 when connected.
one more thing...if this is in fact a screwed up bootloader, is there anything valuable i can check/monitor/log while attempting to fix this to benefit anyone on the site?
Its up to you. I would try only the Bootloader because it will be superquick. Maybe you should check out the Flashing from SD Card Thread.
stukes said:
Its up to you. I would try only the Bootloader because it will be superquick. Maybe you should check out the Flashing from SD Card Thread.
Click to expand...
Click to collapse
ok, i'll give the straight bootloader a shot.
i was gonna follow the sd card flash instructions on the wiki...seemed simple enough. are you thinking of another thread i should check first?
thanks for your help, greatly appreciated. i'll post results of course.
jamiefiedler said:
flashing via SD card is a great idea - didn't even think of that, thank you. i'm not entirely sure which nbh would be appropriate to flash in this situation though - a complete OS/radio/BL package or attempt just the hard SPL nbh file again?
Click to expand...
Click to collapse
Flash HardSPL latest version first, otherwise you'll overwrite it because you have an old version which does not have SPL protection.
jamiefiedler said:
sorry...should have mentioned i tried another cable. both cables i tried are verified good with another device, and both cables are able to charge the 8525 when connected.
Click to expand...
Click to collapse
Try another usb port on computer then... or better, another computer and another usb cable.
jamiefiedler said:
one more thing...if this is in fact a screwed up bootloader, is there anything valuable i can check/monitor/log while attempting to fix this to benefit anyone on the site?
Click to expand...
Click to collapse
either your hermes usb connector is broken (which i doubt cos is able to charge) or you're using a bad cable, a bad usb port on computer, or an operating system without proper usb driver installation. For sure is not a problem of the SPL.
jamiefiedler said:
ok, i'll give the straight bootloader a shot.
i was gonna follow the sd card flash instructions on the wiki...seemed simple enough. are you thinking of another thread i should check first?
thanks for your help, greatly appreciated. i'll post results of course.
Click to expand...
Click to collapse
The WIKI is great. Pof gave you a nice sum'd up list.
ok...flashed hard SPL v7 successfully - now have SPL-2.10.Olipro but still no USB - pof was right (surprise surprise), it wasn't the bootloader.
i've now tried this using 3 different usb cables with 2 different USB ports on each of 2 different XP boxes. activesync is unresponsive on both (i've used activesync 4.5 successfully on both in the past) and when watching in bootloader mode then 8525 continues to show "Serial" in all cases.
maybe just one of the data pins of the mini-USB jack is damaged? intact power pins would still allow it to charge even if a data pin was bad.
unless anyone has another suggestion, i'm going to assume it needs to be rolled back to the cingular ROM and sent off to HTC for (attempted) warranty repair...hopefully nobody will notice anything SPL/CID related.
Bummer man. Try yanking the battery out while it is on and let it sit with it out for a while. Then roll back to your original ROM. Sucks if it where a bad pin.
This is a stretch, but anytime I have hardware connection issues (hard drive, flash drives, etc) I put them in the freezer for 10 mins. If it works, at least you know its the hardware.
peezy said:
This is a stretch, but anytime I have hardware connection issues (hard drive, flash drives, etc) I put them in the freezer for 10 mins. If it works, at least you know its the hardware.
Click to expand...
Click to collapse
LOL. I saw this somewhere before. Now for the more serious thought effects of extreme cold.
Moisture
Metals Expand and Contract
i popped the back off the 8525 and took a close look at the mini USB jack's pins, expecting to see evidence of a damaged pin (or more than one). well, no damaged pins - but i did find what looked to be a tiny sliver of metal that had worked it's way down (or in from outside) and was lodged between a couple of the pins. i used an x-acto knife to gently scrape between the pins as they traveled down to the main board, making sure not to damage any of the pins. went through all of them just in case, then closed it back up.
USB = working. problem solved.
thanks guys, as always i really appreciate your help.
Outstanding!!!
Very Nice!
btw stukes I put my dead sd card in the freezer last night, and what do you know? It Works! I know its a bit of a black art but I have used it successfully more than once.
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
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.
im a tech for a sprint affiliate store and i have a customers mogul that she got into bootloader...normally what i would do in this situation is disable usb connection in AS...plug in the phone...wait for the drivers to install and use UNI_ExitBootloader.exe to get it out of bootloader...
but for some reason with this phone when i plug it up via usb...it still says serial, instead of switching to USB at the bottom and the program nor the computer can read the device
i have a test mogul here...and when i put it into bootloader...it says(rom 3.45 offical sprint windows 6.1)
"TITA100
SPL-2.07.0000
CPLD-9"
and it unlocks fine
the mogul that wont get out of bootloader says(rom 3.35 official sprint)
"TITA100
SPL-1.04.0000"
and thats it...
im stumped...
Run titan_exitbl instead of UNI. A quick forum search and you'll find it. See if that works for you.
ive tried that as well...the problem is when i connect the phone to the computer its supposed to go from serial mode to usb mode...and it doesnt...so the computer doesnt download the drivers and hence wont connect using either program...
ive scoured many forums for hours and have not been able to find a solution or even a description of my particular problem...
thank you for the suggestion but being im not a noob this doesnt seem like your regular search and find your answer type of problem
justincredible said:
ive tried that as well...the problem is when i connect the phone to the computer its supposed to go from serial mode to usb mode...and it doesnt...so the computer doesnt download the drivers and hence wont connect using either program...
ive scoured many forums for hours and have not been able to find a solution or even a description of my particular problem...
thank you for the suggestion but being im not a noob this doesnt seem like your regular search and find your answer type of problem
Click to expand...
Click to collapse
Run MTTY to exit BL.....
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
BTW the 2.07 is the re-locker from NO2chem....
and no dice on that solution as well...just reads com1 and com2 under ports where you are supposed to be able to select USB
This is kind of a stupid question to ask....but did you try enabling usb connections in activesync and connecting it?
yes i did...wouldnt connect...but it will connect on my broke mogul and the working mogul i own...
which bugs me because i still dont think its a physical issue(like a broken USB port) because the customer was having problems sending SMS called tech support and they tried some stuff with her over the phone and she got stuck in bootloader...
im assuming this is a lost cause...but i try to repair as many phones as i can instead of just tossing people reconditioned ones...even though my store technically isnt a repair center...
thanx again for everyones suggestions...
and if anyone else has a clue wtf is going on lol...
please feel free to let me know
Flash from SD?
Since it is possibly dead anyway, how about try flashing from SD card as it will exit bootloader and reboot as its last ac ??? Can not hurt any worse;-)
so i need to take the installer file...get the RUU_signed.nbh file extracted from the ROM...rename it to TITAIMG.nbh...format the SD card to fat32...pop that baby in and see what happens?
thanx for that suggestion i totally forgot about that...
well good idea but still no dice...
i installed th ROM via SD card...it worked!...
fixed the SPl and CPLD errors fixed...so i know the ROM got loaded correctly...
the test mogul and the broken one look exactly the same in bootloader...yet i STILL cant get my comp to see the device...its still stuck in serial mode and wont switch to USB mode and i cant get it out of bootloader
edit:
wait...i turned the phone off...plugged it up via usb...turned the phone on and the damn thing worked!
phone booted right up...which is weird because i turned it off and turned it back on after i reinstalled the ROM from the SD card...
thank you guys for all your help...
you just really educated about 30+ TSRs from sprint affiliate stores in illinois, indiana, michigan, iowa etc etc
What does it say in bootloader exactly??? List everything on the screen.... sounds like if it works with the phone plugged in via USB, that you have the wrong bootloader on it.... Does it boot up without being plugged in??
well looks like i gave out the props a lil too soon lol...
im back to square one...installed ROM from SD card...took battery off...put it back in...turned phone on....if its plugged up via USB it'll boot up...add the extra sprint crap on it...as soon i unplug it and restart it goes right back to bootloader...and my comp wont see it as a USB device yet and still it'll see 2 other moguls i have chillen around my house
TITA100
SPL-2.07.0000
CPLD-9
is what it says...
omg this is nuts lol
if i leave the mogul unplugged from the USB cable after reinstalling the ROM from the SD card it just goes right back to bootloader...
it wont take a charge...nix that it took 5 minutes b4 it would accept a charge...
theres definately something wrong with the USB port...has to be...
It sounds like you fixed the software issues but I agree there has to be something up with the USB
the thing that puzzles me is that the usb port doesnt appear to be damaged at all...its still attached to the board...none of the pins are bent or broken...theres no water damage...
im baffled
justincredible said:
well looks like i gave out the props a lil too soon lol...
im back to square one...installed ROM from SD card...took battery off...put it back in...turned phone on....if its plugged up via USB it'll boot up...add the extra sprint crap on it...as soon i unplug it and restart it goes right back to bootloader...and my comp wont see it as a USB device yet and still it'll see 2 other moguls i have chillen around my house
TITA100
SPL-2.07.0000
CPLD-9
is what it says...
Click to expand...
Click to collapse
1st, get some compressed air and blow out the USB port, and get a different cable.... try connecting it now - hopefully something was causing a bad connection....
In bootloader screen does it change from serial to USB on the phone screen when you plug it in?? If it does you can get the official Sprint update and run it while the phone is in bootloader, it should finish just fine..... try this and report back....
i tried compressed air...didnt change anything...the phone will charge but wont switch from serial to usb...its not the cable because i have a my working mogul and a test mogul here and both worked perfectly...
the phone will boot up and work if its usb port is in use(charging, syncing) but as soon as i disconnect the cable and restart for any reason it goes right back to bootloader...and it will not boot up at all if the usb port isnt in use...
like i said...this is easily the most retarded seemingly unfixable mogul break down ive ever seen...
its very interesting in a werid kinda dorky way...this mogul is impervious to traditional bootloader fixes lol
So try this, copy NueSPL to the SD card, and then boot the phone and copy it to the phone. Then run the nuespl so it upgrades the spl to nuespl 2.47. You already have the the 3.56 ROM and the 3.42 radio on it right???
Heres the link to nuespl nueSPL-2.47.rar
what radio version is installed?
reading your first post, SPL 1.x should not have been on the broken phone. I wonder if it failed during the 3.X ROM update. Maybe she tripped over the USB cable while flashing.. I've done it.
az ill go ahead and try that when i get the phone back...she didnt feel like waiting another day and i could def understand that...so when the exchange is done im going to bring it back home and play mogul dr...
and dcd she hasnt updated her ROM at all...it was the stock 3.35 rom that came preinstalled when she got it...and no diss to her but i know her and shes not that technically inclined...but ill note the radio and get back to you...
this is an issue resolution that could help a lot of people...
i appreciate all you guy's help and suggestions...