Develop Bugs

8525 Dead-End

PLEASE ASSIST: I'VE RECENTLY UPGRADED MY CINGULAR/ATT 8525 HERMES UNIT TO WINMOB6 AND NOW CAN'T GET PAST THE INITIAL WINDOWS MOBILE SCREEN WHERE IT SAYS "TAP THE SCREEN TO SET UP YOUR WINDOWS MOBILE BASED DEVICE." (THE TOUCHSCREEN SEEMS TO BE DISABLED) ALSO, NOW ACTIVESYNC WILL NOT CONNECT TO THE DEVICE. I'M AT A LOSS AS TO WHAT ELSE TO DO (TRIED HARD RESET SEVERAL TIMES WITH SAME RESULT). IF SOMEONE COULD POINT ME IN THE RIGHT DIRECTION - I'D SURE APPRECIATE IT.

ETUMON said:
PLEASE ASSIST: I'VE RECENTLY UPGRADED MY CINGULAR/ATT 8525 HERMES UNIT TO WINMOB6 AND NOW CAN'T GET PAST THE INITIAL WINDOWS MOBILE SCREEN WHERE IT SAYS "TAP THE SCREEN TO SET UP YOUR WINDOWS MOBILE BASED DEVICE." (THE TOUCHSCREEN SEEMS TO BE DISABLED) ALSO, NOW ACTIVESYNC WILL NOT CONNECT TO THE DEVICE. I'M AT A LOSS AS TO WHAT ELSE TO DO (TRIED HARD RESET SEVERAL TIMES WITH SAME RESULT). IF SOMEONE COULD POINT ME IN THE RIGHT DIRECTION - I'D SURE APPRECIATE IT.
Click to expand...
Click to collapse
hmm no need to scream.
Push the OK on left and power on right, and stick stylus in all at the same time. Re run the exe file while it is plugged in to active sync, and see. Which WM6 did you use?

Sorry I'm new at this. I used WM6.1. Which exe file do you want me to re-run. ActiveSync is offline....I can't get it to connect to the unit. Thanks for your assistance.

ETUMON said:
Sorry I'm new at this. I used WM6.1. Which exe file do you want me to re-run. ActiveSync is offline....I can't get it to connect to the unit. Thanks for your assistance.
Click to expand...
Click to collapse
Ok, since you're on ATT I suggest you follow my instruction above, get into tricolour screen (bootloader), and download this
from the post above you will get the shipped ATT rom. Don't worry if activesync is saying is not connected, just run the file. You will then get back to a WM6.

The phone originally came with WM5 and I was upgrading to mess around with the thing. I'm at the tricoloured screen and now downloading the files from RapidShare. Will this get me back to WM5 or to the upgrade. If there is a way, I like to try the HardSPL flash I've been reading about today - will this work on either WM version? Txs & Rgds.

ETUMON said:
The phone originally came with WM5 and I was upgrading to mess around with the thing. I'm at the tricoloured screen and now downloading the files from RapidShare. Will this get me back to WM5 or to the upgrade. If there is a way, I like to try the HardSPL flash I've been reading about today - will this work on either WM version? Txs & Rgds.
Click to expand...
Click to collapse
After you have flashed this WM6.0 you really need to flash hard SPL first, I thought you would have done that already.
Really please read this first before you brick your phone.

No that's the thing. I'm just finding out how I went about this all wrong and maybe shouldn't have been messing this in the first place. Anyhow, my bootloader screen reads like this:
HERM100
IPL-1.04
HERM100
SPL-1.40.Olipro

ETUMON said:
No that's the thing. I'm just finding out how I went about this all wrong and maybe shouldn't have been messing this in the first place. Anyhow, my bootloader screen reads like this:
HERM100
IPL-1.04
HERM100
SPL-1.40.Olipro
Click to expand...
Click to collapse
Well follow mrvanx guide, that's all I had to get on with few months ago.

Many thanks for the advice. So just to be clear I should first run the file I downloaded from RapidShare to get me back to a working WM version, then follow mrvanx guide to flash Hard SPL or viceversa...

ETUMON said:
Many thanks for the advice. So just to be clear I should first run the file I downloaded from RapidShare to get me back to a working WM version, then follow mrvanx guide to flash Hard SPL or viceversa...
Click to expand...
Click to collapse
I have not tried to hardspl a non working phone sorry so I have no experience with that. Give it a go first, and report back.

