yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
This thread really should be renamed to be more specific. The commands used with MTTY as descrbed in this thread are really not for fixing bricked kaisers.

The set 16 0 & set 14 0 commands only clear the system RUU (rom Update) flags.

Sometimes when flashing the system gets hung up & is still looking for rom data to be downloaded to the device, which is what the BL or tri-color screen is for.

This is called a RUUNBH error. When you encounter an RUUNBH error, your device will default to the BL (tri-color) screen. You will at these times notice the letters RUUNBH at the top of the BL screen.

THis error can be troublesome for the newer 1.93 SPL on recent AT&T TIlt Devices.

For the AT&T Tilt with any SPL below 1.93 the proper sequence for RUUNBH errors is:

cmd> set 16 0

cmd>boot

As all SPL versions can & sometimes do have different valid commands, the boot command may be invalid for some HTC & all 1.93 SPL version Tilt's.

In this case, after the set 16 0 command you may just soft reset. Alternatively, to boot the device via MTTY you can also use the following command:

cmd>task 8

Again, the info in this thread is primarily concerning RUUNBH errors. Should you have another issue causing your device to be stuck in BL, there are other commands to try, but some of those can be quite risky, so I'll not post them here. Besides, if you know enough about CE, SPL, OEMSBL, etc...Then you know how to find them. Just be careful in what you share, as you defintely have previously noted there are some people a little to eager to help, that know neither the reason nor the consequences behind some of the mtty commands.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cweems:
everything worked for me. thanks all!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Mmm... thank you again.

Can you help me with this, how should I name the thread, what needs to be fixed?

Mostly when you get stuck on a flash it's the OS part isn't?

Maybe I also need to add how to get out of a bad radio flash?

Seems like I'm helping a lot of people with this thread who where stuck at bootloader and now are using there device again!

Anyway... if you tell me what need's to be changed, I will change it. ;)

Regards,

Leo :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ukelvin:
really helpful!!!! I just revived my dead Kaiser
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] 3emado:
Thanks Man You Really Saved me
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] -IK-:
I spent 4 hours in hell and was going to go back to the Vodafone shop to try and get a replacement for what I thought was a bricked Kaiser.

Thank you so much for this guide...Phew!

Got it working again and even better, have an excellent Vodafone WM 6.1 Rom installed.

It's all good :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] edbutler:
Use Mtty On A Kaiser And You Will Need To Buy A New Kaiser!

You will need to use specific coding for the Kaiser which is different then the hearms. Take care fined someone that has used it and get the info from them follow each step to the key. I have seen more whopps reports then "it worked" take care.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aahmad:
Hi all,

My Kaiser fell in the water accidentally and I pretty much spent the whole day looking through forums trying to unbrick it. I bought it a few days ago online. When it turns on, it shows me the 3 color strips and is stuck there. I tried mtty and the commands mentioned in this thread . None of them worked.

It keeps coming back to the tri-band / bootloader screen and it displayed "no image found on file " for a second and comes back to the bootloader. I did a hard reset (basically pen reset + power button + all other buttons one after the other as I didn't know which one is the record button) . It booted to windows splash screen once and shut down by itself. It, then , went back to the bootloader again.

Before the bootloader, I kept getting the error that battery was empty which I don't get because the battery should be fully charged. I have had it connected to the power supply (USB) this whole time. Although, when I got t he windows mobile splash screen, it was not connected to USB.

I have been wracking my brains trying to figure this out. Can you guys please point me in the right direction? Thanks in advance
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] edbutler:
Dropped in the Water

If you dropped it in the water then I would quickly remove the battery ,take it apart and dry it as best you can then do not try to power it up for about 3 days. Let it dry completely. Then you might be surprized and it will be working again. If you power it up while there is water on the internal PC board then you might be shorting components left and right and a tricolored screen will be all you ever see. good luck!

Ed...:confused:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bolasz:
Could you, please!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Mmm... I disagree.

The steps I mentioned on page 1 are harmless if you follow them correct!

But MTTY is a powerfull tool so it's necassary to know before you try! ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
Yeah, it's helped a lot of people. But the issue arrises when people use the general search for MTTY commands instead of using the forum specific search. Most of the MTTY info out there comes for the Universal & Hermes forums. Panicked people that have tried the set commands start entering random commands or searching & inadvertantly find things that really only apply to older models.

