Database Info

Help me please!!!

Tell me what Im doing wrong. I did the hard spl first and then I downloaded the rom I wanted to use. I extracted the rom and started it up and followed all the steps on the screen. It said that it successfully installed the rom and restarted my phone. Then it takes me to the screen where i have to align my screen so I did that and set up the device. then the home screen loads up and then its starts the customization process. When thats finish it restarts the phone again and then after the second splash screen it freezes and eventually my screen looks like the static on a television. Ive tried to go into bootlegger mode and reflash it and it does the same thing. Ive also tried to hard reset it when I get to the screen alignment screen because I read that in wiki and it still does the same thing. Im so lost what should I do. Thanks for your time and help.

If you CID unlocked it properly then reflash to the OEM rom and then try to reflash the ROM you want. Anybody disagree?
-McMex

It can also be aRADIO prblem that doesn't match with the ROM,
check this and try to replace the RADIO.
Ciao.

mcmexican said:
If you CID unlocked it properly then reflash to the OEM rom and then try to reflash the ROM you want. Anybody disagree?
-McMex
Click to expand...
Click to collapse
Agree. If the OEM Rom doesn't work either, i'm betting on the CID Unlock having failed.
And... you do have a Kaiser, don't you?
One more note: next time you open a thread, try to at least come up with a decent topic title..

Confirmed... It is a radio conflict, I had the same problem after flashing a wrong radio by mistake..

change radio. click my link below and go to the radios folder and pick one. the new ones only work w/ 6.1 roms though.

Flash - What Went Wrong?

I've always fancied flashing my Kaiser (V1615) with a new ROM, but was always nervous because I wasn't sure of the process and didn't want to risk bricking the phone as well as all the effort needed to get everything back on it I needed. Well, a few days ago my old Kaiser met the floor and an untimely end. So I decided to take the risk and put a new ROM on it and decided on the latest Dutty WM6.1 ROM.
I read all about flashing on here and made as much sense of it as I could. Thing is, I'm very technical in general, but not very familiar with Windows Mobile or flashing. I found there was lots to read, but it was all written with an assumed level of knowledge and understanding of terminology. As a result I found it quite hard to understand. I took the plunge anyway and started, but things didn't work out as expected and I didn't understand why.
I'm not trying to be critical of all the work a lot of people have put into the documentation that is available online, it's just that when I originally approached this with zero flashing experience I found it difficult and confusing to understand. What I really needed was a concise and basic introduction to flashing. I've now been through the process and after re-reading the documentation it makes a lot more sense.
I worked out you need to run something called HardSPL before you could flash a new ROM. I'm still not sure what HardSPL does apart from CID unlock the device, but what does CID unlock mean?
I ran HardSPL v1 and it started ok, but then I ended up with a white screen. At this point I already wished I hadn't started, but no going back now. Is it known why some phones white screen? Turns out it's a common problem, so followed the instructions to recover. All was well again, but still with the original ROM.
I thought I'd be brave and stuck with it and this time tried JumpSPL1.56-KAIS instead of HardSPL as recommended on one of the tutorials. This went better and I ended up with the Tri-Color screen. I plugged my USB cable in and USB showed on screen.
Next step I thought was to flash a ROM onto the device. I ran the Dutty updater on my PC and all started ok, but when the update got to 18% I received a communication error. I tried to recover using the updater, but the same thing happened. At this point the phone wouldn't boot, so I was more than a little worried and wishing I hadn't started!
Found something that described several options for recovering from this problem. I decided to try and flash the device back to the original ROM from Vodafone. When I eventually found that ROM I ran JumpSPL again, got to the Tri-Color screen and ran the updater. This time the update completed successfully and the phone rebooted and was all working again.
I decided to leave the device as it was and started customising it myself. I'd still love to put a cooked ROM on there, especially if it helps with performance, but after the experience above I'm not very confident.
Can anyone tell me where or what went wrong? I'm going to get my old Kaiser repaired and want to try again on that phone.