Still Stuck
zocster said:
I have not tried to hardspl a non working phone sorry so I have no experience with that. Give it a go first, and report back.
Click to expand...
Click to collapse
Nope, didn't work. Here's the report:
ERROR [260]: UPDATE ERROR
The update utility cannot connect to your PDA Phone. Please check that your USB cradle/cable is connected properly between the PC and your PDA phone.
Check the following:
1. The PDA Phone is connected to the USB cradle/cable.
2. The USB cradle/cable is connected to the PC.
Is there another way to establish comunication with the PDA other than through ActiveSync? Somekind of emulator box or binary software???

ETUMON said:
Nope, didn't work. Here's the report:
ERROR [260]: UPDATE ERROR
The update utility cannot connect to your PDA Phone. Please check that your USB cradle/cable is connected properly between the PC and your PDA phone.
Check the following:
1. The PDA Phone is connected to the USB cradle/cable.
2. The USB cradle/cable is connected to the PC.
Is there another way to establish comunication with the PDA other than through ActiveSync? Somekind of emulator box or binary software???
Click to expand...
Click to collapse
hmm weird, so have you got .net framework installed on your PC? try it again one more time while in bootloader, plug the phone to USB as long as you can hear the 'ding' sound you should be OK. I have 'bricked' my phone a few times and this always work. What are you trying to flash? the hardspl or the ROM?

Yes, today I upgraded to .net framework 3.5 when ActiveSync failed Microsoft Error took me to their website and offered me the option. I had been running 2.x .net framework and never had a problem would also use same ActiveSync with my old Axim X30.
Yes, I can hear the 'ding' sound and I was trying to run the file RUUWrapper.exe (Hermes ROM Upgrade w/ the option Force using SSPL).

well that shows the other way around doesn't work, so you need to get your phone to a working WM6 state, how is your download going from rapidshare? get it to boot loader mode again and flash that exe file.

Just completed that route - I ran the PDA Phone ROM Update Utility 3.12.3.7 - the process took about 10 minutes to go through 100%, then it restarted and stayed at the Window Mobile screen for little over minute (crossing my fingers), but then just showed the same message "Tap the screen to set up your Window Mobile based device." Please let me know if you have other avenues to try – It’s close to 4am here in Miami, but I'm not sleeping. I’m really glad you are able to assist with this mess – thanks a lot!

ETUMON said:
Just completed that route - I ran the PDA Phone ROM Update Utility 3.12.3.7 - the process took about 10 minutes to go through 100%, then it restarted and stayed at the Window Mobile screen for little over minute (crossing my fingers), but then just showed the same message "Tap the screen to set up your Window Mobile based device." Please let me know if you have other avenues to try – It’s close to 4am here in Miami, but I'm not sleeping. I’m really glad you are able to assist with this mess – thanks a lot!
Click to expand...
Click to collapse
so did you follow it through? and it didn't fix it? you have some bad blocks?
Unfortunately, you need to have some sleep, and read these when you wake up
http://forum.xda-developers.com/showthread.php?t=296722
http://forum.xda-developers.com/showthread.php?t=369434

zocster said:
so did you follow it through? and it didn't fix it? you have some bad blocks?
Unfortunately, you need to have some sleep, and read these when you wake up
http://forum.xda-developers.com/showthread.php?t=296722
http://forum.xda-developers.com/showthread.php?t=369434
Click to expand...
Click to collapse
what does bad blocks mean?
Okay, looks like I've got a Type 2c Brick Situation in my hands.... I think I will take your advice and get some rest and tackle this again later on. I really appreciate your assistance - will you be around again later?

Okay good day, I'm back on the trail. Found shipped ROM on WIKI for HERMES in the following thread - http://forum.xda-developers.com/showthread.php?t=277664
Downloading now...According to pof(moderator) it's a "new rom from the still unreleased Cingular 8525: HTC Hermes (HERM100) branded from U.S. Operator Cingular"
My only question then would be that this appears to be made for WM5 and I performed the WM6 upgrade which is what got me into this mess in the first place - so will there be any conflicts or issues I should now about? I'm about to go ahead with it - if anyone is out there and thinks otherwise, please advise soonest. Thx & rgds, Ed