The bottom line is, you're pretty safe if you follow directions. Only panicked people that don't read thuroughly have issues.

The main thing is that the commands here are specifically aimed at RUUNBH errors.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aahmad:
Thanks edbutler.

I had a hunch that I shouldn't power it on but I got impatient and had to see if it was working or not. Now, it's stuck in bootloader mode. I guess I will have to get it replaced (assuming it's possible). I wish there was a way I could point it to the right place for the OS image. Oh well.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aruppenthal:
Heres a handy trick for water logged electronics. As edbutler said remove the battery as quickly as possible. Get some uncle bens rice-(DRY rice) (if you have a craft store nearby flower drying pellets work better). Put the phone and the rice(or pellets) in a plastic bag and seal them up for 24 hrs.

See if it boots. If you do this immediately after the water it will work 90% of the time. If you power it on before you attempt to dry it the percentage drops considerably.

I have used this method many many times.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] wr450f:
I have really to say, that this thread helped me a lot. My Phone was crashed and I was able to reset the phone by using the tools and following the steps in this thread.

Thanks a lot.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lasagne:
Thanks a lot you saved my Kaiser :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mad_tunes:
wicked! thats all I needed!

my kaiser was stuck at the boot loader screen for no apparent reason (id just done a normal soft-reset). This got it booting the OS again.

sorry if it's been asked - but what went wrong?

thanks a lot

'tunes

edit:

close, but not quite!

Once I ran the command above, my phone did boot into the OS and finished the setup for the last flash I did.

once that'd finished, the phone reset itself and dumped me back at the bootloader screen!

Anyone know how I can successfully set the phone to load the OS every time it boots?

thanks again,

'tunes
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
You can try:

cmd>set 14 0

cmd>boot

But if that doesn't do it you may need to perform other diagnostics to find the issue.

There is no one thing that can cause this, other than bad blocks & many things can cause bad blocks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mad_tunes:
Right, I got this:

Cmd>set 14 0

HTCST ÚÈÒHTCE

Cmd>boot

InitDisplay: Display_Chip=1

Card inserted

Cmd5 CMD_TIMEOUT

SD 2.0 LC card

SD Init OK

SDFATChkConf: RhOpenFile() failed KAISCONF.txt

OSSIReadBack ++

Read SI data from flash success

tail signature match

Checksum match

UserStorageSIPreload ++

then it sat at the boot loader again.

One thing I've noticed is that just before the bootloader screen shows, I get a light coloured screen with the message 'now loading No image file!'

here a few other details which might help:

The tri-color screen doesnt show "RUURUN" or similar

########################################

Cmd>task 32

Cmd>info 2

HTCS00000000jR*¥HTCE

Cmd>getdevinfo

GetDevInfo: Get backup CID

HTCSKAIS1300HTCE

###########################################

Cmd>info 8

--- 2K bytes sector version ---

DEVICE NAME=samsung_k9k2g08

DEVICE ID=0xAA

DEVICE MAKER ID=0xEC

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x800

BLOCK PAGE=0x40

Checking block information

BLOCK 2 (0x2) is reversed block

BLOCK 8 (0x8) is reversed block

BLOCK 9 (0x9) is reversed block

BLOCK 10 (0xA) is reversed block

BLOCK 11 (0xB) is reversed block

BLOCK 16 (0x10) is reversed block

BLOCK 17 (0x11) is reversed block

BLOCK 18 (0x12) is reversed block

BLOCK 19 (0x13) is reversed block

BLOCK 43 (0x2B) is bad block

BLOCK 46 (0x2E) is bad block

Partition[0], type=0x20, start=0x2, total=0x63E

Partition[1], type=0x23, start=0x640, total=0x740

Partition[2], type=0x25, start=0xD80, total=0x8700

Partition[3], type=0x4, start=0x9480, total=0x11E40

CE Total Length(with sector info) = 0x4A8A400

CE CheckSum Length(without sector info) = 0x4A40000

############################################

I've also noticed that when I use MTTY to get it to boot into CE, everything seems to work OK but the signal strength icon show an exclamation mark like I have no coverage.

Anyone got any recommendations.....pleease?

A huge thanks in advance,
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mad_tunes:
anyone....

please.....
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mkford:
Infact I tried to up ROM ( Wrong CID -- 15% then failed ) and my device was bricked.....Just use mtty with "set 16 0" and "task 8" my device be boot in normal.