My flashing routene (not ideal but it works for me)
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
2) after device reboots, hold camera button and restart to check SPL
3) Flash rom/radio of choice
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Sam

Wow, I need a cuppa now
I'll go through 1 at a time... (and Sam has answered some questions already)
-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave

Thanks for the advice, but this is what I normally encounter when I read something on here, which is advice which no doubt makes perfect sense to the author or others experienced in flashing, but usually raises more questions than it answers in my head.
For example;
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
Click to expand...
Click to collapse
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
2) after device reboots, hold camera button and restart to check SPL
Click to expand...
Click to collapse
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
3) Flash rom/radio of choice
Click to expand...
Click to collapse
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Click to expand...
Click to collapse
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?

BTW, not trying to moan about everything, just posting my experiences to find out where I went wrong, but also highlight some issues hopefully other flashing newbies can relate to and authors of tutorials can draw some useful feedback from.

Only one question, do I need to CID Unlock before using Jump and HardSpl or, the Hardspl does the Supercid ?
I'm not referring about SIM since I don't care, for now
With WM6.1 - Oficiall HTC ROM
Thanks

Thanks for that one dave, on reflection i kinda missed the whole point of the thread, and as for the majority of the stuff you posted i didnt undertand that to begin with.
Also, DaveTME, if you are wanting to flash a custom rom to youre kaiser. from my experiance and from the number of times ive seen this happen. i advise against asking for reccomendations(sp?) (not saying you will but its worth saying) try a few roms out and decide from there.
Also another thing to note. if you flash to WM6.1 remember to use a 3.xx spl otherwise you'll encounter a few problems with youre device.
Sam
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
Click to expand...
Click to collapse
download the Kaiser unlocker and run the first stage of it, the program is in the linked thread.
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
Click to expand...
Click to collapse
No, after the device reboots, youre given youre Rom, Protocol and Radio. if you hold the camera button and reset you'll get youre SPL displayed, youre looking for 1.01 olinex to be shown
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
Click to expand...
Click to collapse
1) Yes, just run the RUU with youre chosen rom and thats it
2) its not a minefield, just make a decision on what rom you like and flash it. theres nothing to stop you flashing another one.
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?
Reply With Quote
Click to expand...
Click to collapse
The 1.01 SPL will allow you to flash a cutom rom. following that you need a 3.xx SPL as they are designed for windows mobile 6.1. as for yure decision. i use 3.29, yet other users have had better sucess with 3.56. Most rom chefs will say which SPL they reccomend anyway with their rom.

-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
Click to expand...
Click to collapse
Great. Thanks for that. Makes perfect sense now
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
Click to expand...
Click to collapse
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave
Click to expand...
Click to collapse
Thanks, will have a read

DaveTME said:
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
Click to expand...
Click to collapse
Read the "SPL Questions" Wiki Page, it is all there and fairly clear.
Ta
Dave

Kaiser stuck on custom ROM, cannot update ROM or Radio, Tried EVERYTHING!

Hi, I have a Tilt with PDA Corner Ultimate V.10,
Hard SPL 3.29,
and radio 1.27.14.09 (AT&T Stock)
The radio is causing the phone to have no sound, but everything else works fine. I know this problem is common, but I have tried everything within my ability and cannot get it to flash to any other ROM or radio.
When flashing a new ROM or radio, it shows the current version and update version, but never gets past 0% without a 262 error
I have tried all of the solutions I found posted on the forum, (Jump SPL, MTTY, EVERYTHING) trust me i've searched and read and searched more, I am not a newb to this although my post count is low.
Is there anyone with this particular problem on this particular ROM/radio combination that can help me out?

