Related
Hi guys,
I've got a T-Mobile MDA Vario 2 (Hermes).
i used the "HTC Hermes SIM & CID Unlocker *New* version v3a" tool so i could then load any ROM i want. I followed the instructions perfectly and then ran the unlocker, and that went fine too, however, when i'm trying to change to a particular ROM version, it gives me a "error 101 : Connection Error" after it tries to check the status of the device......it gets to the tricolour bootloader screen absolutely fine and the screen shows the following -
HERM300
IPL - 1.01
HERM300
SPL-1.40Olipro
It sits saying 'Checking the information onyour device..........please wait' for around 2 minutes, then kicks back and gives me the "Error 101 : Connection Error".
I have tried the search function, but there's not a lot i can find on the problem.
Can anyone help?
Thanks
Mark
That drove me crazy too until I finally found a post on another board explaining what to do.
If you notice when the updater is running, your activesync program will exit. Immediatelly restart activesync when you see it exit. It will not reconnect to your device, in fact it will show not connected but that is ok. The ruu is only using the activesync program, not to actual connection to communicate with your device.
I actually created an easily accessible activesync icon on the desktop of my PC so I can restart it quickly. Watch it closely, I have had the activesync program exit up to two times before I ever get the installation underway.
I guess this is normal, based on what I have read elsewhere.
Hope this helps. Let me know if you are successful with this method.
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.
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!
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
rceubanks said:
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
Click to expand...
Click to collapse
Your phone's cdma. This is a gsm forum. I'm assuming that you're trying to brick your phone with the gsm hard spl and not trying to flash the proper hard spl. Stop doing that, your phone is getting pissed at you. Go to ppcgeeks or the cdma (Herman, not Raphael) forum here.
haha leave it to me to find the wrong way to do something. I appreciate your heads up Ted!
rceubanks said:
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
Click to expand...
Click to collapse
Try here: CDMA Herman
same issue on GSM phone
Hi I have the same problem on a GSM phone.
I get the updating bar on my phone- it stays stuck at 0%.
then a communications error
Thanks in Advance
What is the problem with the RUU update?
I have searched for a solution to the RUU update/upgrade problem; none so far. Apparently, it is a major issue. I am interested in upgrading my Windows CE on my Xperia 6.1 to 6.5. I must have tried over a dozen times. The update process stops at 0% and Error [262] is reported. What can we do to resolve this? Is it compatibility or scalability issue? is it a problem with the software? The fact that it is working for some . . . and not for others is a source of concern about the stability of the software and this has potential implications; or it may well have to do with the hardware limitations of the PDA. Any ideas of a workaround?
You might try the Experia forum. You also might want to try Experia Roms.
I used to experience this issue as well. I simply go into communications and hit the USB to PC connection. Then remove the advanced functionality check. This has resolved many of the communication errors when playing with ROMS. This has been true with both GSM and CDMA devices.
I can confirm the issue. I have a 1st day release Fuze and flashed HardSPL no problem and have been making my roms ever since. But my cousin just got his new AT&T Fuze through his company and it refuses to HardSPL.
I went through several versions of the HardSPL and tried installing new drivers for the phone while in bootmode... all with no luck.
When connected through Activesync or Mobile Center, running the HardSPL brings up a confirmation windows on the phone, allowing reboots the device. It gets stuck at the black screen and times out. I've tried manually putting the phone in bootmode and trying it, but never gets past 0%.
I wonder if newer model TouchPro's are coming out with a revised bootloader?
Dunno if i can link to another forum. If not, appolgize and Admins remove the link than please.
For the 262 error, look here:
http://www.4winmobile.com/forums/windows-mobile-faq/13329-ruu-errors.html
player911 said:
I can confirm the issue. I have a 1st day release Fuze and flashed HardSPL no problem and have been making my roms ever since. But my cousin just got his new AT&T Fuze through his company and it refuses to HardSPL.
I went through several versions of the HardSPL and tried installing new drivers for the phone while in bootmode... all with no luck.
When connected through Activesync or Mobile Center, running the HardSPL brings up a confirmation windows on the phone, allowing reboots the device. It gets stuck at the black screen and times out. I've tried manually putting the phone in bootmode and trying it, but never gets past 0%.
I wonder if newer model TouchPro's are coming out with a revised bootloader?
Click to expand...
Click to collapse
Yes they are coming with a new bootloader. I just got my phone replaced from ATT and the new one came with 1.95 version while originals were 1.90. There is no HARD-SPL out for 1.95.
The way to do it now is to flash an old original AT&T rom with the 1.90 bootloader (since it's original, it won't require HardSPL). Then go ahead and everything should work as described in this forum/wiki.
Interseting. Sounds like a winner. Next time he comes around I'll try this.
Any idea where I can get a AT&T older rom that has the 1.90 HardSLP on it? I am having the same issue with the Error 262 update error.
Thanks
smicale said:
Any idea where I can get a AT&T older rom that has the 1.90 HardSLP on it? I am having the same issue with the Error 262 update error.
Thanks
Click to expand...
Click to collapse
You should probably go to your ATT store and tell them you'd like to get the official Hard SPL update.
I am really struggling with this. Do I have to the FLASH HardSPL or can I just go straight to the flashing my preferred ROM. I can not get get the FLASH HardSPL to work because of this Error 262. Please someone tell me where I am going wrong with this!!!! I am bout to pull my last hair out!
smicale said:
I am really struggling with this. Do I have to the FLASH HardSPL or can I just go straight to the flashing my preferred ROM. I can not get get the FLASH HardSPL to work because of this Error 262. Please someone tell me where I am going wrong with this!!!! I am bout to pull my last hair out!
Click to expand...
Click to collapse
If u want to use not the official rom made for ur provider and phone, hardspl is the only way. Any custom rom needs hardspl. Otherwise ur phone will not accept the rom.
But look here http://forum.xda-developers.com/showthread.php?t=410150
and flash the stock 1.90 SPL first, then u are ready for hardspl.
Description how to do stock spl is in this thread. Its normally meant for going back to stock for repair, but it should also solve ur issue.
NOT SHURE BECAUSE IN THE CDMA SECTION, IS UR PHONE CDMA OR GSM. MY SOLUTIUON IS FOR GSM !!!!!!
U SHOULD CHANGE THE POSTING SECTION IF ITS GSM !!!!!
Try doing the HardSPL in a Windows XP machine (needs .NET Framework 2.0 and ActiveSync). Goodluck.
i had the same problem as you and i maybe have a solution for you
go to your usb settings and look if you have a check box saying something about advanced networking. if it is indeed checked uncheck it and your problem will be gone hopefully
i did it on my telus touch pro and i am now able to upgrade my phone to winmo 6.5
Hey All,
I'm at my wits end here. I got a new phone through Sprint's phone replacement program a week or so ago and decided to flash it today, that's when my problem started.
I've searched Google, PPCGeeks, SmartphoneJunkie, and XDA-Devs and tried all the suggestions but still seem to have no luck getting around the 262 Error when I try to flash to HardSPL 0.37.
When I enter bootloader, I face the following screen:
Security Unlocked
RAPH800
SPL-0.40.0000
MicroP-Herman (LED) v0C85
MicroP-Herman (KEY) v0685
PSOC-Raph STAGE_EVT v20
USB
Initially I tried flashing after I plugged it in. Error 262. I realized I forgot to associate it through WMDC (through a clean install) so I did that and tried again. Error 262. I searched around and realized I didn't deselect "Enable Advanced Network Functionality". Changed it, tried again, Error 262. I tried it on my desktop (Win7 x64), my laptop (Win7RC x32), and my old desktop (WinVista x32) all with Error 262. Knowing it was a communications error, I disabled Windows Firewall and all AV products thinking maybe they blocked something. Still Error 262. I even re-downloaded the Hard SPL package. Big surprise, Error 262.
I read in my travels that the shown Security Unlocked banner is for Radio only, so I know I have to flash to SPL-0.37 before I try any other flashing.
Suggestions, Please??
Aquinox88 said:
Hey All,
I'm at my wits end here. I got a new phone through Sprint's phone replacement program a week or so ago and decided to flash it today, that's when my problem started.
I've searched Google, PPCGeeks, SmartphoneJunkie, and XDA-Devs and tried all the suggestions but still seem to have no luck getting around the 262 Error when I try to flash to HardSPL 0.37.
When I enter bootloader, I face the following screen:
Security Unlocked
RAPH800
SPL-0.40.0000
MicroP-Herman (LED) v0C85
MicroP-Herman (KEY) v0685
PSOC-Raph STAGE_EVT v20
USB
Initially I tried flashing after I plugged it in. Error 262. I realized I forgot to associate it through WMDC (through a clean install) so I did that and tried again. Error 262. I searched around and realized I didn't deselect "Enable Advanced Network Functionality". Changed it, tried again, Error 262. I tried it on my desktop (Win7 x64), my laptop (Win7RC x32), and my old desktop (WinVista x32) all with Error 262. Knowing it was a communications error, I disabled Windows Firewall and all AV products thinking maybe they blocked something. Still Error 262. I even re-downloaded the Hard SPL package. Big surprise, Error 262.
I read in my travels that the shown Security Unlocked banner is for Radio only, so I know I have to flash to SPL-0.37 before I try any other flashing.
Suggestions, Please??
Click to expand...
Click to collapse
it doesn't seem like you are doing the process 100% correct. unlocking your phone really doesn't have much to do with activesync, as that part is only needed to actually move the files to your device.
you are supposed to initiate the hardspl from the device itself with the .nbh file present on the sd card. your sd card may have something to do with it, it should be FAT32 formatted & probably no larger than 4gb.
feel free to get at me thru PM/IM/EMAIL watever & we'll figure it out man. GL