Thanks !
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bikepilot:
This works.. great job now just need to get mine unlocked :((
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ddavis17:
Life Saver

O my god thank you for the set 16 0 command. I kept using the set 14 0 command and i was getting very frustrated:mad:. Im glad i saw that before i threw my tilt out of the window:D:D:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] htc_ro:
bricked...

hello guys! i have some problems with my MTeoR and mtty...

my device is bricked (i guess so, because it will not go over the HTC logo screen) after unsuccessful ROM update.

mtty commands:

set 14 0

task 28

task 0

worked perfectly, but still the device doesn't pass the HTC logo...

any ideas?

thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
Dude, FIRSTLY, how do you figure that the MTTY commands woul be the same? The above commands are only for certain SPL version of the Kaiser. task 28 formats the OS, & should not really be used on a non-booting device.

These commands are really most specifically geared towards RUUNBH errors. This will show on a kaiser with "RUUNBH" on the screen.

The best bet for these errors is cmd>set 16 0

followed by cmd>boot or for newer SPL's, cmd>task 8

99% of the time a set 14 command will do nothing for you. Your device is not in this error state of RUUNBH. Sounds more like OS issue. Reflash an OEM rom. IN THE FUTURE BE CAREFUL WHAT YOU DO AS NOT ALL SPL & THEIR COMMANDS ARE THE SAME!!! For instance, in Hermes, a tsk 2a can repair bad blocks, however, in kasier it will wipe out your splash, your OS & your SPL. This was a hard brick until about a month ago. Try finding out if this command will work & PM me the results

cmd>info 8

Also tell me your SPL, rom & radio version & I'll have a look at what we can do.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Enigma_cpl03:
Can some one help me I ran into a snag.. at this time.. my phones screen is black.. no backlight or anything.. I get up to step 8 and I cannot type anything in MTTY.. the only way i can type somthing in is if I do a soft rest which messes the whole process up. Can some one give me some direction on to why MTTY isent letting me type anything.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Enigma_cpl03:
When I get to step 8 I the following info "SetHTCRegionInfo: block=3, CID=11111111, PID=00000017, IMEI=-----------------------, SECU_FLAG=0" which doesent seem to corrispond to what is pictured. what am I doing wrong
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] htc_ro:
the boot command doesn't work, no matter how hard i try. i have sent you a PM with the feedback from the info 8 command.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
Dude, DO YOU HAVE A MTEOR??? OR A KAISER??? YOU DO REALIZE THAT THIS INFO IS SPECIFICALLY GEARED TO HTC KAISER, RIGHT??? SO YOU ARE ENTERING KAISER SPL COMMANDS ON A DIFFERENT DEVICE???
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
There are no 8 steps. I don't know what the heck you're talking about, but it sounds like you killed your SPL.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kleze:
i have exactly the same problems. Without a reason the 3 color screen appeared after it worked for 2 weeks. There is no RUNUUH on the screen, it just says

KAIS130 MFG

SPL-1.0.Olipof

CPLD-8

with USB or Serial on the bottom of the screen.

Also, i can boot the device with mtty, but i can't connect to it through activesync or windows explorer.

I get response from mtty and i can flash everything in the kaiser, but it doesn;t change the SPL!

GSLeon3 told me that the SPL is overwrite protected! Because i can;t connect to the device, i can't copy files to it.

So the SSPL trick won't get the SPL overwrite protection off. There are mtty commands which can get the overwrite protection off, but i can;t find these commands.

Does anyone have some suggestions? There are a lot of people with this problem, but i guess they couldn't find a solution!

Thx in advance! I will donate the winning tip :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Enigma_cpl03:
7) Run MTTY (COMn) and carefully enter following commands:

echo_on (the reply in MTTY should be "ECHO ON MODE")

setboot 1

=> see screenshot "5. mtty-echo_on setboot 1.JPG"

mb 9de8bc => dump HTC security area

mw 9de8bc 1 31313131 (replaces first half CID by SuperCID "1111")

mw 9de8c0 1 31313131 (replaces second half CID by SuperCID "1111")

mw 9de8e4 1 00000000 (Sets security flag to 0, sec unlocked)

mb 9de8bc => dump HTC security area again and check if CID and security flag are modified in memory

=> see screenshot "6. mtty-mb 9de8bc.JPG"

setinfo

powerdown

=> see screenshot "7. mtty- setinfo - powerdown.JPG"

Close MTTY