da_truth540 said:
Hi, I have a Tilt with PDA Corner Ultimate V.10,
Hard SPL 3.29,
and radio 1.27.14.09 (AT&T Stock)
The radio is causing the phone to have no sound, but everything else works fine. I know this problem is common, but I have tried everything within my ability and cannot get it to flash to any other ROM or radio.
When flashing a new ROM or radio, it shows the current version and update version, but never gets past 0% without a 262 error
I have tried all of the solutions I found posted on the forum, (Jump SPL, MTTY, EVERYTHING) trust me i've searched and read and searched more, I am not a newb to this although my post count is low.
Is there anyone with this particular problem on this particular ROM/radio combination that can help me out?
Click to expand...
Click to collapse
Maybe this is another one of those 'Radios from Hell' that won't let you upgrade. Note this quote from Ultimate Radio Thread:
Originally Posted by jockyw2001
A new sort of "Radio from Hell" emerged for the Diamond. See here. It combats rom updating by preventing us from running a SSPL.
A clear advice to all is: always make sure you have HardSPL installed and your device is security unlocked before installing a new radio !!
Also, maybe something in this thread will help you...
http://forum.xda-developers.com/showthread.php?t=393337

Thanx for your quick reply. I was thinking along the same lines, but I installed HardSPL just fine and flashed to the PDA corner ROM with no problem, the problem arose when I figured out that the radio was causing the phone to have no sound and wanted to update it..which of course did not work. Right now I am trying the stock ROM with the same radio to see if it will allow me to flash it...

da_truth540 said:
Thanx for your quick reply. I was thinking along the same lines, but I installed HardSPL just fine and flashed to the PDA corner ROM with no problem, the problem arose when I figured out that the radio was causing the phone to have no sound and wanted to update it..which of course did not work. Right now I am trying the stock ROM with the same radio to see if it will allow me to flash it...
Click to expand...
Click to collapse
That's why I'm thinking you may have flashed a 'Radio from Hell' which is preventing any further ROM updates. Maybe something in the RFH thread I linked to can help...
Good luck!