ETUMON said:
Okay good day, I'm back on the trail. Found shipped ROM on WIKI for HERMES in the following thread - http://forum.xda-developers.com/showthread.php?t=277664
Downloading now...According to pof(moderator) it's a "new rom from the still unreleased Cingular 8525: HTC Hermes (HERM100) branded from U.S. Operator Cingular"
My only question then would be that this appears to be made for WM5 and I performed the WM6 upgrade which is what got me into this mess in the first place - so will there be any conflicts or issues I should now about? I'm about to go ahead with it - if anyone is out there and thinks otherwise, please advise soonest. Thx & rgds, Ed
Click to expand...
Click to collapse
Sounds good man!! Flash it!! oem WM6 roms usually fix allot of issues.. Don't be scared everyone else is busy flashing WM6.1 roms all the time now!

Thanks for the words of support <joshkoss>! Just attempted several times to flash the Shipped ROM I found from <pof> (PDA Phone ROM Update Utility - R:31300 D:51000 U:31101 P:0) and keep getting ‘ERROR[260]: UPDATE ERROR’ message. While instead I went back again to flashing the ROM that <zocster> suggested last night (PDA Phone ROM Update Utility 3.12.3.7) and it does go through the entire 10 minute process until it shows 100% completion both on the PDA and on the PC and then tells me congratulations….etc. I even flashed it twice back-to-back as I read to do in one of the threads – but just keep getting back to the dreaded Window Mobile screen with the same message "Tap the screen to set up your Window Mobile based device."
My next question is this: Why does the PDA Phone ROM Update Utility 3.12.3.7 connect to the PDA, but the PDA Phone ROM Update Utility - R:31300 D:51000 U:31101 P:0 (which I read is the Shipped ROM that I need to get the PDA back to) gives me an error message. Obviously, there is a connection since I’m able to get a 100% completion on the other ROM??? Please kindly advise…..

Cannot HARD Reset ???!!!!!

Hi Experts,
Would like to check whether anyone out there have ever encounter such problem?
I receive a rude shock this morning when I power on my 1 week old HTC HD which reads below:
"This concludes the beta test of this software release. Thank you very much for your time and effort in helping make this a great product for our customers.
To obtain a newer release or further information, please revisit the web site that you used to obtain your current beta release."
I've flashed it with Dutty's Rom v1.8 and many other software which I use to have on my previous PDA. I son't think its coming from the ROM but maybe the software i installed. I remember the last few ones was Resco Explorer, Resco Pro viewer, FTP CLient...etc.
I tried many ways but just cannot seem to get rid of this screen as it appears right after any reset. So I decided to hard reset the phone but after going thru the procedure of holding the Vol up/down and power button, it just reboot like after a soft reset...and YES, it went back to the same screen!
Another thing, I couldn't get the phone to sync with my PC too.
What when wrong and what other method can I try? Any kind soul's advice will be greatly appreciated.
Cheers and thanks in advance.

put your phone on bootloader mode(tricolour screen),then connect your usb cable,on your tricolour screen it should show you USB,when you see it on the screen(on your phone)then you can flashing rom.
Hope this help

chg1282002 said:
put your phone on bootloader mode(tricolour screen),then connect your usb cable,on your tricolour screen it should show you USB,when you see it on the screen(on your phone)then you can flashing rom.
Hope this help
Click to expand...
Click to collapse
Thanks for the advice, you are right. Its the Time Bomb for Dutty's ROM v1.8.
Just manage to get the new ROM and flash it. Have to re-install the bunch of softwares i did earlier as i didn't read carefully that there's a time bomb.
Thanks again for the advice.
Cheers

yes it's a problem with the OS version used unknown by the cooker. It has been corrected. It is mentioned the Dutty 1.8 thread. Since Dutty 1.9 is out seems good time for an upgrade.

you have to put the CAB file on your memory card,when you flashing the new rom,you have to install all software back your phone

Can you be a bit more specific
Hi
Can you please do a little step by step thing. I am having this problem. What do i do once i am in tricolour screen after USB is displayed at bottom of screen.
Thanks in advance

Stuck unlocking (read the other forums) little help?

Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.