At this point your Kaiser is unjailed, security unlocked (and SIM unlocked) and SuperCID Now we need to prepare another run with FrankenKaiser to softload a SPL which will allow us to flash a HardSPL. In principle steps 1-7 need never to be done again.

8a) Unplug usb cable, remove and reinsert battery, replug usb cable and then power on. Connect with MTTY (COMn):

- type "echo_on". (the reply in MTTY should be "ECHO ON MODE". if you see that it means you never have to perform steps 1-7 again. If you don't, something went wrong in steps 1-7 or there is a connectivity problem)

- type "setboot 1" (you should see "ARM9BootMode:1").

- Close MTTY !!

8b) Unplug usb cable, remove and reinsert battery, replug usb cable and then power on. Connect with MTTY (COMn):

- type "echo_on". (you should see "ECHO ON MODE")

- type "dload" to put phone in dload mode.

- Close MTTY !!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] htc_ro:
oops... it's a meteor, damn! :(

any info though?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kleze:
I got it going again with the SSPL bootloader. I have send it with a bluetooth connection to my device. After that i flashed hardspl 3.28 and now it's back to normal!

Thx!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] karlux:
Hi,

I have a Kaiser which reboots into bootloader all the time - I was ablo to boot it into OS with mtty boot command, I was also able to flash hard spl v1, also I did flash Dutty's rom.

I don't have RUUNBH on bootscreen

info 8 gives me this:

Cmd>info 8

--- 2K bytes sector version ---

DEVICE NAME=samsung_k9k2g08

DEVICE ID=0xAA

DEVICE MAKER ID=0xEC

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x800

BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block

BLOCK 1 (0x1) is reversed block

BLOCK 8 (0x8) is reversed block

BLOCK 9 (0x9) is reversed block

BLOCK 10 (0xA) is reversed block

BLOCK 11 (0xB) is reversed block

BLOCK 476 (0x1DC) is bad block

BLOCK 479 (0x1DF) is bad block

BLOCK 763 (0x2FB) is bad block

BLOCK 771 (0x303) is bad block

BLOCK 867 (0x363) is bad block

BLOCK 1119 (0x45F) is bad block

BLOCK 1223 (0x4C7) is bad block

BLOCK 1261 (0x4ED) is bad block

BLOCK 1265 (0x4F1) is bad block

BLOCK 1313 (0x521) is bad block

BLOCK 1315 (0x523) is bad block

BLOCK 1379 (0x563) is bad block

BLOCK 1491 (0x5D3) is bad block

BLOCK 1537 (0x601) is bad block

BLOCK 1569 (0x621) is bad block

Partition[0], type=0x20, start=0x2, total=0x63E

Partition[1], type=0x23, start=0x640, total=0x740

Partition[2], type=0x25, start=0xD80, total=0x8A00

Partition[3], type=0x4, start=0x9780, total=0x11B40

CE Total Length(with sector info) = 0x4C0BC00

CE CheckSum Length(without sector info) = 0x4BC0000

Cmd>

What can I do?

I flashed HARD SPL 3.56 and on 100% got error - now it is stuck in bootloader and doesn't allow to execute MTTY commands - command error.

What can I do with this Kaiser?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kleze:
now it's even worse, with spl-3.28.Hard i can;t boot with mtty's command 'boot'. Also, i have the same bad blocks (2) as the guy above me. What causes these problems? I'm sure i didn't flash anything wrong. It worked for 2 weeks, flashed the spl-3.28 today, it looked okay again, en now the problems are even worse! Should i do the frankenkaiser?

Thx!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MickyMax:
Thanks Laurentius26 !

Thanks, you save me today... :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] culleyps:
If one has a msg form the pc that says it can't connect to the unkown device it appears to have malfunctioned but the phone says USB in the bootloader, is it still possible to connect to the phone with MTTY?

I am using Vista and have MTTY version 5.13.

Any help is greatly appreciated.

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] StealthNet:
Kleze,

I have the same problems as you do. I started another thread here about my problem.

Thing is, using the phone is near to impossible. Sometimes I reset it and it gets to bootloader, sometimes it boots ok.

USB connection is only working in bootloader mode. I'm able to flash anything, but with the phone booted, I get a "USB device not recognized" message.

Did you issued the commands as Enigma_cpl03 stated ?

Here is my info 8:

Cmd>info 8

--- 2K bytes sector version ---

