Hello, i'm trying to upgrade my device but facing a weird problem. The WMDC works fine and i can sync my device. When i run the RUU, it analyzes the rom and put the device in bootloader mode....
as soon as the device enters the bootloader, the usb loses the connection and says "cannot recognize the device" or "drivers not found" etc....and the RUU gives the error of "cannot connect to the device. make sure...."
I have tried this with the AthenaUnlocker as well as the AthenaWrapper. I'm currently on SPL 1.1 and want to upgrade to 1.2
Please help!
I have the same problem!
I want to install HSPL on my device. I cannot install this via SD Card so i tried it with USB. But after the bootloader the connenction was lost. Many times...
Can somebody tell me how to fix this problem?
Thanks
Edet: My device is a HTC HD2
This might not fit your problem, but ...
... try to connect your device to a PC/laptop with USB 1.1 - with my Ameo I have many "connection loss" problems with USB 2.0 speed, which occure only on heavy (data) load on syncing.
Disabling USB2.0 is possible on some machines within the BIOS.
If you got no PC/laptop with USB1.1 you can disable the USB 2.0 related driver in the Windows Device Manager (it works for me, in general). Therefor open the device manager and select the "View" menu -> devices by connection (or similar). Now search for the Athena entry attached to the listed USB hardware. Disable the "most-upper" USB controller the Athena is attached to.
OK, the last description might be confusing, but try.
Good luck (as this solution fits to your problem, as I am not sure)
What worked for me
junooni said:
Hello, i'm trying to upgrade my device but facing a weird problem. The WMDC works fine and i can sync my device. When i run the RUU, it analyzes the rom and put the device in bootloader mode....
as soon as the device enters the bootloader, the usb loses the connection and says "cannot recognize the device" or "drivers not found" etc....and the RUU gives the error of "cannot connect to the device. make sure...."
I have tried this with the AthenaUnlocker as well as the AthenaWrapper. I'm currently on SPL 1.1 and want to upgrade to 1.2
Please help!
Click to expand...
Click to collapse
I just spent the weekend trying to unlock my Athena and was having the exact same problem... USB would disconnect, errors 202, 267 . I finally was able to flash the Olipro bootloader, but had a hard time unlocking the radio. My device showed no radio under its properties, so I could not tell what radio version I had. Pressing "phone" would not bring the dialup screen. After so much sweat, I had to put it apart, only to find that the radio board connection to the motherboard was improperly seated, thus was having a bad connection. Once the connection was properly seated, the phone booted up to the emergency call screen, notified that there was no SIM card detected and when I looked in the device properties, the radio version was listed!. I then proceeded to unlock and flash the radio and this time the connection was not lost, the process completed without a glitch.
Hope that helps...
Related
I have tried many times to upgrade the Rom Image on my HTC Tytn (Cingular 8525) with no success. I am getting a 260 error with the program located at this link...
http://forum.xda-developers.com/showthread.php?t=293665
I did first run the unlocking application to unlock both SIM and CID before running the upgrade.
I followed all the steps exactly and have had no success...
The following might be effecting my attempt:
I am running my pc on Vista
I am syncing with Windows Mobile Device Center
I have tried to solve this problem for about two weeks. Can anyone help me?
Mrvanx has a guide on how to prepare Vista for flashing, you can find it here.
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Same problem
compwiz2008 said:
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Click to expand...
Click to collapse
Same problem here trying to change the radio version after changing the bootloader........
Connection alwayse lost just as said above.
Any help will be appreciuated
justx24
Use the RUU wrapper with the NBH file you want to upgrade.
I still have the same issue, even when using the RUU Wrapper and any nhb.
don't use vista
Ok, got one step furthur
I reached the point where the ROM Begins to update, which is VERY good...
The ROM update Reaches 1%, then waits for 20 minutes...
Then I get a 262 error and have to go through recovery, try again, with the same result.
i have same problem plz help thnx in advance
compwiz2008 said:
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Click to expand...
Click to collapse
Have you tried removing or adding a checkmark to the USB to PC in CONNECTIONS on your device? I remember having a similar problem when I installed Radio Rom 1.38 that my USB connection was lost with the pc . I am using XP when flashing so if you have no luck then do this on a XP machine.
Forgot to ask! What ROM are you trying to flash??
@compwiz2008 and ahmerpar
I read somewhere that running windows update will update WMDC........maybe give that a shot?
Maybe you can try to upgrade your ROM from your SD card.
Nope
Let me try that...
Still did not work
I'm probably going to just take my phone to a computer repair shop and pay them to deal with it, since I'm evedently doing something wrong.
I have a AT&T 8525. I installed 2.10 Olipro and then flashed with the latest AT&T WM6 upgrade from this site. It was labelled as the "official" upgrade.
The upgrade went well and everything seems ok (though it feels a bit more sluggish and I thought it would noticiabley increase speed of apps etc.)...anyway my Activesync is simply not working with this phone anymore. It doesn't recognize it when I plug in with the cable. This makes it hard for me to re-install a different ROM or any other app.
Bluetooth can see the phone, but, again, it doesn't seem to want to make an Activesync connection....please help...thanks in advance.
try deleting existing relationships. and create a new one. most likely because of your current upgrade, your DEVICE ID has been changed.
I actually have no relationships in Activesync right now.
I'm loading a fresh copy of Activesyn on my wife's computer to see if I can get a relationship established on a new install.
Any other ideas...I'm all ears!
you should be creating one.. its most likely because your DEVICE ID has been changed. have you checked it?
I have the same problem
The problem apears when I connect the device to the computer "USB Device Not Recognized".
Tested in another computer with same results...
It seems to be some driver issue, but I have no clue where to start...
I have a HERM200 (TyTN) unlocked and activesyn was working when the device OS was WM5. fter the upgrade, does not recognize anymore...
It's working now
After the OS upgrade, needs to turn off (for real) and turn on again. It works sweet.
Need to remember: MS Windows DEvices needs MS Solutions - Reboot !
Alright so I am so frustrated with this...and I am sure there is a simple solution for it. The screen on my old 8525 got messed up and since it was under waranty they sent me a replacement...the screen is ok on the replacement, but the phone isn't working (shows exclamation point next to "wine glass" rather than signal strength bars).... after hours and several phone calls to tech support, High End Devices waranty dept and who knows where else, it was determined that the current ROM version is incompatible with the AT&T network, I have to upgrade. So the version of the ROM on the replacement is 2.15.502.3 which makes wonder why in the world would AT&T send me a phone that would not work on their network? (I'm really trying not to vent here...) Anyways so I go to the HTC website as directed by the Tech. Support person download the stuff and after another hour on the phone with HTC and every possible sollution that they know is tried still can't install. I am running a Vista 64 machine and after getting around all the Vista quirks I am finally able to get to the Bootloader screen (button combination is: Side button [Ok] + [Power] Then push [Reset]...if done correctly your phone goes to the 4 bar boot loader screen, if not your phone soft resets and you have to try it again...) anyways in the bootloader screen it goes to the installation bar on both phone and PC and goes to 1%, then durring that one percent I get the horrible "ERROR 294 : INVALID VENDOR ID" on the PC and the Phone resets.....No matter how we have tried it it is always the same thing...redownloaded the file 3 times, restarted the phone about a gazillion times and the PC about 2 or 3 times. What can I do? I would love to have Ms Windows Mobile 6, but all I really want is a working phone....can anyone please help?
Some more info for those of you that can help:
On "Device Information" screen here is what I have:
ROM version: 2.15.502.3
ROM Date: 04/09/07
Radio version: {blank}
Protocol version: {blank}
On Bootloader screen:
In the top (red) section:
(in white)
HERM100
IPL-1.03
(in yellow)
HERM100
SPL-1.11
and then at the bottom (white) section:
(in black)
USB
(it says Serial when I unplug the USB cable)
I am trying to install the ROM titled:
RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship.exe
downloaded from:
http://216.139.227.230/download/Sof...502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship.exe
found by going to http://www.htc.com, Support, AT&T 8525, Software Download.
Thank you for any help you can give.
u cant be serious......you got an invalid model ID from an 8525 while trying to install an update from at&t itself.
well the solution would simply be to install hardspl (see the sticky) and then install the update. although there are many other easier and faster solutions i think this is the *safest* way. but then the fact that your radio version shows nothing makes me wonder......maybe a corrupted radio or something, which may or may not be related to the invalid model ID error.......anywho, search the forums for error 294 its probably been discussed many times
First of all thanks for your help. So I tried installing the 2.10 - Hard-SPL-V7 and it wont finish the install. I connect the device follow through the installation and when I get to the point where I push Yes on the 8525 the screen goes to the red/green/blue/white bars screen shows
HERM100
IPL-SSPL by Des
HERM100
SPL-1.09.ds
then the Computer shows ERROR [260]: UPDATE ERROR and the installation stops....
error 260 is an open port error, reboot your computer, and try again, if it doesnt work, try a different usb port, also disable watever firewalls or antivirus software you have
Okay so I diabled both the firewall (Windows Firewall) and the antivirus (AVG) and restarted the computer...tried 3 different USB ports...still the same problem....You don't think it could have anything to do with Windows Vista 64 and Windows Mobile Device Center. BEcause as soon as I go into the new Bootloader screen, the WMDC shows that the 8525 is diconnected now...even though it's not. I saw a post on here about installing drivers to get Active Sync on a Vista machine, but the drivers it provides are unsigned and Vista won't let me load them....so what's the next step? And again thank you so much for your help.
Is there any use in putting more effort into this or should I just have AT&T send me a new one?
whether there's any use left is ur decision, dont ask me to help you make your decision.
i know you can install unsigned drivers on vista, i dont know how, use the search. i have also heard that updating wmdc to the latest version helps too.
or you can either try and install hardspl using the microsd card, again use the search.
I installed an "updated" HTC Home Screen Plugin (obviously not for my phone model #) and now my phone is frozen. It will boot up but the home screen is frozen (i.e., non-responsive to any button presses). I attempted to re-flash the ROM using various ones I found for the NEON but all fail for the same reason.
Specifically, connection to ActiveSync is not possible (I connect via USB cable but ActiveSync doesn't recognize device). So what I do is put the phone in bootloader mode and then connect the USB cable. When I do this, the ROM upgrade program recognizes the phone and gets to the point where it shows the screen "Updating the ROM image on your PDA Phone.." and the phone shows a status bar at 0%. However, after a minute the computer screen says "ERROR [262]: UPDATE ERROR" and the phone is stile stuck at 0%.
My question is if there is any other way I can re-flash my NEON300? I've heard that it may be possible to but the nbh file on a FAT32 formatted card. I tried this by naming the nbh file to "TOUCHIMG.NBH" and "NEONIMG.NBH" but neither are recognized by the bootloader.
Thanks in advance for any assistance.
Try changing usb port or even re-installing activesync.
Alot pf people had the same problem on different devices but the cause should be the same.
for example, http://forum.xda-developers.com/showthread.php?t=298516
Let me know how you go.
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
wangobyte said:
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
Click to expand...
Click to collapse
You should have read the WIKI before flashing your device... http://wiki.xda-developers.com/index.php?pagename=Flashing Guide and here http://forum.xda-developers.com/showthread.php?t=355730
Am having a problem with unlocking a Hermes using the SIM_CID Unlock version 3A
I appear to be stuck in a loop with the unlock process. I appear to have got as far as having installed OliPro (while still being at bootloader 1.01) but keep getting error 262 UPDATE FAILED
I can then recover to the tri-colour screen and process as far as RECOVERY SUCCESSFUL
But I cant get as far as updating the radio or whatever else it unlocks towards the end of the process and no new ROM loads (if that is what the unlocker does?) The percentage screen appears but doesnt progress at all. Then I get ERROR 262 again.
Is starting to the bootloader screen a sign of a bricked Hermes? I can get SERIAL to show and can get it to change to USB on that screen when I plug it into a computer but cant get any proper communication with the unit from the computer with that screen in place: ActiveSync obvoiusly wont start. As I left the 3A unlocker, it said RECOVERY SUCCESSFUL but does that necessarily mean that I have a brick now? I thought that the installation of olipro by SIM_CID unlock version 3A means that the unit is now hard-unlocked?
(Yes, I did try Hard-SPL-V7.zip but cant set up any communication between the exe file and the tricolour screen)
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
I thought that tricolour screen meant that it is ONLY starting in bootloader mode?
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I am a bit lost: How do I get into bootloader mode? I thought that it starting in the tricolour screen meant that it had started up in boot loader mode? Is there some combination of pressing buttons and 'on' switches like on my Blue Angel?
As it appears to have got stuck in a mode while in an upgrade process which didnt work when this error occurred, when I get it started, what should I flash to get the bootloader updated, the SIM and CID unlocked so that I can choose which ROM to flash? Should I continue with the SuperCIM_CID unlock or Hard SPL?
I have fully unlocked another Hermes before and have been playing around with ROMs but this one seems to have worked out differently: I was under the impression that loading OliPro meant that it was unlocked?
(Sorry about that answer: I will try RUU_Unwrapper.exe again)
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I did what you said and immediately I unchecked the tick in USB, I heard that the computer was establishing communication with the Hermes
But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??
V7 still wont run but v3A still will!
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: This device both will and wont coopeate at the same time. But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE on error 260\.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: (Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
(Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
The computer IS communicating with the device (as I said it does give the 'ding' showing that the computer knows it is there) but it wont hard reset! It just goes straight to the tricolour screen immediately on startup. Even using a three hand method of pressing both buttons, pushing the reset in and putting the battery in at the same time gave the tricolour screen. And Windows Explorer cant get into the device. It seems to see it but there is no tree at all. So I cant use the Post 1160 method to flash from an SD card.
Even more baffling, i have now flashed a stock ROM successfully and v7 STILL wont communicate with the Hermes!! In desperation I even moved the directory to the root of C: Are some of these devices encrypted differently from others? So suddenly it boots properly and I immediately did a hard reset and erased everything and now Guess what? It hangs at the Windows Mobile screen! Needing a hard reset all over again
Should I just keep on trying Super SIM and CID unlock again and again until it works? (I assume that I have no longer got OliPro on it, though it does show a SPL of 1.40) There must be a way of unlocking this unit but this total non-cooperation doesn't seem to be covered in the Wiki. Is there a version of the Hermes like the Wizard which is more difficult to unlock than the others?
Sorry to reply again when no one gave any ideas on my last posting but I am wondering, horror of horrors, whether this might be a hardware problem?
I am now stuck at the tricolour screen ( 1.01, SPL 1.40.Olipro)) which turns on whenever I put the battery in. Connecting to the computer doesnt make any difference and obviously I keep getting ERROR 260 which seems to be a connection error meaning that the computer either isnt connected to the device (or that some software is conflicting somewhere, which is unlikely as flashing to the stock ROM did work before I tried to run V7 again)
Is there any possibility that running SuperCID&SIM unlock (which has never completed) caused all of this and is there any rescue procedure or should I just assume that this is a hardware problem now (or should I do a fresh posting)?
Is it inherently suspicious that tricolour turns in when I just put the battery in AND that even though SERIAL changes to USB on the Hermes, running the v7 hard update utility causes ERROR 260? [Or cant you run V7 when you already have OliPro installed somehow?]
There IS communication: Though I reported in my last posting that I could flash the Cingular ROM, flashing to the Cingular ROM now gets consistently stuck at 14%, sometimes with an ERROR 264!