Ok, this is a radio from hell, i found some information on it stating that when it is used with any other ROM, sound will not function. Now I am trying to revert back to the orignial ROM but I have a new problem, I cannot find the original rom for this phone (AT&T aku 0.4.4 build 18128 radio 1.27.14.09) in working condition. There is only one link to it and the file is corrupted(rapidshare). is there anyone with this operating system that could send me a link that is NOT the one posted on XDA: (http://forum.xda-developers.com/showthread.php?t=341886). Thanx to drtolson, and thanx in advance to anyone else who is brave enough to get involved.
(Drtolson, I want to try the techniques on the post you sent a link to, but it states that the steps only work with that particular radio and others have not had any success using it with any other radios.)

da_truth540 said:
Ok, this is a radio from hell, i found some information on it stating that when it is used with any other ROM, sound will not function. Now I am trying to revert back to the orignial ROM but I have a new problem, I cannot find the original rom for this phone (AT&T aku 0.4.4 build 18128 radio 1.27.14.09) in working condition. There is only one link to it and the file is corrupted(rapidshare). is there anyone with this operating system that could send me a link that is NOT the one posted on XDA: (http://forum.xda-developers.com/showthread.php?t=341886). Thanx to drtolson, and thanx in advance to anyone else who is brave enough to get involved.
(Drtolson, I want to try the techniques on the post you sent a link to, but it states that the steps only work with that particular radio and others have not had any success using it with any other radios.)
Click to expand...
Click to collapse
I got the File from Rapid share and extracted the NBH and it seems fine.

Jonathan.Parker2005 said:
I got the File from Rapid share and extracted the NBH and it seems fine.
Click to expand...
Click to collapse
ok thanx, I'm downloading it again to see if it works...

Ok, i re-downloaded the file and it worked and also successfully flashed back to the original ROM, I probably won't be able to flash it to another custom ROM but at least the sound is working and the phone is fully functional. THANX TO EVERYONE FOR YOUR HELP!

Noob help w/ATT Fuze + WM6.5

Trying to flash my AT&T Fuze with HardSPL so I can pop a ROM of WM6.5 on it. Not having any luck.
I run the HardSPL executable, it sees the phone (with the current 5.11.XX... ROM version), and then when I hit OK, and see the progress bar (at 0%), it just sits there for about 45 seconds, then gives me a communications error.
Tried this on WinXP and Win7 with the same results. What am I doing wrong?

crescent.wire said:
Trying to flash my AT&T Fuze with HardSPL so I can pop a ROM of WM6.5 on it. Not having any luck.
I run the HardSPL executable, it sees the phone (with the current 5.11.XX... ROM version), and then when I hit OK, and see the progress bar (at 0%), it just sits there for about 45 seconds, then gives me a communications error.
Tried this on WinXP and Win7 with the same results. What am I doing wrong?
Click to expand...
Click to collapse
Is the phone new. We have reports that the SPL Loader changed and prevents flashing HardSPL. Check ur SPL it should not read anything different from 1.90. If it is a higher number then.
Go to the Hardspl thread and flash the 1.90 stock spl frome there first.

Yes, the phone is brand new.
SPL-5.10.0000 is displayed when I enter the bootloader. Would you mind pointing me in the right direction with the HardSPL thread (where I can flash to 1.90)? Can't seem to find it.

crescent.wire said:
SPL-5.10.0000 is displayed when I enter the bootloader. Would you mind pointing me in the right direction with the HardSPL thread (where I can flash to 1.90)? Can't seem to find it.
Click to expand...
Click to collapse
The 1.90 u can find in the HardSPL thread. But check if its ok to get from 5.1 to 1.90
I was more thinking from 1.9XXX to 1.90, so still within the 1.9 loaders. Dunno if its ok for the 5.1 to go down. It should but not shure about that.

Great. I'll check it out. Worse comes to worst, I just may not be able to throw WM6.5 on this, correct?

crescent.wire said:
Great. I'll check it out. Worse comes to worst, I just may not be able to throw WM6.5 on this, correct?
Click to expand...
Click to collapse
well when hardspl works, everything is possible. All the GSM roms are also for fuze afak

http://forum.xda-developers.com/showpost.php?p=4209384&postcount=589
Look through the HardSPL thread, seems that 5.1 Fuze is working with the 1.9 SPL.

Okay, so I was able to boot into the bootloader, where it tells my SPL is 5.1. I can get the HardSPL exe to run and get all the way to the Progress Bar screen (and the phone also jumps to a grey screen with a progress bar), but they both sit at 0% for about 1 min, then it cancels and says "ERROR(262): Update Failed."
Any ideas?

I also had this issue. I did the CID unlock first, then HSPL. I was then able to complete the upgrade.

No joke. I'll have to try that, then.
And, in anyone's opinion, what's the best cooked ROM to be using? EnergyROM?

crescent.wire said:
Okay, so I was able to boot into the bootloader, where it tells my SPL is 5.1. I can get the HardSPL exe to run and get all the way to the Progress Bar screen (and the phone also jumps to a grey screen with a progress bar), but they both sit at 0% for about 1 min, then it cancels and says "ERROR(262): Update Failed."
Any ideas?
Click to expand...
Click to collapse
Are you doing this through activesync. I asume you are. Make sure the file is placed on your main drive of the computer and ran from there. It cannot be in folders hidden. Otherwise it won't work. I had this issue with prior devices while upgrading.

crescent.wire said:
No joke. I'll have to try that, then.
And, in anyone's opinion, what's the best cooked ROM to be using? EnergyROM?
Click to expand...
Click to collapse
That is kind of like asking which is the best baseball team, NASCAR driver, flavor of potato chip or type of candy. Some cooks go for stability. Other cooks go for the latest release. Some cooks throw in all kinds of goodies. Other cooks put an the absolute minimum in the ROM, so the users can add just what he wants. You may hate my favorite ROM and I may hate your favorite ROM. That is why there are so many ROMs to choose from and all these wonderful cooks making them. Try a several different ROMs and see which you prefer.

Mxdadevolper said:
I also had this issue. I did the CID unlock first, then HSPL. I was then able to complete the upgrade.
Click to expand...
Click to collapse
And how might one go about unlocking the CID first?

yamilrx said:
Are you doing this through activesync. I asume you are. Make sure the file is placed on your main drive of the computer and ran from there. It cannot be in folders hidden. Otherwise it won't work. I had this issue with prior devices while upgrading.
Click to expand...
Click to collapse
Yep, doing all that. Thanks, though.

dlweston said:
That is kind of like asking which is the best baseball team, NASCAR driver, flavor of potato chip or type of candy. Some cooks go for stability. Other cooks go for the latest release. Some cooks throw in all kinds of goodies. Other cooks put an the absolute minimum in the ROM, so the users can add just what he wants. You may hate my favorite ROM and I may hate your favorite ROM. That is why there are so many ROMs to choose from and all these wonderful cooks making them. Try a several different ROMs and see which you prefer.
Click to expand...
Click to collapse
A fine point, to be sure.

Sorry, all -- kind of got ahead of myself with all these replies.
So, can anyone point me in the right direction for unlocking my phone's CID?

Simple question
crescent.wire said:
Yep, doing all that. Thanks, though.
Click to expand...
Click to collapse
I have one question. Do you have the phone in "ActiveSynch" mode before running the HardSPL? I found that running it while in the "BootLoader" does not work well, when running the HardSPL.
So, activesynch --> run the hardspl --> make sure you click "Ok", when the phone prompts you, if it is okay to run the 2 executables on your phone --> then watch your phone restart into the "bootloader", then update the hardspl...
Just observation from my past experience...

cso5874 said:
I have one question. Do you have the phone in "ActiveSynch" mode before running the HardSPL? I found that running it while in the "BootLoader" does not work well, when running the HardSPL.
So, activesynch --> run the hardspl --> make sure you click "Ok", when the phone prompts you, if it is okay to run the 2 executables on your phone --> then watch your phone restart into the "bootloader", then update the hardspl...
Just observation from my past experience...
Click to expand...
Click to collapse
Hmmm... I do not have it in ActiveSync mode. I actually have an Exchange connection set up on the phone right now with work. So I should remove that connection, set it to sync ONLY with my desktop, then run HardSPL with ActiveSync 4.5 (on XP) // WMDC (on Vista/7) open?
That's good advice, if I understand you correctly. Thank you!

Did u try to go Stock 1.90 first before doing HardSPL or did u try to flash direct to the unsigned 1.9 ?
As far as I know u have to switch from 5.1 first to the 1.90 signed and then to the unsigned version. See the hardspl thread for more info. Go to this
STEP BY STEP HOW TO RETURN TO STOCK SPL
first.

schnitzelbrain said:
Did u try to go Stock 1.90 first before doing HardSPL or did u try to flash direct to the unsigned 1.9 ?
As far as I know u have to switch from 5.1 first to the 1.90 signed and then to the unsigned version. See the hardspl thread for more info. Go to this
STEP BY STEP HOW TO RETURN TO STOCK SPL
first.
Click to expand...
Click to collapse
Awesome. I'll give that a shot, too. Thanks, guys!

[Q] wrong rom update, what now?

Hello everyone.
Yesterday I saw that there was a new update of my favourite rom EnergyRom. So today I downloaded it, installed it, everything went well. Until I restarted my Raphael ( raph300 btw). It kept stucking on the bootscreen.. even after I installed the rom again it still stucked at bootscreen. So I began trying to fix it with installing my hardSPL again, that didn't work either, still no further than my bootscreen.. after a while I decided to downgrade my spl to my stock-spl. that went well but still stuck on bootscreen. So I tried to install my stock-rom from my provider: (t-mobile netherlands). But then the Rom updater stuck at 0% and I received the well-known [262] error. Suddenly I saw that I stupidly accidentally installed the cdma version of EnergyRom instead of the one I needed: GSM. That explained why it wouldn't boot in the first place. Now I tried to install the olinex hardspl, but the updater stopped everytime with the 262 error. I connected my device to another computer with windows XP, but there I saw that the computer recognized it as a CDMA device.
I know it is a stupid mistake, but is there anybody who knows what I could try? I also tried to hard-reset it, but that wouldn't help either. Any help would SO be appreciated

try to search a tool called MTTY maybe it helps

lvxincad said:
try to search a tool called MTTY maybe it helps
Click to expand...
Click to collapse
Thanx, but how can I use this in combination with my problem?

As I remember 2 years ago,HardSPL is somehow depended on RadioROM. Maybe the ROM influenced the Radio with HardSPL,so try to reflash HardSPL again and Radio. Or it works absolutely not?
http://forums.techarena.in/hardware-peripherals/1161954.htm
http://forum.xda-developers.com/showthread.php?t=371154
http://htcwiki.wetpaint.com/page/RUU+Error+List

TomasNM said:
As I remember 2 years ago,HardSPL is somehow depended on RadioROM. Maybe the ROM influenced the Radio with HardSPL,so try to reflash HardSPL again and Radio. Or it works absolutely not?
http://forums.techarena.in/hardware-peripherals/1161954.htm
http://forum.xda-developers.com/showthread.php?t=371154
http://htcwiki.wetpaint.com/page/RUU+Error+List
Click to expand...
Click to collapse
No, I can't update any ROM. So now i'm stuck with my stock SPL, therefore I wanted to Hard SPL my device, but that didn't work and since then I haven't been able to update any ROM.. would flashing on a different PC help maybe? now I am on a Win7 Pc but maybe it will work in WinXP..

It is also not a bad idea to try different PC with XP to flash. I remember apx.1 month ago I tried to update HTC Trinity with WM6.5 ROM and it keeps failed with some errormessage(nowadays I can't remember which,but the syndroms was similar). Then I considered it as "bricked",until I tried another PC and everything wents correctly and the phone is in its productivity again. Yes,tfirst PC was company notebook with lot of safety kind of software(firewall,this,that,etc...) and the second one was my private laptop at home,just equipeed with regular antivirus software,all updates disabled(instead of AV).

Btw,what about trying to flash official ROM,while you are with stockSPL? Maybe it helps you to startup again the device and then HardSPL again afterwards...

TomasNM said:
Btw,what about trying to flash official ROM,while you are with stockSPL? Maybe it helps you to startup again the device and then HardSPL again afterwards...
Click to expand...
Click to collapse
yeah, that's what I thought too. I tried that also, also tried other custom roms btw before going to the stock rom. But with the stock rom it also stuck at 0% on the update

so, today I tried to flash my rom with two different computers: one with win7 and one with winXP. didn't work either.. I read the MTTY thread and after I installed the custom driver I was able to connect trough MTTY. But what commands should I use to clear the ROM and is there any way that I can update my rom via MTTY?

search MTTY on the forums the first link has all you need to clear the rom and flash via MTTY

I think you may be screwed. You should've asked for help before you started messing with the spl. I don't understand why you thought reverting to the stock spl would be a good approach; it may well be the end of your device. What you should have done is just flashed a stock rom-that would probably have restored your device. Re-flashing hard spl is kind of pointless. The only thing that can over-write hard spl is the special 'stock spl' that olinex put together. It's not entirely stock, and I am not sure that it can be over-written by hard spl. The sole purpose of the 'return to stock spl' is so that you can flash a stock rom, then restore the spl so that you can return your device for warranty/service without being dinged for having unofficial firmware on the device. When you do this, you aren't anticipating getting the device back, so I'm not sure that hard spl can over-write it. I know there have been discussions on whether or not it can be over-written, but I'm not sure that there was ever a clear answer. Anyway, with the 'stock spl' on the device, you can't flash any cooked roms to the device. If you are very lucky, you may be able to flash a stock rom. So, my advice is to try a few stock roms.
I'm pretty sure you'll need hard spl to run mtty/task 29, so I wouldn't waste your time on that. I really doubt it works, and I'm not sure what it's going to buy you, anyway. You really need to be able to flash a rom to the device, and you can't flash a cooked rom with that spl. Maybe you can flash a stock rom, but maybe not. I'm not sure which carrier it will let you upgrade to, either.

NeoTokyo22 said:
search MTTY on the forums the first link has all you need to clear the rom and flash via MTTY
Click to expand...
Click to collapse
yes I did, but the problem is that I can't access my Internal Storage, so I can't put any ROM's on that. Tonight I tried to flash a ROM via my SD card, but when I put my device in bootloader-mode it kept saying that it was 'loading...'

If the bootloader just says 'loading', then you probably need to either reformat the card to FAT32 or rename the image to RAPHIMG.nbh. Make sure you get the extension correct (not RAPHIMG.nbh.nbh).
But you're not going to flash anything with the stock spl, anyway. You need hard spl. I'm not sure you can even flash a stock rom off of the sd card-it probably needs to do it over usb.

I updated lot of smartphones already,but it was already few years ago. However I think,that SP's are flashed with MTTY. For that I needed ROM image in nbh file and with some commands you tell the PC,that it should flash it. Don't forget to disable USB connection in Activesync on XP in case MTTY will connect.

TomasNM said:
I updated lot of smartphones already,but it was already few years ago. However I think,that SP's are flashed with MTTY. For that I needed ROM image in nbh file and with some commands you tell the PC,that it should flash it. Don't forget to disable USB connection in Activesync on XP in case MTTY will connect.
Click to expand...
Click to collapse
I already managed to connect my device with MTTY, the only thing I need to know is which commands I can use to flash the ROM through MTTY. It just sucks that I am not able to go to my Internal Storage, otherwise it would be much simpler I think.

Farmer Ted said:
I think you may be screwed. You should've asked for help before you started messing with the spl. I don't understand why you thought reverting to the stock spl would be a good approach; it may well be the end of your device. What you should have done is just flashed a stock rom-that would probably have restored your device. Re-flashing hard spl is kind of pointless. The only thing that can over-write hard spl is the special 'stock spl' that olinex put together. It's not entirely stock, and I am not sure that it can be over-written by hard spl. The sole purpose of the 'return to stock spl' is so that you can flash a stock rom, then restore the spl so that you can return your device for warranty/service without being dinged for having unofficial firmware on the device. When you do this, you aren't anticipating getting the device back, so I'm not sure that hard spl can over-write it. I know there have been discussions on whether or not it can be over-written, but I'm not sure that there was ever a clear answer. Anyway, with the 'stock spl' on the device, you can't flash any cooked roms to the device. If you are very lucky, you may be able to flash a stock rom. So, my advice is to try a few stock roms.
I'm pretty sure you'll need hard spl to run mtty/task 29, so I wouldn't waste your time on that. I really doubt it works, and I'm not sure what it's going to buy you, anyway. You really need to be able to flash a rom to the device, and you can't flash a cooked rom with that spl. Maybe you can flash a stock rom, but maybe not. I'm not sure which carrier it will let you upgrade to, either.
Click to expand...
Click to collapse
Oke, thanx for your input. I tried to reset my ROM memory with mtty/task 29, but that didn't work, just like you predicted. So my next question is: 'Is there any app that can perform the task 29 without MTTY?'. I googled it, but I could only find the task 29 app for the HTC HD2.. And further, does anybody have a recovery ROM for my RAPH300? I tried the stock ROM on the XDA thread of HTC Raphael, but still got the 262 error

There's really no point in doing Task 29. The bad rom isn't what's killing you now, it's the SPL. It's going to block task 29, no matter what you try (that's one of it's jobs). You should just try to get hard spl back on the device, or try flashing every stock rom you can find. I tend to doubt that either will work, though. The only other option would be to look up the jump spl developed by PoF. I don't remember the name (search for threads started by him), but it was a universal soft spl that would temporarily CID unlock devices so you could flash custom roms. I've never used it before, and I don't know how it loads. You may not be able to load it onto your device with its current state, and it may not even be compatible with a Raphael (it's 3 or so years old), but it's probably worth at least checking out.
Edit: here's the jump spl link. I think you may have to activate it off the device.