Error [244]: Invalid Model ID, on flashing a PTB rom - HTC Excalibur

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

Related

JASJAR always go to bootloader mode - how to fix it?

I downloaded the Dopod 900 rom, wishing to change my PPC into Traditional Chinese. But after running the no id exe file. It reboot my PPC and said the country ID is not correct.
Afterwards I run the bootloader.exe on JASJAR. And it automactially go to bootloader mode. I'm able to upgrade my PPC rom. But after the cold reboot the system go to bootload mode (ask me to insert serial or USB cable). How can I get PPC work?
you always have to start your device in bootloader mode manually before upgrading.
as you didn't, special bit in the device was set, to start it always in bootloader mode now.
rerun the upgrade with MaUpgradeUtil_noid.exe again. it will fix it.
buzz
I got the same problem after upgrade to a new version complately but always still on bootloader mode,I have rerun the upgrade but still got same problem.Help please.
Reset while holding the power button
xdaIIse said:
I got the same problem after upgrade to a new version complately but always still on bootloader mode,I have rerun the upgrade but still got same problem.Help please.
Click to expand...
Click to collapse
Reflash the Jasjar again. But use the Radio Rom 1.04.02 only. Then do a reset.
Is here nobody who can read?!
Here is the answer how to solve the problem:
http://forum.xda-developers.com/viewtopic.php?t=33191
Or if you're unable to open the link:
make the update w i t h o u t any card (sd-card and sim-card) and you'll see: it works. Maybe you've to run the update twice without changing anything!
Teja
Hi,
I had a similar problem, system and unit both indicated a successful ROM flash but after the reset remained in bootloader mode ("Serial v1.00).
In the end I did a final JasJar ROM flash, then did the radio only ROM flash and after radio done, a reboot worked.
Maybe try the 1.04.02 radio only ROM flash and see if that works.
Note: during the last two ROM flashes I too had removed the SIM and SD cards.
Note: I had removed the SIM and SD cards for a number of ROM flashes prior to that, so I know how you feel finding out that wasn't the quick fix I read. But try all that in combination.
Regards
Michael
most of the time reviving a dead universal is easiest with another rom upgrade of the radio flash.
If your universal boots in usb mode (bootloader), I can confirm your universal is dead. Mostly caused by using an upgrade program that was not made for the universal. For instance using a cracked magician upgrade program to force universal upgrades. In most cases this will get you a dead universal which can easily be repaired by doing an aditional radio rom upgrade (even if you already have that radio upgrade)
Hi,
I can confirm that in the 2 instances of bricking my device (unable to get out of bootloader mode) that the radio only upgrade (1.04.02) got it working again.
I've done this for both the JasJar and Qtek ROMs (currently running Qtek).
My unit is a Dopod 900 originally purchased in Taiwan.
Regards
Michael
i had the same problem with the QTEK of my principal after I upgraded his ROMs.
(after the hard reset, the pocket remained in bootloader mode).
you can solve this problem in a very simple way:
you have to launch the bootloader installation (BL1.01_RUU_UNI_V.1.2.EXE) from the PC (still connected with the PPC through USB) while the PPC is in bootloader mode (on your display you see "USB > Serial 1.01" or something like that).
then you do a SOFT reset and the pocket boot normally.
very simple.
i hope to be helpful to someone.
Yep, i agree with u parallel666killer, it worked by just reinstalling the bootloader (BL1.01_RUU_UNI_V.1.2.EXE).

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!!!

Ok, I'm with Bell mobility, had nsf's 6.5 rom installed. I had t osend my phone in for repair, so I needed to downgrade.
I read the instructions and put the coke 0.41 unlocker on, Now I try putting on the original bell rom and it stops at 31% and says theres a error.
What I've tried
-Restarting the rom, keeps erroring at 31%
-Tried the unlocker again, says no device connected
-Tried the 2.31 unlocker still says nothing connected
Somebody please help
Why do people keep using the .41 unlocker? That is for non-gps devices.
You need to flash the .40 unlocker, then the stock ROM.
Flash from bootloader (Power+ Camera button, and stylus reset)
Thanks for your quick response, I got it back up by putting the custom rom back on, but as you just said the wrong unlocked
where would i get .40
I found 0.40
Now do I just downgrade the unlocker, let it restart the device and everything it does and then install the stock rom?
Yep.
10chars
ok so I installed 0.40, and then the stock rom
It stopped at 31% again, I followed the recovery, removed the battery and it went back to stock!!!
Thanks
ok have a new problem, Now it turns on, Gets to the today screen and I get the error "\windows\ppst.exe does not exist" And it won't let me do anything, have to take the battery out
You're going to want to flash it again. It should have gone all the way through. ppst.exe is loaded during customizations.
Ok, so now activesync won't connect, so it won't let me flash the rom again
my internet won't work on it, I'm guessing it has to do with ppst.exe not installing.
What should I do now
Put the phone into bootloader, then flash. Don't worry about activesync right now.
Ok so heres an update. I finally got the .40 unlocker working and reinstalled the original rom, but it said PPST.exe was missing. I tried a hard reset and it still said PPST.exe was missing from \Windows
I tried again to reflash the original rom that I downloaded from the htc website for bell and still got PPST.exe is missing.
I installed 2.31 unlocker and put nsf's wm 6.5 on and everything works fine
But I need to know why PPST isn't working so I can replace the original

[Q] Problems with bootloader [SOLVED]

I had 3.29 HardSPL, i used Android on nand for quite some time, after that i decided to flashed back to WinMo to check something out, in one of the guides, it told me to put the kaisimg.nbh and kaisdiag.nbh, (i had flashed back to WInMO several times but never included the Kaisdiag.nbh, since the guide mentioned it i thought it was something good to do)
i used the official WM6.1 and entered bootloader as usual... then my device reset in the middle of flashing...
When i tried again bootloader got stuck at 'Loading...' and the bootloader was now showing 3.34.000
Now i am unable to flash the windows ROM or HardSPL as they all got stuck in the bootloader at 'Loading...' also tried with bootloader in USB mode... nothing
Please help me... thanks in advance
BTW, luckily the android kernel was still functional and i can use it for now...
I posted this in the TyTn General Discussion section but since i got no reply for days, i reposted it here, so sorry in advance for the double thread.
Put the kaiser in boot mode, connect to a pc and flash an original rom from windows. Then reflash hard spl.
l1q1d said:
Put the kaiser in boot mode, connect to a pc and flash an original rom from windows. Then reflash hard spl.
Click to expand...
Click to collapse
Thanks for the reply... i tried this, dont know if i did something wrong but it still got stuck, i used the stock 6.1 asian, it was originally a swedish kaiser so do i need that particular rom?? i will try again...
I tried RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.rar but while it was flashing, it got to 1% on the computer and then the device just resets
It said Error [294]: Invalid vendor ID
the update utility could not be used for your PDA phone on my PC
Finally solved... i went to htc website and downloaded the update using my phones serial number... i successfully flashed back to WinMo using that ROM... now i can use hardspl again... thanks for all the help

Categories

Resources