New Dash, Trouble flashing to WM6.1 *please help!* - HTC Excalibur

Alright got a new dash and carefully began to flash to 6.1 from 5.0.
I first did a hard reset.
Then ran the app unlock.
Reset device.
Downloaded Ricks WM6.1 and ran the auto.bat
Followed instructions.
Screen turns white.
Run the ROM updated.
ERROR: Connection or something..
Turn off device and enter boot mode by holding camera.
Downloaded the Dash_Software_Update_1.22.531.4.exe and ran it succesfully
Phone wont turn on at all..
I can enter boot mode though with the camera button.
What should I do? The original dash software doesn't even seem to install correctly and I cant CID unlock because I can only boot into the tri-color screen. Help is much appreciated.

T-Mobile wm6 ROM
proph3t said:
Alright got a new dash and carefully began to flash to 6.1 from 5.0.
I first did a hard reset.
Then ran the app unlock.
Reset device.
Downloaded Ricks WM6.1 and ran the auto.bat
Followed instructions.
Screen turns white.
Run the ROM updated.
ERROR: Connection or something..
Turn off device and enter boot mode by holding camera.
Downloaded the Dash_Software_Update_1.22.531.4.exe and ran it succesfully
Phone wont turn on at all..
I can enter boot mode though with the camera button.
What should I do? The original dash software doesn't even seem to install correctly and I cant CID unlock because I can only boot into the tri-color screen. Help is much appreciated.
Click to expand...
Click to collapse
Put T-Mobile's wm6 ROM back on your device and start all over again.

proph3t said:
Alright got a new dash and carefully began to flash to 6.1 from 5.0.
I first did a hard reset.
Then ran the app unlock.
Reset device.
Downloaded Ricks WM6.1 and ran the auto.bat
Followed instructions.
Screen turns white.
Run the ROM updated.
ERROR: Connection or something..
Turn off device and enter boot mode by holding camera.
Downloaded the Dash_Software_Update_1.22.531.4.exe and ran it succesfully
Phone wont turn on at all..
I can enter boot mode though with the camera button.
What should I do? The original dash software doesn't even seem to install correctly and I cant CID unlock because I can only boot into the tri-color screen. Help is much appreciated.
Click to expand...
Click to collapse
I think you will need to upgrade from WM5 to WM6, then flash again up to WM6.1 ... been doing this a while now and have never seen much success with jumping generations.
I'd guess this is because of IPL/SPL versions.

Related

PV HERMES Rom Expired????????