I had what sound like the same problem yesterday.
my post is over at ppcgeeks.
"I disconnected but I did not see the phone exit bootloader mode and reset itself.
....
What should I do from here?
Reboot phone, soft reset, hard reset? - go have fun?
....
I did a couple soft resets and have been playing around with it,
I guess I upgraded right... but it was weird there at the end, instructions not the clearest to me, i guess."
mine seems to be working fine, except the weather thing.
shows
in the About section my phone reads
WM 6.1 Pro
CE OS 5.2.21041
Device Information reads
ROM version 1.05.Alltel
Radio version 3.42.30
PRL Version 30008
PRI version 2.02_011
I was kinda scared to do another hard reset b/c I had already changed a bunch of settings.
Sorry if this doesn't help you too much,
but it is nice to know I'm not the only one with this issue
.

Hmm sounds like a similar problem. But I thought it wasn't unlocked unless we saw 2.31.coke somewhere in the device information.
As far as I know, hard reset did not hurt the phone. I tried installing that unlocker 4 times then went with the original HTC rom and it still turned out just like before. It installed the rom fine
Yeah I am still concerned about how it wont go through the exitbl step...

moonwoo said:
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
Click to expand...
Click to collapse
Yeah, the directions can be a bit confusing over there on that thread
Basically here are the steps
Download the 2.31 unlocker
Download the ROM you want to use (my personal preference is this one for a TF2D style or this one for a WinMO 6.5 style interface that has TF2D included to switch back and for - both very stable, fast and clean and the thread is very active for help (especially if your on Verizon or Bell which can have issues)
from there, use WinRAR to extract each file into separate folders
then Put your phone in bootloader mode (press and hold power+camera+stylus in reset until 3-color screen comes up)
At this point at the bottom of the screen it will say Serial, plug it into the USB cable or cradle and it should change to USB
Start the exe in the 2.31 and follow the directions (you may get some errors about sleep4.exe just click on OK as it keeps occuring its a XP/Windows7 64 bit issue if that is what your using)
At the point where it tell you to disconect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
once complete, reboot, allow it to do its thing then reboot and go back into bootloader again during reboot you should see coke 2.31 in the upper left if so your ready to go
plug it into your USB/Cradle again and then go into the ROM folder you extracted the ROM into
Once the screen on your phone says USB again go to the folder and double click on the RomUpdateUtility.exe file and follow the directions again, it may take some time so be paitent
once the phone flashes and reboots, let it run and do its thing to the and reboot itself then (and here is an important step for stability) once it starts up do a hard reset (red+green+stylus in reset hole) hit the enter button (center of D-Pad) it will reflash the phone and then red key (send) when prompted
then go thought the setup again, this time you can actually set things up as your keeping them this time and once things are done and your at the start screen on your phone power off (not reset) the phone and then start it up again - seems doing it this way takes care of alot of little issues that will come up before they can happen
Depending on your carrier be sure to have one of the DCD Carrier Cabs as well especially for the 6.5 ROM as it is a generic ROM and some have reported needing to run the DCD Carrier Cab for the service they use to get on the internet and use GPS and the like
Hope that clears up things a bit LOL
Detroit Doug

Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!

moonwoo said:
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
Click to expand...
Click to collapse
Your all set to flash if in bootloader it says as your phone does SPL-2.31.CoKe
you all unlocked and ready to go ... just put your phone in bootloader mode then connect the phone to your PC "serial" will change to "USB" and then run the RomUpdateUtility.exe file and follow along with the bouncing ball, do the watusi, wipe hands on pants - whatever helps you pass the time
but follow the steps as outlined above with the hard-resets and power-offs and the like, believe me its better to solve the issues before they occur than wait and have to start over
Detroit Doug

Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!

moonwoo said:
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
Click to expand...
Click to collapse
Glad it worked, and Ill try to answer you concerns
1 -Now that it is unlocked go ahead and swap ROMs all you want to, the tricky part is the stock ROM, flashing back to stock can and will revert your radio (if youve upgraded it) and ca cause issues with the unlocker, but a simple run of the unlocker 2.31 again can correct it
2 - NFSFAN like other Chefs have ways of moving data/programs around when they cook up these ROMs utilizing whatever kitchen program they personally prefer that being the case how they data/programs get pushed about can create the speediness you now see in your phone by freeing up the RAM for apps and the like and pushing programs off to the side optimizing how the device should have been setup from the start
As for that, Ive been using his ROMs as well as some others for quite some time and have had little to no issues with how he places the progs and data so I wouldnt worry about it
Yeah, Live in Las Vegas now - but Michigan will ALWAYS be home Go Red Wings !!!!
Detroit Doug

Thanks Doug, for all your information. Your answers were great! Hopefully I wont need too much more help in the future. i'm learning~

Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.

hibbiejibbie3 said:
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/showthread.php?t=20370
Detroit Doug

Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.

Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
Check your PM over at PPCGeeks
Detroit Doug

Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
From Detroit_Doug
At the point where it tell you to disconnect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
Maybe wait longer if you can,
I reckon some pc take longer to fully recognize[process] the disconnect and reconnect procedure.
example: disconnect > wait 20-30 seconds > reconnect > wait 20-30 seconds > then continue
I had that same issue and waiting longer during this process helped
.

I can't even get to that point. With active sync on as soon as I start the unlocker RUU it gets the info from my phone and shows the current rom 3.14.605.1 ....I click update and it shows 2.31 unlocker I hit next and then the install status bar comes up on my desktop and my phone goes into bootloader mode and the active sync connection drops and I get the 262 connection error. If I start the RUU with my phone in bootloader usb mode already it does not detect my current rom and I click next. click next to 2.31 unlocker, and it goes through the same steps and I get the same error. Is there anything I have to do to my phone prior to running the RUU. My phone is a verizon xv6900 running wm 6.1 rom 3.14.605.1 with radio 3.37.78

I have the same problem with my new sprint touch. I get error 262 at 0%, did they change something in these new phone that won't allow us to unlock?
Rom is 3.03.651.4
radio 3.42.30

I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.

I ended up having to re-run the .041 unlocker and then the 2.31 unlocker and it ended up working for me. I'm not sure why I had to because I Had the same bootloader info prior to running the 2.31 unlocker in the first place. The 6.5 rom and gps rom has been working flawlessly for a week now, the only thing I had to do was call up VZW (*8889) the guy answered "account investigations" LOL I told him I had to hard reset and my phone wouldn't authenticate and he asked me to call back from another line. I told him that I had no landline and he said thats fine I can override it just call back right away whenever you get to another phone. That was on friday and I have not called back but I've been able to text, make and receive calls so I don't think I will unless I have to.

gooney said:
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
Click to expand...
Click to collapse
thank you! i did that and it worked for me.

yeah, it says right in the directions over there to just run the exe it will create a temp folder and run the RUU itself from there
Extracting it and running it will always cause issues
also - Ignore the sleep4.exe or whatever if you encounter it - it is a legacy exe that is called that isnt used anymore, wont affect the unlocking just hit OK through it
Detroit Doug

Energy ROM semi bricked my Dash, help needed! (And appreciated)

Hello everyone, I am really new to this forum having received the Dash 2 days ago. Looking to get it up to speed I flashed the 6.5 Energy Rom according to instructions. I think that was a very bad move, because now the cellphone is stuck on the Loading Energy Rom screen. I have searched the forum for answer and have already tried the following:
1- Entering bootloader and flashing original ROM. No luck because EVERY rom I have gotten, be it from here and T-Mobile, it says invalid vendor ID.
2-Tried to perform a hard reset. Did not work.
3-Flash the original ROM through the memory card. No avail.
The phone cannot connect to active sync, so I can't install any cooked ROMS. I think the solution is installing the original ROM by the bootloader, but I cant seem to find a compatible one. My cell information is the following:
Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU
EXCA 100 S/N SZ713FE05873.
Is there any way with that information someone can tell me which ROM to use? Or any other tip/hint/suggestion? Any help will be greatly appreciated!

I have the same Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU value and i was able to restore my phone to working status with the following ROM
http://www.megaupload.com/?d=IJIVTIMF
Hope this help
10507

Thank you very much 10507! I'll download it now and see if it works.

Thanks for the file but it appears that it is for the SDA. It dit not work

luisro said:
Thanks for the file but it appears that it is for the SDA. It dit not work
Click to expand...
Click to collapse
That's odd, I was able to restore my Excalibur/Dash after flashing the corrupted EnergyRom.
Hope you will find a way to resolve your problem.
10507

But how did you do it? Flashing it through USB or through the memory card? The weird thing is that when I run the EXE the cellphone that appears in the picture of the program is an SDA. But well I will try it again and thank you for the help!

I used bootloader method and connected my phone through USB for flashing. Remember to remove your memory card when flashing.

well, I've been in your situation for almost 3 days now, and still no solution for it, maybe it's time to put it in the box and purchase a new one , all thanks to the broken EnergyROM ...

Ok guys. Don't give up. Believe it or not, a Dash is NOT easy to brick like some other devices. the steps are fairly clear but let me refresh:
- Go into bootloader by holding the camera button and powering on the phone
- Connect the USB cable, you will hear the ba-bing USB connect sound on your PC (if u don't thats why you're having issues flashing)
- Download and unpack a "factory sealed" signed ROM. I use this one: http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
- With USB connected and the phone in the multicolor bootloader, run RomUpdateUtility.exe, check the boxes, it next, bla bla bla.
- It will look for your device for 20 seconds. then hit "update" and next.
- It should then start flashing the Excalibur Brightpoint Factory ROM back onto your phone
- If you can't get this far or it fails, try a different PC or Flash from the SDcard
** NOTE: If flashing from USB, REMOVE the SD CARD! This is the biggest mistake of most people trying to flash from USB.
Good luck.

ookba said:
Ok guys. Don't give up. Believe it or not, a Dash is NOT easy to brick like some other devices. the steps are fairly clear but let me refresh:
- Go into bootloader by holding the camera button and powering on the phone
- Connect the USB cable, you will hear the ba-bing USB connect sound on your PC (if u don't thats why you're having issues flashing)
- Download and unpack a "factory sealed" signed ROM. I use this one: http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
- With USB connected and the phone in the multicolor bootloader, run RomUpdateUtility.exe, check the boxes, it next, bla bla bla.
- It will look for your device for 20 seconds. then hit "update" and next.
- It should then start flashing the Excalibur Brightpoint Factory ROM back onto your phone
- If you can't get this far or it fails, try a different PC or Flash from the SDcard
** NOTE: If flashing from USB, REMOVE the SD CARD! This is the biggest mistake of most people trying to flash from USB.
Good luck.
Click to expand...
Click to collapse
Thanks ookba for cheering us up. I'm having the same problem like many, many people in this forum hopeless seeing our dash not responding to every solution proposed in this forum and the only thing that we have right now is keep trying to flash and see if it works. I will try again in different PC and see what happens. I'll let all of you know if I finally resurrect my s621.

Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems

luisro said:
Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems
Click to expand...
Click to collapse
This problem is ridiculously weird to why some members are able to restore their phone to original factory condition, and others are not able. Therefore, I have search from trustworthy sites and from friends for difference made ROM. Hopefully, one of these ROMs with help out anyone...........
1.33.422.1 (Worldwide English, WM6)
http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
1.27.405.1 (Worldwide English, WM6)
http://rapidshare.com/files/100235639/HTC_S620_WWE_1.27.405.1.exe
1.22.531.6 (T-Mobile USA, WM6)
http://www.mediafire.com/download.php?z4vjgzxisrz
1.22.531.4 (T-Mobile USA, WM6)
http://www.mediafire.com/download.php?yygkw1d5xmc
1.11.531.1 (T-Mobile USA, WM5)
http://rapidshare.com/files/104641948/T-Mobile_DASH_WM5_V_1.11.531.1.exe.html
Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_ 02.98.90_Ship
http://www.mediafire.com/?9gbwdzd2omg

Thanks 105507 but no success at all, I even found 2 more factory roms in the web and also they don't work. I own an unbranded international version s621 manufactured by Brightstar corporation (I tried to flash Brightstar's stock rom but it didn't work) and I noticed this because in the warranty docs it says brigthstar corporation and originally the phone came with WM5.

not that this will help. but this is one of the reasons why people should be really installing the hardspl so if you have a bad flash, you dont have to install a stock rom. any rom whether be it cooked or not will work. but this hardspl must be done prior to installing ANY rom. the hard spl is done by jockyw2001. send him a pm to see if theres anyway to get that on the phone, even in its current state.
edit: here's the link to the hardspl: http://forum.xda-developers.com/showthread.php?t=329605

luisro said:
Hello everyone, I am really new to this forum having received the Dash 2 days ago. Looking to get it up to speed I flashed the 6.5 Energy Rom according to instructions. I think that was a very bad move, because now the cellphone is stuck on the Loading Energy Rom screen. I have searched the forum for answer and have already tried the following:
1- Entering bootloader and flashing original ROM. No luck because EVERY rom I have gotten, be it from here and T-Mobile, it says invalid vendor ID.
2-Tried to perform a hard reset. Did not work.
3-Flash the original ROM through the memory card. No avail.
The phone cannot connect to active sync, so I can't install any cooked ROMS. I think the solution is installing the original ROM by the bootloader, but I cant seem to find a compatible one. My cell information is the following:
Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU
EXCA 100 S/N SZ713FE05873.
Is there any way with that information someone can tell me which ROM to use? Or any other tip/hint/suggestion? Any help will be greatly appreciated!
Click to expand...
Click to collapse
My phone is the same your phone but ONBL 1.33.0000 and SPL 1.33.0000
I'm trying to find the original rom of this line but not found. Please help me!

Have you done a reset? My friend fixed his by trying reset a few times. He reset it, walked away...., it took long time to see whether it booted over; if not, do it again...
By the way, he leave the sim card in; and, you need to remove your micro sd card.

On an official site it is possible download ROM for your phone. It is flashing from bootloder mode. It some times helped me, while I have not flashed hard SPL.

luisro said:
Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems
Click to expand...
Click to collapse
Hi my friend, I wish you lucky!!!
by the way, where country you're from, I have some Shipped Roms here for brazilian Excalibur (S621), maybe it could help, if the answer is yes, let me know to made this one come to you

http://wiki.xda-developers.com/index.php?pagename=Elf_GoldCard

Furious Girlfriend (oh My beloved Helloween died with my ROM's)
Boy oh Boy...
My ROM's are now in heaven
Girlfriend deleted they (I'm so sorry...)
But, pay attention in this thread
http://forum.xda-developers.com/showthread.php?t=381726
In there have a sort of shipped ROM's and maybe coud help you
Good luck my friends
A friend from XDA have some Shipped Rom's and will upload it for you, shortly he'll post something here

[TOOL] Task 29 (format internal Memory) without drivers, without mtty-It's about time

Hi all, for all the people like me who do not have the patience or knowledge do adventure themselves in the mitty thread.
This program already exists for X1, HD2, TP2 (for what I know) and I have tested it and it works.
After some search on this forum I have talked to agent_47, who was kind enough to make a task29 program for our HTC Diamonds (GSM version).
Agent_47 or me do not take any responsibility for ay damage done to your device. Use it at your own risk, and only after you have HSPL already installed on your device.
Do not know what a HSPL is, check here:
http://forum.xda-developers.com/showthread.php?t=415191
agent_47 said:
it will flash radio 1.09.25.23
replace the radio if u want to use other version
Click to expand...
Click to collapse
agent_47 said:
now we can mtty our "HTC Diamond" without having the need of MTTY and its drivers
INSTRUCTIONS:
- download and unzip
- run then ROMUpdateUtility.exe and wait for it to finish.....
- device will reboot but will neva go past the bootscreen coz there is no OS to boot
- take our batti and then flash a rom using mSD card or by taking device into bootloader and using customRUU to load ur favorite ROM
DOWNLOAD:
http://rs604.rapidshare.com/files/407049148/task29-diamond.7z
WHATS TASK29\MTTY
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
but the thing is, mtty is and can be hard to use for new users. ... for me,, i was having the worst time installin the drivers needed to run mtty on win7 x64. so u i made this tool for me and for all
CREDIT:
all credit goes to doloop for coming up with the idea
Click to expand...
Click to collapse
and I would add to agent_47, as he adapted this tool for the HTC Diamond

Did anyone tried this?
What's the verdict?

mmm. interesting.

Thanks for the share and all your hard work but this is actually harder than mitty for me and i am a windows 7 user also

wapvirus said:
Thanks for the share and all your hard work but this is actually harder than mitty for me and i am a windows 7 user also
Click to expand...
Click to collapse
I do not understand how this is possible, I am using Vista and this is as easy as flashing a ROM with a computer. You just connect the device via USB to the Diamond, let active sync finish. Then you just need to run "ROMUpdateUtility.exe" and follow the instructions.
I have tested this, and I can confirm this is working for the European HTC Diamond (bought in Portugal).
This was not made by me, but I do think that more people will benefit with this program. Hopefully people will overcome the initial resistance to change.

Great idea!
I used to MTTY through VMWare Windows XP x86 within my host Windows 7 x64. It was a pain in the ass to get though but it always worked for me. This is a great time saver!
Regards to both of you Johev and agent_47!
Willing to test on my next flash.
Best regards,
Cina.

INSTRUCTIONS:
- take our batti and then flash a rom using mSD cardor by taking device into bootloader and using customRUU to load ur favorite ROM
Click to expand...
Click to collapse
What do you mean? take out battery?
Gonna try this with my next flash

Yeah, the sentence is a bit odd to me to
i asume it means take out battery but still..
i'm not gonna try it until i know it for sure!
--edit--
i couldn't help it and used it anyway..
i assumed "take our batti" means take out battery cuz it worked for me!
my diamond was clean (i guess) and i'm now enjoying a new rom!
Thanx guys!!

I would never post something that I did not test first.
I am glad that you liked it, and I really think it is much simpler then the mitty thread.
Good luck flashing.

rapidshare
first would like to give thanks for sharing this one but some people cannot use rapidshare links and unluckily I am those few
can you give alternative link like mediafire ????

character said:
first would like to give thanks for sharing this one but some people cannot use rapidshare links and unluckily I am those few
can you give alternative link like mediafire ????
Click to expand...
Click to collapse
http://www.mediafire.com/?jabdu2n968xa9uk here you are

I LOVE THIS TOOL
this isn't good for my ORD.. i'm flashing the hell out of my diamond now!
Getting a HD2 in about a month.. can't wait for it ;D

I tried it, but I only get the start screen with "Touch diamond", no bootloader.
But I´ve installed HARDSPL Olinex, because I already flashed other ROM´s.
How can I solve this problem?
What about battery? When I have to get it out, when I can put it in again...?
fibula

to get into bootloader you have to reset your device while holding the volume down button!
then you will get the tri-color screen,
connect your diamond to your pc and flash a rom with a RUU!

fibula said:
I tried it, but I only get the start screen with "Touch diamond", no bootloader.
But I´ve installed HARDSPL Olinex, because I already flashed other ROM´s.
How can I solve this problem?
What about battery? When I have to get it out, when I can put it in again...?
fibula
Click to expand...
Click to collapse
To get into bootloader with my diamond:
1) Turn Diamond off, take out battery for 5 seconds.
2) Put battery back inside, and press and hold the centre button (circle) and turn ON the device (hold both buttons) until you see a 3 colour screen
If step 2 does not work, try pressing holding volume down while turning the device on (hold the ON button too). Remember to take out the battery before you do this.
Hope this helps.

Hi!
Does this work by simply copying any ROM's nbh file (instead of radio*.nbg) to folder and executing ROMUpdateUtility.exe? Will it MTTY before flashing the ROM?
Currently I'm trying this method out. It is around at 50% of flashing progress.
I'll report back.
Cina.

thanks a ton dude.... magnificent work...

Now if there were only a way to do it directly from Internal Storage, without RUU...

It does not work the way I described. It hangs on HTC Diamond black boot screen and no red lines appears in lower right corner (no OS recognized).
So you have to flash 2 times. Radio flash is shorted for the first attempt and on the second turn you flash your ROM with CustomRUU.
There is a similiar tool like this with the method working with other devices I described above. FlashaholicRUU. Someone give it a try for Diamond. Next week I'll do it and report back.
Cheers,
Cina.

cina said:
It does not work the way I described. It hangs on HTC Diamond black boot screen and no red lines appears in lower right corner (no OS recognized).
So you have to flash 2 times. Radio flash is shorted for the first attempt and on the second turn you flash your ROM with CustomRUU.
There is a similiar tool like this with the method working with other devices I described above. FlashaholicRUU. Someone give it a try for Diamond. Next week I'll do it and report back.
Cheers,
Cina.
Click to expand...
Click to collapse
I remember to see that post on xda developers front page short time ago, but I was not sure if it would work for HTC Diamond.
A universal task29 that would format and flash the device in one single process.
Ironically it was developed a few weeks after I have found an alternative way to mitty that I posted here.
So far I did not hear that it was compatible with Diamond, so I will not risk it.
It's nice to have all these options, because when I searched for something like this a few months ago, I could only find the mitty threat that has more than 80 posts.
For me it was strange as newer devices with very similar hardware and software already had something like this, but Diamond users had to use mitty.
Well I am glad that you like it, and hopefully I helped someone that was not able or willing to do it manually.