I recently installed 3VO's Windows Mobile 6.5 ROM and i used it for a few days
Then i started having problems with it sowing down so i tried to get another ROM
But everytime i tried to install a new ROM my computer would say "The system cannot find the path specified "Excalibur<Dopod C720/720w, HTC S620/S621, T-mobile Dash> ROMUpdateUtility
I tried installing the official ROM back on to my phone and it worked
But now when i try to flash any other ROM's my compuer gives me that msg again.
I need a updated ROM because i have a 4gig SD card and it is not compatible with the Official ROM
Can someone please help me with this Problem???
Are you remembering to Application Unlock your phone prior to trying to update again?
yea i run the SDA application unlock and the screen comes up and i click remove lock
Then when i run the ROM update
it gives me that msg again
Are you making sure during the FLASHING process to click the center button on your phone to initiate the flashing mode?
---At one point after the cmd file copies and runs some files on your phone, it will tell you a disclaimer about flashing and ask you if you want to proceed. There is a button that says YES, you click the center button and then you enter the 'bootloader'/flashing mode (to my understanding). Someone else had this issue...they forgot this and that messed them up...
when i begin flashing it shows that msg
And when it gets to the step that your talking about my phone doesnt react and show anything at all
Related
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???
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.
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.
Hi folks!
I got the Wildfire S from my Mum and flashed it to 3 different Custom-ROMs.
the problem is, her phone has an error. Everytime when waking up from standby, it takes like 5 seconds before the display does take input!
Means : When someone calls and the display went on, u have to try many times (like 5 secs or more) to receive the call. same when trying to unlock.
With stock rom it was even worse! there it took like 10 seconds or more.
now we want to flash back original rom without root and take it back to our dealer and let it change with a working phone. problem now is, the USB-Ports seems to be broken or so??
when connecting with her laptop or even with my PC the pc's recognises the phone as "unknown device" and when trying to install usb-drivers for asb or fastboot, it says "the device is already up to date".
so i CANT use fastboot, adb or even the RUU-flasher-exe files
no i am searching for a way to flash the phone with a stock rom out of the recovery menu.
is there a way or a way to fix the usb-driver problem ???
someone plz help!
i installed htc sync and tried to flash the ruu manually by fastboot.
it only flashes system.img and the boot.img. when trying to flash the other stuff like hboot and recovery or radio it says "wrong verficiation id. Remote not allowed"
now the phone wont boot further than bootloader or recovery
bootloader is unlocked!
plz someone help!!
Is there a way to flash a stock rom out of the recovery?
can SOME PLEASE make me a backup of his system and upload it anywhere so i can fix mum's phone?
plz ppl help!
ok got it back working. with custom rom only, but its ok for now.
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
read carefully
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
XicoBombas said:
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
Click to expand...
Click to collapse
so weird
Ratchewer said:
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
Click to expand...
Click to collapse
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Try this here
ok go back to the original phone stock rom from the service provider and start over. use the usb bootloader mode after run the xda applicationunlocker file and do the cid bypas. then run the utilityupdate from the other rom ( not the one in the cid bypas file in the link) meaning do not click yes to the windows security prompt skip and run the romm u want to use
XicoBombas said:
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Click to expand...
Click to collapse