Hello.
I have installed a PV Hermes WM 6.1 Rom.
It now says : thank you for using this software...etc
I think it was for betatesters, and now it shows only a splash screen, and i CANNOT install another ROM.
I tried to install by starting in BOOTLOADER, but it does not help.
What can i do???
emipop said:
Hello.
I have installed a PV Hermes WM 6.1 Rom.
It now says : thank you for using this software...etc
I think it was for betatesters, and now it shows only a splash screen, and i CANNOT install anothor ROM.
I tried to install by starting in BOOTLOADER, but it does not help.
What can i do???
Click to expand...
Click to collapse
I think I read somewhere (but have not tried), do a hard reset, and when the screen that says Tap to begin using your device pops up, start attempting to flash from there.
But they "should" flash from the bootloader screen.
I had exactly the same problem. Tried all the tricks to go back to the previous ROM. I also tried boog321's hard reset idea, but it just puts you back into the bootloader. HOWEVER, when I then went through the screen alignment process (just for fun), lo! it works!
The problem is that i can`t get inside windows anymore. It stays at the screen 3 seconds after power up. Is there a way to hardware reset?
emipop said:
The problem is that i can`t get inside windows anymore. It stays at the screen 3 seconds after power up. Is there a way to hardware reset?
Click to expand...
Click to collapse
Just flash a different rom dude!! probably a expired beta rom.
i have tried to falsh 4 differnt ROM`s. It makes 2% and says rom orrupter or something.
Tried installing via MicroSD card? I installed the same ROM a while back...
Hey. I just re-flashed right now after I installed an expired beta by mistake.
Start with the Hermes connected USB, showing the splash out of luck screen.
1. Hold both Power and the ok button on the left and then RESET with the stylus. It should go in tri-color mode
2. Flash a known good ROM
Good luck!
Bro just flash your ppc using other ROM (flash it in bootloader mode) when its in the hermes rom upgrade tap the (force using safe SSPL) it will do the trick.
I already said i did that.
After 1% it stopped and says : ERROR 270. UPDATE ERRROR: The image file is corrupted please check your update utility.
I have done this with 5 roms now.
Will try microsd install.
Hope you have Hard SPL, you need it for sd card flash...
I solved the problem with the bad ROM.
I downloaded an official rom from here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
I has done a clean install.
But i still can§t install another rom, from the forum.
Will try again.
emipop said:
I solved the problem with the bad ROM.
I downloaded an official rom from here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
I has done a clean install.
But i still can§t install another rom, from the forum.
Will try again.
Click to expand...
Click to collapse
Are you sure you have HardSPL installed and CID unlocked your device?

HELP! - Cannot flash bootloader away from SPL-0.41.coke

I have a major issue here. Please bear with me.
I flash my phone to the official 6.1 rom a few months back. Now I recently decided to try a custom rom by NFSFAN. So first thing was to flash the bootloader by IMCokeMan version 0.41. After doing that I flashed the custom rom. Once it booted up my phone kept reboot itself every few seconds or so. It turns out now that it was a battery issue, but I was sure the battery was fine and thought it was simply an incompatibility issue with the rom.
So I then tried to flash the official 6.1 rom back on, but it froze at 44% and then threw a 262 error after a minute or so. I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Then I thought I'd try the NFSFAN's rom again. So I flashed that. Once it successfully finished and started to load it freezes at the Telus splash screen and "No Radio" appears in red on the screen.
So this is where I'm at. I've tried to flash nearly every bootloader I could find and no matter what I do the bootloader always shows "SPL-0.41.coke". I can't flash any official rom including Telus, Bell or Sprint as they each freeze at different spots but consistently at the same spot individually (Telus at 44%, Bell at 30-some%, Sprint at 29%). I can flash custom roms as well as the beta wm6.5 rom but those don't fully load and give the "No Radio" error.
The ONLY rom I can successfully flash is an old 6.0 rom that someone dumped from a telus vogue. But in this rom under "Device Information" the rom is 1.11.661.1 and the radio version field is blank! And I cannot make data connections, as in I cannot connect to the internet, etc.
So my question to anyone that may know is: why am I having these issues with the radio version? How can I get rid of the SPL-0.41.coke bootloader?
And what can I do at this point? Any help from anyone is a thousand times over appreciated!
There's another copy of this thread at PPCGeeks.com:
http://forum.ppcgeeks.com/showthread.php?p=792095#post792095
-Chris
*********** bump-a-doo? *************
eeps! similar issue! did I brick it???
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
cbstryker said:
I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Click to expand...
Click to collapse
I've been reading through the ImCoKeMaN's unlocker sticky (http://forum.ppcgeeks.com/showthread.php?t=20370), and I noticed there is a "VERY IMPORTANT / Warning" referring to the 0.40 rom you used. Here's what it says:
If your carrier did not release a rom and you flash an exe of another carrier with the 0.40 unlocker you won't be able to flash ANY rom until unlocking again (this requires booting into WM)
Click to expand...
Click to collapse
then it points to this: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
Hopefully that helps you out.
esskay said:
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
Click to expand...
Click to collapse
hey, I answered this question of yours already over here http://forum.xda-developers.com/showthread.php?p=3526872#post3526872
Detroit Doug
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Viper Matrix Wireless said:
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Click to expand...
Click to collapse
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Detroit_Doug said:
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Click to expand...
Click to collapse
I answered his question on his thread. You forgot one thing though Doug. He doesn't have a radio. He'll need to flash back to stock before he flashes a custom. Doesn't this get frustrating???

Please help!!

i just loaded a new rom onto my diamond. after installation the phone turns on and displays touch diamond then sits there for about 20 seconds then reboots. its keeps doing it. what can i do?!! ive tried loading another rom but it seems to keep doing it.
When you put you phone into bootmode, does it still restart then?
And have you tried a hard-reset?
it did stay in boot mode, but once i loaded a new rom it did the same thing. i had to load a couple roms before it stuck and started working. thanks for your help.
bigk05 said:
i just loaded a new rom onto my diamond. after installation the phone turns on and displays touch diamond then sits there for about 20 seconds then reboots. its keeps doing it. what can i do?!! ive tried loading another rom but it seems to keep doing it.
Click to expand...
Click to collapse
Maybe this link will help to solve the problem: http://forum.xda-developers.com/showpost.php?p=3433851&postcount=22
Option 2:
If the link above method doesn't work for you, then just simply but your device into bootloader and flash a stock ROM then go back to a cooked ROM and everything she be ok.
Go Here to Find Stock Roms It doesn't matter which one you chose as the goal here is to remove the bloated ROM which happens from too many flashes.
hi, i know this post is a little old but MY DIAMOND IS DOING THE SAME EXACT THING!
i just started leaerning how to do all this, and the only HardSPL that worked on my phone was 1.24.
i updated to that spl, then i upgraded the radio but when i did the rom flashing event i am left with a messed up phone, resulting in only turning on and off, not getting past the touch diamond screen.
PLEASE HELP ME.
Guide to completely restore your messed up device
This little guide is made for newbies who are stuck after flashing images in a wrong way or flashing wrong things.
Note: This is only for GSM Touch Diamond!
This Guide does not include the MTTY Procedure!!
Q. What does this mean?
A. Well, if you are still facing some problems after following this guide, it's time to use MTTY.
Q. what is MTTY?
A. It's a flashing procedure before flashing a ROM, it actually formats your phone (you internal storage will not be lost) and then you are able to flash a ROM.
Q. When do I have to use MTTY?
A. You have to use it before every ROM flash. Before you proceed with step 14, you must read this! It's the only step you need to do it, except for the latest cutsom ROM flash.
Perform a hard-reset (Hold Center button + reset)
Go into bootloader mode by holding volume down and pressing the red reset button
A red-green-blue-white screen will appear. In the white part of the screen, there should be the word 'Serial'
Connect your phone to the computer.
If the word 'Serial' changes into 'USB', you succesfully connected your phone
Go to this link and download 'Unsigned-Hard-SPL-Diamond-OliNex.zip'
Extract it to an empty folder.
Run RomUpdateUtility.exe, make sure your phone is still connected
Follow the steps, check device for prompts after PC shows loading bar. it should go to black screen now.
SPL flashes, device automatically reboots, job done.
to confirm you got it installed, go into bootloader mode and verify the screen shows 1.40.OliNex.
note: you will not see the SPL version during normal boot, that is the OS version, not SPL!
Now you have re-flashed Hard-SPL, it's time to flash a stock ROM.
Make sure your phone is connected again
Download a stock rom (ie from here) and run the executable.
Follow the instructions, and be patient.
You're done now. You are now able to flash a custom ROM of your choice.
If you can't get your device to work, not my problem! If this didn't help your device is bricked. You'll have to return it to HTC.
And of course I am not responsible for any trouble you get with this guide.
Don't you understand some steps or do you still need help?
Try reading this. It is a great tutorial about flashing your device including the MTTY procedure.
If you still can't get a clue of it don't hestitate to PM me!
You can also add me to msn, see the msn icon to the right of my post.
when i tried to upgrade to 'Unsigned-Hard-SPL-Diamond-OliNex.zip' the progress bar on my phone and the computer go up to 100% in less than 2seconds, then it says 'error [270]: update error
the image file is corrupted. please check your update utility'
And on my devices bootloader screen it says 'upgrade ROM code error please try again'
devyn_ciara said:
when i tried to upgrade to 'Unsigned-Hard-SPL-Diamond-OliNex.zip' the progress bar on my phone and the computer go up to 100% in less than 2seconds, then it says 'error [270]: update error
the image file is corrupted. please check your update utility'
And on my devices bootloader screen it says 'upgrade ROM code error please try again'
Click to expand...
Click to collapse
Are you using Vista? If so, try it on another computer
Another problem could be that the package is corrupted. Try downloading it again.

Apparently I have severly bricked my S620.

I was attempting to change to ookba's 3VO ROM but the operation failed and the ROM did not install. I did get the recovery instructions screen and followed them but the phone did not reset to the previous ROM (NRGZ28's EnergyROM 52409). The phone hangs on the Windows Mobile screen. I have done the following -
1) Followed ookba's recovery instructions and gotten the tri-band screen. However whenever I try to flash back to the T-Mobile ROM (any version) I get Error 260.
2) Followed stylez hard reset instructions and gotten the reset screen but the phone hangs on the Windows Mobile boot screen. A hard reset does not occur.
3) Followed NRGZ28's "In Case Things Go Wrong" instructions and gotten the tri-band screen, however when I try to flash the EnergyROM (or any other non T-Mobile ROM) I get corrupted image errors.
4) I have used jockeyw2001's bootloader but get Error 260
Also, the power button does not turn the phone off. I have to remove the battery to get it to shut down. I think I have tried all the recovery steps I know if. If anyone has a suggestion or solution I would be most appreciative. Thanks.
The Rotagilla said:
I was attempting to change to ookba's 3VO ROM but the operation failed and the ROM did not install. I did get the recovery instructions screen and followed them but the phone did not reset to the previous ROM (NRGZ28's EnergyROM 52409). The phone hangs on the Windows Mobile screen. I have done the following -
1) Followed ookba's recovery instructions and gotten the tri-band screen. However whenever I try to flash back to the T-Mobile ROM (any version) I get Error 260.
2) Followed stylez hard reset instructions and gotten the reset screen but the phone hangs on the Windows Mobile boot screen. A hard reset does not occur.
3) Followed NRGZ28's "In Case Things Go Wrong" instructions and gotten the tri-band screen, however when I try to flash the EnergyROM (or any other non T-Mobile ROM) I get corrupted image errors.
4) I have used jockeyw2001's bootloader but get Error 260
Also, the power button does not turn the phone off. I have to remove the battery to get it to shut down. I think I have tried all the recovery steps I know if. If anyone has a suggestion or solution I would be most appreciative. Thanks.
Click to expand...
Click to collapse
Maybe its safe to assume you have a hardware issue? Since the initial flash and following consecutive flashes failed, maybe its a bad USB cable? I would try reflashing the shipped T-Mobile ROM from a different PC altogether using a different USB cable. Since your phone gets to the Bootloader (multicolor) screen means it's not bricked. Try different PC and cable hardware...
Will do. I did try another hard reset and the boot screen has sat for over 20 minutes without getting past it.
Or try flashin stock ROM via SD
you must flash to official rom to make any progress at this point. at least thats what i had to do when my computer auto-restarted in the middle of one of my flashes.
Fixed, thanks for the help.
bricked excalibur
how did you fix it cause i'm having the very same problem
Switched from a PC running Windows 7 to one running XP.
muga said:
how did you fix it cause i'm having the very same problem
Click to expand...
Click to collapse
Welcome to the forum
Also reading here would help http://forum.xda-developers.com/showthread.php?t=415225
Well that didn't work for me its stuck it the multi colour screen and pc not flashing it. When it does recognise and start to flash i see a count down screen like the one on pc but only stops at 3percent
muga said:
Well that didn't work for me its stuck it the multi colour screen and pc not flashing it. When it does recognise and start to flash i see a count down screen like the one on pc but only stops at 3percent
Click to expand...
Click to collapse
Muga, It's also happening to me. I had previous flashes with different roms Kavana's, rose, energy (6.1 release) and everything went well with no problems at all. But a few days ago, I tried to flash my excalibur with the latest release by NRGZ28 (energy rom 6.5) and what I think what happened was that I didn't run the unlock file aplications (since I didn't have to do it in the other flashes, because I already had unlock the phone with the first upgrade) that's the only explanation I can get. At the end, I came up with the frozen screen and I've tried the bootloader steps, original rom installation, hard reset with no succes at all. What I get is the same error you have.

Vogue Stuck at Colors Screen

Ok so i just recently got a Verizon XV6900 (Vogue), i tried flashing the NFSFANS wm6.1 and wm6.5 roms but both of these would constantly cause my device to reboot if it wasn't plugged via USB. So i tried reflashing it back to the original 6.1 pro that came on the phone by using the one from the HTC Website, that failed after 31% and i had to recover it. Now the device is just stuck at the screen with the 3 colors with the message
Vogu100
SPL - 2.01.0000
CPLD-3
i have no idea what to do to get out of this, sorry I'm a complete noob and I tried searching but I couldn't find what i was looking for
Any help is appreciated
Your Vogue is not unlocked. Try running the unlocker (.40) again. Once that is done, unlock using the 2.31 unlocker. You should then be ready to flash a custom ROM.
EnZandOutZ said:
Ok so i just recently got a Verizon XV6900 (Vogue), i tried flashing the NFSFANS wm6.1 and wm6.5 roms but both of these would constantly cause my device to reboot if it wasn't plugged via USB. So i tried reflashing it back to the original 6.1 pro that came on the phone by using the one from the HTC Website, that failed after 31% and i had to recover it. Now the device is just stuck at the screen with the 3 colors with the message
Vogu100
SPL - 2.01.0000
CPLD-3
i have no idea what to do to get out of this, sorry I'm a complete noob and I tried searching but I couldn't find what i was looking for
Any help is appreciated
Click to expand...
Click to collapse
just plug it back in and try to reflash the stock ROM. don't open any programs on your computer while you are flashing. i tried to open a media player to listen to music and it froze the RUU. just flash it again it worked for me.

Categories

Resources