Database Info

I don't think it's a paperweight yet, although I am but a newb...

First of all, big thanks to all the geniuses out there working through this stuff. And an equally big apology for being a lame neophyte.
I thought I did all my homework, read all the threads, and was ready to pop my ROM cherry and start flashing my 1.57.00.00 AT&T tilt. Last night, I excitedly downloaded jockyw's fixed HardSPL. Ran JumpSPL from the device, and flashed the TEST ONLY splash screen. Then flashed HardSPL itself. The RUU didn't display any version information for my device, but let me proceed anyway. Finished, rebooted, and bootloader read as follows:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Looked good, so I went ahead and tried to flash Dutty's DualTouch v2 2k8 fixed rom. Started up, again no device info on the RUU, but flashed anyway...progress bar came up, went to 100%, and rebooted. At the ATT splash screen, R/G/D numbers came up, and the phone just hung there. Left it for 30 minutes, came back, and reset it. Same splash screen hang.
Read the forums, and tried again to flash with a different ROM (dutty's no7b). Same prob. Tried others as well. Same issue. Then tried to access device with mtty, ran boot command, and nothing. Finally reflashed with the Cingular WWE ROM (which brought my R/G/D numbers back to normal). Still stuck at splash screen.
Then I connected to device via MTTY, and ran info 0 and info 2 commands. Instead of clean numbers, i got the following:
Cmd>info 0
Platform Model ID:KAIS1*000
Platform HW Board ID:31, PVT1
Cmd>info 2
HTCS00000000jR*¥HTCE
Cmd>
I then ran the boot command, with the following output:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0xAB80, total sector=0x10740
Storage start block=707, total block=1053
Total Bad Block in CE: 0
Erase physical block from 995 to 2032
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
It freezes there...
Asked around on IRC to no avail, but a bored XDA genius told me to try to run a task 37. Did that, but the console spit out a massive volume of info -- actually all repetitions of the same thing:
every field full of 0s (R0=0000000, R1=0000000, etc.) and
"prefetch abort: thread=blah blah NK.exe"
I can access the bootloader without problems, but I can't get any further than the splash screen.
I've read through as much as my eyes can handle, but can't seem to find a solution to this problem that works. Any brilliant xdadev out there care to offer his/her guidance?
Also, barring a solution, I need to send this phone back (still within my 30days...until the 10th). I read the thread on reverting back to stock SPL, but I don't see how that's possible without being able to get back into the phone itself. Is there a way around this?
Thanks so much in advance.

one last thing...
I found a thread in the forum in which Pof advises to run a task 32, then info 2, then getdevinfo. This is what comes up:
Cmd>task 32
Cmd>info 2
HTCS00000000jR*¥HTCE
Cmd>getdevinfo
GetDevInfo: Get backup CID
HTCSKAIS1*00HTCE
Just to save a (possible) step...

ok where did you get the advice to run the boot(cmd) that was a no no!
Now what you need to do is put your phone in bootloader and flash the original rom your tilt/kaiser came with and you should be good to go

whoops. as i said in my earlier post, please forgive my foolishness.
a secondary bit of foolishness is that i'm not sure which rom my phone came with. i know the display driver was 1.57.00.00, but not so sure about the radio GPRS. *sigh*
RUU_Kaiser_CINGULAR_WWE_ seems to put the numbers back to familiar shape...do you happen to know if this is the correct package?
since i've already tried it a few times, i went ahead and reflashed it anyway. got right back to the ATT splash screen, frozen. any ideas?
thanks for your help & speedy reply.

eidetico1 said:
whoops. as i said in my earlier post, please forgive my foolishness.
a secondary bit of foolishness is that i'm not sure which rom my phone came with. i know the display driver was 1.57.00.00, but not so sure about the radio GPRS. *sigh*
RUU_Kaiser_CINGULAR_WWE_ seems to put the numbers back to familiar shape...do you happen to know if this is the correct package?
since i've already tried it a few times, i went ahead and reflashed it anyway. got right back to the ATT splash screen, frozen. any ideas?
thanks for your help & speedy reply.
Click to expand...
Click to collapse
That is the correct ROM for a "stock" Tilt... try flashing it again, try a hard reset... if none of that works try flashing from another PC.

eidetico1 said:
First of all, big thanks to all the geniuses out there working through this stuff. And an equally big apology for being a lame neophyte.
I thought I did all my homework, read all the threads, and was ready to pop my ROM cherry and start flashing my 1.57.00.00 AT&T tilt. Last night, I excitedly downloaded jockyw's fixed HardSPL. Ran JumpSPL from the device, and flashed the TEST ONLY splash screen. Then flashed HardSPL itself. The RUU didn't display any version information for my device, but let me proceed anyway. Finished, rebooted, and bootloader read as follows:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Looked good, so I went ahead and tried to flash Dutty's DualTouch v2 2k8 fixed rom. Started up, again no device info on the RUU, but flashed anyway...progress bar came up, went to 100%, and rebooted. At the ATT splash screen, R/G/D numbers came up, and the phone just hung there. Left it for 30 minutes, came back, and reset it. Same splash screen hang.
Read the forums, and tried again to flash with a different ROM (dutty's no7b). Same prob. Tried others as well. Same issue. Then tried to access device with mtty, ran boot command, and nothing. Finally reflashed with the Cingular WWE ROM (which brought my R/G/D numbers back to normal). Still stuck at splash screen.
Then I connected to device via MTTY, and ran info 0 and info 2 commands. Instead of clean numbers, i got the following:
Cmd>info 0
Platform Model ID:KAIS1*000
Platform HW Board ID:31, PVT1
Cmd>info 2
HTCS00000000jR*¥HTCE
Cmd>
I then ran the boot command, with the following output:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0xAB80, total sector=0x10740
Storage start block=707, total block=1053
Total Bad Block in CE: 0
Erase physical block from 995 to 2032
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
It freezes there...
Asked around on IRC to no avail, but a bored XDA genius told me to try to run a task 37. Did that, but the console spit out a massive volume of info -- actually all repetitions of the same thing:
every field full of 0s (R0=0000000, R1=0000000, etc.) and
"prefetch abort: thread=blah blah NK.exe"
I can access the bootloader without problems, but I can't get any further than the splash screen.
I've read through as much as my eyes can handle, but can't seem to find a solution to this problem that works. Any brilliant xdadev out there care to offer his/her guidance?
Also, barring a solution, I need to send this phone back (still within my 30days...until the 10th). I read the thread on reverting back to stock SPL, but I don't see how that's possible without being able to get back into the phone itself. Is there a way around this?
Thanks so much in advance.
Click to expand...
Click to collapse
Try flashing to this ROM...
I had a similiar error happen. This fixed my Tilt for me.
http://rapidshare.com/files/5340369...adio_sign_22.45.88.07_1.27.11.31_Internal.exe

alltheway said:
Try flashing to this ROM...
I had a similiar error happen. This fixed my Tilt for me.
http://rapidshare.com/files/5340369...adio_sign_22.45.88.07_1.27.11.31_Internal.exe
Click to expand...
Click to collapse
just flashed it...
it changed the splash screen to the ATT TEST ONLY one, and altered the R/G/D numbers, but still frozen...no boot.
Incidentally, spent a good long while on IRC this evening with cmonex/OliPro--those two are saints, btw--and they discovered through mtty that i had no extROM. they told me to look for a NBH that included an extROM.nb, but i can't find any...all the ones i've downloaded only have 769.nb, SPL.nb, PrimarySplash.nb, and windows.nb.
Still no real idea how to proceed...

the kaiser has no EXT_ROM oli and com should have known that lol... so either they where just ****ing with you or didn't know you had a kaiser...

try reflashing hardSPL just for the hell of it. then flash a rom from your SD card there are instructions on how to do that floating around in the Wiki

austinsnyc said:
the kaiser has no EXT_ROM oli and com should have known that lol... so either they where just ****ing with you or didn't know you had a kaiser...
Click to expand...
Click to collapse
or we have no kaiser and never needed to patch anything about its (non existing) extrom so never found out about this.

austinsnyc said:
try reflashing hardSPL just for the hell of it. then flash a rom from your SD card there are instructions on how to do that floating around in the Wiki
Click to expand...
Click to collapse
er it is hard-SPL for a reason
fortunately lnb flashing is not patched in it (yeah it is MFG) so that would allow SPL reflash.

I didn't mean to create any bad blood here, folks...
just trying to fix this $200 desk sculpture.
austin: tried reflashing hardspl. no joy.
hopefully cmonex & Oli will have some advice later tonite on irc.

hey cmonex/oli -
sorry i fell asleep on you last night. felt like a loser when i woke up at 5am at my terminal. anyway, i ran the command you told me to run in your final message, when you spoke of a WORKING solution (!)
here's the output:
Cmd>
Cmd>mw 8C019AD4 1
8C019AD0: E1A00000 - | ....
Cmd>
I'll try to find you guys on IRC later on. thanks again.

Sorry to intterupt....
Whats the IRC Channel?
Thanks,
Nadavi

it's #xda-dev on freenode. lots of good peoples on there...

cmonex said:
er it is hard-SPL for a reason
fortunately lnb flashing is not patched in it (yeah it is MFG) so that would allow SPL reflash.
Click to expand...
Click to collapse
OK, just to make this statement more precise... turns out lnb performs the same check on the SPL version (i.e. same function), but again as this is MFG we've been able to unpatch this patch in HardSPL by changing some bytes in the loaded bootloader image in RAM - and stock SPL was reflashed fine, i hope eidetico gets the replacement quickly.
again, this only works if your hardSPL is MFG, kaiser is lucky there

big ups to cmonex and oli for helping me fix this issue. you guys are geniuses!
got the replacement today! gonna try to reflash tonight -- hopefully things won't get so gummed up this time.

eidetico1 said:
big ups to cmonex and oli for helping me fix this issue. you guys are geniuses!
got the replacement today! gonna try to reflash tonight -- hopefully things won't get so gummed up this time.
Click to expand...
Click to collapse
good luck! let us know if it went ok

Think I've bricked my Kaiser - Can anyone help?

Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?

Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though

If your at the tri-color screen, just reflash a new rom

Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try

japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.

hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?

japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.

Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously

Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE

New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910

Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?

Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver

You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?

japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.

jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash

No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.

Did you try installing HardSPL and then reflashing?

the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.

URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.

austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!

HELP! SDA stuck on bootloader screen

I just flashed the NiTroGen WM6 SP1 onto my friend's T-Mobile SDA (US). I m guessing something didnt go right putting it into SuperCID, because after it finished flashing the ROM, instead of booting up it went straightback into bootloader mode.
I tried to go back to an original ROM, but couldnt find any. Tried flashing a number of others, but keep getting 'Invalid Vendor ID'.
Can anyone tell me what I can do to get that phone working again?? does anyone have an old ROM that i can just put on it??
thanks for any input!

Read on this small thread, its only 3pages. Pay attention to page 3
http://forum.xda-developers.com/showthread.php?t=278718&page=3
Now do make sure you followed the instructions step by step as on this thread:
Step-by-Step Pictorial guide to Upgrade HTC Tornado to WM6
http://karhoe.net/content/view/21/1/
Don't forget to SuperCID your phone and "format BINFS" before flashing!
Good Luck!!

Up & Running Again!
thanks, markanthonypr. i actually managed to revive it last night.
since the SDA was never properly in SuperCID, it refused to flash any standard ROM. obvious solution is to patch a compatible ROM with TyphoonNBFtools. but it simply wouldnt work...
here is why it took so long:
i think TyphoonNBFtools 0.4 has a bug where the header data changes wont stick, even after you save them. so no matter what ROM i tried or what I put the header to, the phone wouldnt allow it to be flashed.
It only worked after I saved it under a different file name (then renamed back manually to nk.nbf), and then flashed it using ROMUpdateUtility.exe v2.00.2 (the one that was provided with NiTroGen WM6 SP1).
heres what I put the header to. not sure if that was even significant in the end:
HTC
Tornado
[blank]
ENG
[blank]
SMC_0501
those changes finally showed up when running ROMUpdateUtility ("Verify that you want to update the ROM version From .... to ...").
All downhill from there. flashed I-mate ROM, unlocked & SuperCID it (confirmed SuperCID with mtty1.42.exe 'info 2') and flashed WM6. phew
One final issue was that we couldnt get GPRS to work at all. found out that we needed to update Radio seperately. did that, and after like 8 hours the friggin SDA finally played nice.
Famous last words:
"WM6 is awesome, dude. bring your phone tonight, it ll take like 20 min."

I'm glad it all worked good for you. Now its time to enjoy your new phone. I'm looking forward to moving up to 6.1 or 6.1Pro though I'm very satisfied with I'm using now. Its pretty stable, just about as stable as my OEM WM5.

hy, pls can you help me.
i have a spv C600 from Orange, but when i buy it it was upgraded with i-mate sp5m and i tryed to upgrade with: Tornado_WM6_Platinum_Edition_-_SP1
i'm a beginner
it upgrade ok..with no problem. and after restart he stuck in booloader.
i think he wasn't superCID
and with Tera Term i got this:
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSORG_0409 ‘©öIHTCE
Cmd>
is he DEAD?
or is a another chance to see him alive?
P.S: it works to upgrade on with: Tornado_WM6_Platinum_Edition_-_SP1, with other only error or invalid vendor id etc.
thanks. i hope you understand my bad english.

phynesse said:
Famous last words:
"WM6 is awesome, dude. bring your phone tonight, it ll take like 20 min."
Click to expand...
Click to collapse
Ahhhh... that's the funniest thing I've heard today! Made me laugh out loud. It would be exactly the same kind of thing I'd say to someone, and then regret it four hours later.

oniciuc said:
hy, pls can you help me.
i have a spv C600 from Orange, but when i buy it it was upgraded with i-mate sp5m and i tryed to upgrade with: Tornado_WM6_Platinum_Edition_-_SP1
i'm a beginner
it upgrade ok..with no problem. and after restart he stuck in booloader.
i think he wasn't superCID
and with Tera Term i got this:
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSORG_0409 ‘©öIHTCE
Cmd>
is he DEAD?
or is a another chance to see him alive?
P.S: it works to upgrade on with: Tornado_WM6_Platinum_Edition_-_SP1, with other only error or invalid vendor id etc.
thanks. i hope you understand my bad english.
Click to expand...
Click to collapse
It did NOT upgrade properly if you are still in bootloader mode. Find a ROM that will make you get back a normal phone (maybe the imate ROM-ftp://ftp.clubimate.com/) and then follow this guide EXACTLY!!

O2 Stellar will not flash or boot, tried everything!

Ok, so rapid short overview:
I tried to flash my O2 Stellar with the new HTC wm6.1 Kaiser ROM. The HTC website, for reasons unbeknowest to me would only give me the italian ROM, so I got the english variant off rapidshare.
Tried to flash, everything going well, until (at 0%) it turns around and says the ROM isn't compatible. I figure this requires some HardSPL goodness, but the installer for THAT jumps to 100% in seconds and doesn't seem to do much. Tried a soft SPL (SSPL-KAIS.. no white screen issue), hey-ho, presto! ROM tries to install.
...hangs at 15%, device reboots to the rainbow. Displays:
KAIS130
SPL-1.82.0000
CPLD-8
In the corner: RUUNBH
I've read ALL the other threads on this issue to try and restore the phone. I've tried ALL the O2 ROM dumps people have supplied (all two of them I could find) and every time it either had an error 262 (comms error) at 0%, or got as far as 1% or maybe 2% and then error 29-something (ROM not compatible/suitable for phone). O2 originals, cooked ROMs, HTC updated ROMs, ROMs for different vendors (those produced "wrong vendor" errors). NOTHING IS WORKING!! *tears out hair*
Apparently connecting with mtty and typing "boot" causes the device to try booting the original rom before the flash. I figure maybe I could boot it, copy the phone's OWN rom (c'mon, THAT rom would HAVE to work, right?!) and reflash it. So I fire up mtty, tell it to boot. But it doesn't. Instead, the screen sort of.. fades, between the SPL and pure white (looks almost like display is broken!) and mtty displays:
...OH. Ok, just tried again to copy mtty text and now it's booting.
This is what mtty displays as the phone boots:
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
Click to expand...
Click to collapse
Ok, focus of the thread changing, does anyone know if I could dump the ROM and flash it? I'm about to find out anyway but if someone knows this is foolish please let me know
Cheers, everyone.

Not looking good for you.
Sounds like you flashed a ROM into the SPL at a guess. You shouldn't flash anything except SPL's when you are in Soft SPL's (SSPL or JumpSPL).
Try PM'ing a guy called GSLEON3. He's a mod here and for a beer or two will probably set you right.
@GSLEON3, I really should figure some of this out someday myself. That way I can help rather than just pointing users to you.
EDIT:
You have tried the stuff in here first? http://forum.xda-developers.com/showthread.php?t=371154
Ta
Dave

DaveShaw said:
Sounds like you flashed a ROM into the SPL at a guess. You shouldn't flash anything except SPL's when you are in Soft SPL's (SSPL or JumpSPL).
Click to expand...
Click to collapse
In retrospect that's exactly what I did, yeah. Luckily the boot command worked on the fourth try (as above... guess perseverance gets results) and the phone worked enough for me to retry the HardSPL install (which worked). Then I was able to flash the O2 Stellar ROM found elsewhere in this forum which allowed the phone to boot normally again. THEN I was able to flash the english HTC Kaiser 6.1 WWE ROM.
That thread linking to MTTY techniques for formatting may have come in very useful, I will remember that one!

Go and "security unlock" your device now. It makes it almost unbrickable.
There is a app called FrankenKaiser which can re-install your SPL if you decide to format it (not that you would want to under normal circumstances)
Ta
Dave

universal,updated, screen is garbage on reboot

HI there,
hope someone can help with this. I can upgrade to any rom, except original O2 rom wm5. weird. after successfully upgrading and I do reboot, I press 0 , then the screen is garbage nothing happens, any ideas? I want last o2 rom v 5
thx

redjupiter said:
HI there,
hope someone can help with this. I can upgrade to any rom, except original O2 rom wm5. weird. after successfully upgrading and I do reboot, I press 0 , then the screen is garbage nothing happens, any ideas? I want last o2 rom v 5
thx
Click to expand...
Click to collapse
WELL MY FIRST THOUGHTS IS THAT YOUR DEVICE IS CID LOCKED.. Try to delete the radio.nbf from the package and try to upgrade, should work... if not try doc format and reflash....

redjupiter said:
HI there,
hope someone can help with this. I can upgrade to any rom, except original O2 rom wm5. weird. after successfully upgrading and I do reboot, I press 0 , then the screen is garbage nothing happens, any ideas? I want last o2 rom v 5
thx
Click to expand...
Click to collapse
rajivshahi said:
WELL MY FIRST THOUGHTS IS THAT YOUR DEVICE IS CID LOCKED.. Try to delete the radio.nbf from the package and try to upgrade, should work... if not try doc format and reflash....
Click to expand...
Click to collapse
Hi! I faced the same problem. This happened to my Orange SPV M5000 when I doc format my device. Now all cooked ROMs work fine but whenever I try to install the stock ROM, the screen turns white with light blue lines and I could not move ahead. I have to revert back to the other ROMs. I have tried different WM5 Stock ROMs (i.e. O2, I-mate etc.) but no success at all. Doc Formatted my device a number of time with the idea that it might solve the problem, but no success. I have searched the web to find a solution to this problem but all my efforts went in vain. I hope someone might be able to help.
Regards,
Haque

Haque said:
Hi! I faced the same problem.
Haque
Click to expand...
Click to collapse
As i said in my last post try to there are three roms in oficial rom... ms_.nbf, nk.nbf and radio_.nbf. so try to delete the radio_.nbf and flash... most of the cases it is what causes the problem...
Cheers
Rajiv

rajivshahi said:
As i said in my last post try to there are three roms in oficial rom... ms_.nbf, nk.nbf and radio_.nbf. so try to delete the radio_.nbf and flash... most of the cases it is what causes the problem...
Cheers
Rajiv
Click to expand...
Click to collapse
Hi!
The testing was done with and without the radio. The result was the same. The problem seems that the windows splash screen area gets corrupted while installing a WM5 ROM. However, if the WM5 is installed first to show the Operator Splash Screen (i.e. O2 logo Screen or Imate Logo Screen or Orange Logo Screen) and then any of the cooked version is installed to replace WM5 with WM6.x then the set behaves normal but if WM5 is required the second Splash Screen i.e. Windows Logo is always shown corrupted.
Regards,
Haque

Just install another splash screen after installing the ROM of your choice.
How to change bootsplash image

-Jonny- said:
Just install another splash screen after installing the ROM of your choice.
How to change bootsplash image
Click to expand...
Click to collapse
Can't do that, the phoen is stuck at the garbage screen ONLY if the rom is wm5. All other ROMS work fine.
I did doc format, no avail. I will try to delet the radio.

Perhaps then that particular ROM is corrupt. Have you tried downloading it again, perhaps even from a different source (or a source that is known to work).

redjupiter said:
Can't do that, the phoen is stuck at the garbage screen ONLY if the rom is wm5. All other ROMS work fine.
I did doc format, no avail. I will try to delet the radio.
Click to expand...
Click to collapse
Well, I have already tried all this but all my efforts went in vain. Just try on your device and please do let me know if it is in any sort turn beneficial for you.
-Jonny- said:
Perhaps then that particular ROM is corrupt. Have you tried downloading it again, perhaps even from a different source (or a source that is known to work).
Click to expand...
Click to collapse
Hi! I did try different WM5 ROMs (I-mate, O2, Orange) on my Orange SPV M5000. The result is same. The garbage screen started appearing after the Doc Formatting. I don't know what actually happened to the device. I have Doc formatted my device a couple of times assuming something might went wrong. As mentioned by "REDJUPITER" other ROMs work fine. Just curious what could have be done wrong and how to fix it.
Regards,
Haque

perhaps you miss this one:
(bad radio flashing, do not copy - paste)
USB> password 0000000000000000 (( Returns: HTCSPass1.CMˆËHTCEUSB> ))
USB> set 1e 1 (( Returns: USB> ))
USB> erase a0040000 c80000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a0cc0000 c80000 ((Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a1940000 640000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> set 1e 0 ((Returns: USB> ))
then try to flashing your original rom.

indrastrid said:
perhaps you miss this one:
(bad radio flashing, do not copy - paste)
USB> password 0000000000000000 (( Returns: HTCSPass1.CMˆËHTCEUSB> ))
USB> set 1e 1 (( Returns: USB> ))
USB> erase a0040000 c80000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a0cc0000 c80000 ((Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a1940000 640000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> set 1e 0 ((Returns: USB> ))
then try to flashing your original rom.
Click to expand...
Click to collapse
Hi!
Tried this, step by step, but the results are the same. The problem persists. Hope to get some advice on this.
Regards,
Haque