DEVICE NAME=hynix_hyh0ssj0mf3p

DEVICE ID=0xBA

DEVICE MAKER ID=0xAD

PAGE SIZE=0x800

TOTAL PAGE SIZE=0x840

BLOCK COUNT=0x800

BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block

BLOCK 1 (0x1) is reversed block

BLOCK 2 (0x2) is reversed block

BLOCK 3 (0x3) is reversed block

BLOCK 4 (0x4) is reversed block

BLOCK 5 (0x5) is reversed block

BLOCK 7 (0x7) is reversed block

BLOCK 8 (0x8) is reversed block

BLOCK 9 (0x9) is reversed block

BLOCK 10 (0xA) is reversed block

BLOCK 11 (0xB) is reversed block

BLOCK 12 (0xC) is reversed block

BLOCK 13 (0xD) is reversed block

BLOCK 14 (0xE) is reversed block

BLOCK 15 (0xF) is reversed block

BLOCK 16 (0x10) is reversed block

BLOCK 17 (0x11) is reversed block

BLOCK 18 (0x12) is reversed block

BLOCK 19 (0x13) is reversed block

BLOCK 20 (0x14) is reversed block

BLOCK 1370 (0x55A) is bad block

BLOCK 1371 (0x55B) is bad block

BLOCK 1630 (0x65E) is bad block

Partition[0], type=0x20, start=0x2, total=0x63E

Partition[1], type=0x23, start=0x640, total=0x700

Partition[2], type=0x25, start=0xD40, total=0x90C0

Partition[3], type=0x4, start=0x9E00, total=0x114C0

CE Total Length(with sector info) = 0x4F4F000

CE CheckSum Length(without sector info) = 0x4F00000

Cmd>

I really don't know what else to do, it started doing this (booting into bootloader) out from nothing.

According to what I've read so far, it seems logical to try what Enigma_cpl03 said, and then try to revert to a standard OEM ROM. What do you think ?

ANY help would be greatly appreciated.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] newtonik:
Have you tried as instructed in the first post, doing "set 16" and if it doesn't work try "set 14". One of these commands set it to boot from OS for me (not sure exactly which one).

Try these first if you want to do it without formatting your OS. Also one more thing, i was having an issue with the "set" commands not working then i noticed i had to issue cmd> set 14 , that is a space between > and "set 14". It could very well could be specific to me.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] StealthNet:
Yes Newtonik, and as funny as it may seem, if I get into bootloader, MTTY, and issue "set 14" or "set 16", and then "boot", the device boots into the OS everytime.

But if I turn the device off, and then back on, it gets into bootloader.

Also, when I get the OS, the USB is still not recognized by the PC.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] StealthNet:
... I was thinking about this problem, and I'm prolly wrong here but...

It seems (to me at least) that all these problems are related to bootloader. Also, when I first got this error, I tried flashing an OEM ROM, and proceeded as suggested in the wiki (loaded this ROM and then, tried to change the bootloader).

Since it didn't solve the problem, I forgot about that... but the bootloader was NOT changed. It still reads

KAIS130 MFG

SPL-1.0.OliPof

CPLD-8

It seems to be the same with Kleze (he tried changing the bootloader but figured out it is protected).

Questions:

changing the bootloader wouldn't solve this problem ?

Isn't it being caused by an old HardSPL with a new OS (WM6.1) ?

What about the USB not being recognized ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] newtonik:
Stealth, sorry I am running out of answers here. I am mostly puzzled about the usb not working when you are in the rom but works when you are in bootloader (since you can mtty).

as for you questions

Yes, try to upgrade your bootloader if you are going to stick with WNM6.1

Mine reads

KAIS1(*)0 MFG

SPL-1.0.OliPof

CPLD-8

so a bit different.

and try to reformat the device if you don't mind.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] newtonik:
double post, sorry.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] StealthNet:
I took one of the (rare) times the cellphone booted, and transfered JumpSPL to it. Flashed HaldSPL to the phone sucessfully.

Problem is, now it boots to bootloader every single time, even if I connect to it with mtty, and issue "task 16 0" and "task 8".

I think that matters are gettings worse. Since it won´t boot to the OS anymore, I can´t even run JumpSPL to change the bootloader and try (my last idea) to get back to stock / oem ROM AND bootloader.

I completely ran out of ideas.

any1 ? :(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] newtonik:
so "set 16 0" or "set 14 0" don't help. Not sure what else