Database Info

Need help with Tri-color screen!

Every time I run the Kaiser hard-spl, I get a bad command message as pasted in bold below. What am I doing run? I've been downloading and installing for weeks. I'm new to all this ROM stuff, but if it matters, my ROM version is 1.57.502.2 and ROM date is 08/25/07. Thanks in advance.
---------------------------------------------------------------------------
Kaiser JumpSPL is running on your device, please check your device
screen and follow the steps until you see the tri-color screen.
When done hit ENTER to continue...
Device screen should be now TRI-COLOR and show "USB"
===> PLEASE UNPLUG AND RE-PLUG THE USB CABLE NOW <===
===> PLEASE UNPLUG AND RE-PLUG THE USB CABLE NOW <===
===> PLEASE UNPLUG AND RE-PLUG THE USB CABLE NOW <===
ActiveSync icon should become gray after that.
When done hit ENTER to continue...
Phone screen should now be tri-color and the activesync icon gray
if not, the loading process has failed and you'll have to repeat it again.
If all was OK hit ENTER and the standard "PDA Phone ROM Update Utility"
window will start, allowing you to flash HardSPL on your device.
Hit CTRL+C to Cancel or ENTER to continue...
Follow the steps on the wizard to flash HardSPL, when finished your
device will reboot. It should last no more than 1 minute.
- Launching RUU, please wait...Bad command or file name
Process is finished, congratulations!
If you find it useful don't forget to donate

When I tried HardSPL I had a similar problem. My issue was that I configured the command prompt to automatically change directory to the root drive each time a CMD process is started and this caused the problem I as having. Most likely when you run the tool it's extracting files to a different directory. If that's the case verify you're not doing anything with a autostart registry key for CMD process. You can also look at the folder you run HardSPL from... when you run the command it should extract a few files and if that's not happening then you will get the above error.
I would also try this on another workstation/laptop if you have one available.

I'm sorry to take up your time, but can you please give me a step by step example of how this could be done? How did you do it for your phone? I will try to follow.

you guys need to check out the White screen Solved post.. there is a fix so you can flash rom's.. merry christmas!

MTTY (How to fix a bad ROM flash!)

Hi,
I didn't see any post about using MTTY on Kaiser.
If I did a bad ROM flash with my previous device (HTC Universal), I could always fix this by clearing the FAT table with MTTY.
Believe me... if you flash and it stops ad 85% you will be very happy if you can use this tool!
Reason I started this thread is to help out people who are having such a problem with there Kaiser!
This is the correct procedure to get you out of trouble
1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
2. put your device into the cradle
3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
5. type "task 8" to get your device formatted
6. type "task 0" to ask your device reboot
7. take the device out of the cradle, and manually reset it if it does not do that already.
Incase of an emergency it could be very helpfull I think!
Thank you all for providing the input in this thread so I could make this small user manual!
Happy flashing!
Leo

Well... seems like nobody bricked his device yet!
That's cool....

I've read in many places about people using MTTY on thier Kaiser to get it to boot after a bad flash, but I can't remeber where. And I don't know where they got their info from.

I could attach MTTY here but I'm a bit scared if I do is that people going to blame me if they brick there device!
That's why I'm asking someone has experience with it.
It could be usefull for a lot of people.
DaveShaw said:
I've read in many places about people using MTTY on thier Kaiser to get it to boot after a bad flash, but I can't remeber where. And I don't know where they got their info from.
Click to expand...
Click to collapse

You supply a ROM that people can use to Brick thier devices (if they don't Hard SPL).
I suppose that's why they invented Big Red Font's and disclaimers.
If you do decide to post it, I'd get _Alex_ or Mike to add it to the Sticky.
P.S. I have yet to expirence it myself.

Hahaha... yes you are right
Ok I will attache MTTY.
Thanks,
DaveShaw said:
You supply a ROM that people can use to Brick thier devices (if they don't Hard SPL).
I suppose that's why they invented Big Red Font's and disclaimers.
If you do decide to post it, I'd get _Alex_ or Mike to add it to the Sticky.
P.S. I have yet to expirence it myself.
Click to expand...
Click to collapse

MTTY (How to fix a bad ROM flash?)
Is this thread can help you ?
http://forum.xda-developers.com/showthread.php?t=370169
I can't find the original post that talk about the procedure to unbrick kayser with
MTTY.

Hi !
I used it once.
The "info 2" works as designed ;-)
greetz

A clear procedure would be nice so you can unbrick your device easy using MTTY.
Thanks,
tyoine said:
Is this thread can help you ?
http://forum.xda-developers.com/showthread.php?t=370169
I can't find the original post that talk about the procedure to unbrick kayser with
MTTY.
Click to expand...
Click to collapse

Thanks for confirmation!
flushbeer said:
Hi !
I used it once.
The "info 2" works as designed ;-)
greetz
Click to expand...
Click to collapse

If you have a bad flash....that's no reason to worry.
I haven't had to use MTTY to recover.
In most cases, if there's no issues with the Rom itself...you can pop out the battery and re-flash the same ROM from BootLoader Mode. This will also work if for some reason your computer crashes or loses power & restart during the FLASH.
If the Rom has issues.....the flash will not complete and the device will be stuck in BootLoader Mode. At this point,you must FLASH a FACTORY ROM!!
Pop the battery off 1st, power up the device, device will power up in BootLoader Mode, connect to pc & FLASH your devices FACTORY ROM. This will restore your device back to it's original out the box settings.
The above only works if the device has been put through the Hard SPL or SuperCID process.
I personally have never tried to flash a cooked ROM without unlocking any of my devices. From what I've read what others have experienced...the flash would just fail and they're stuck in BootLoader Mode.
Myself ... I've experienced bad flashes, bad cooked roms that I've cooked, lost power to a pc & had my pc crash during a flash. Listed above is how I've recovered. There is life after Bootloader Mode.
The only time you have to worry is if your device does not power up at all
As a public chef...it's your responsibility to set the parameters of your ROM! Meaning, Radio, HardSPL, program conflicts, etc.
You are not ultimately responsible if someone bricks their phone but if they pushed the issue, you could be hit with some form of liabilty because you failed on providing a simple Disclaimer that sets the expectation.
I hope I've been helpful.....

That's clear
Thank you,
Leo

Okay, MTTY is a very useful tool & can help save your butt on many occasions.
A few of those occasions include:
1. Bad flash or installation of HardSPL
2. Bad Flash of a ROM.
There are several other problems that can arise & be mended with the use of MTTY. The most common use is for recovery of any flash process resulting in an RUUBNH error.
For most of these error you want to use MTTY to reboot the low level CE of your device to flush out any bad blocks.
Use of MTTY to recover from these errors is usually simple. The basic outline of how to use MTTY to resolve these errors is as follows:
1. Right click on the quicklaunch activesync icon on the lower left quadrant of your pc. (You can also just open up the A/S program)
2. Select Connection Settings.
3. Uncheck the box labeled "Allow USB Connections" & then Click "OK".
4. Open MTTY & select "USB from the Port options drop down menu.
5. Select RTS/CTS from the Flow Control Settings & click "OK"
6. Pay attention, because for a brief mmoment MTTY wil report whether or not it could establish a port connection to USB. If you are successful, a Command window will open.
7. Hit the "Enter" key on your PC twice. You should then see a command prompt that looks like this "cmd>".
8. At the command prompt (cmd>) you should enter the command "boot".
This will reboot the device & report back about any errors or bad or erased blocks.
9. If your device was just hung, it should be fine after the reboot. If it returns to Boot Loader however, it means there was a problem with bad blocks.
10. If errors were reported & you end up back at the Boot Loader screen, then repeat the "Boot" Comand at the (cmd>) prompt.
It can sometimes take two or three boots to fully recover from RUUNBH errors, so if at first you don't succeed keep trying & remember to keep notes about any errors reported in the MTTY info window.
Other Information: MTTY needs to have full access to the USB port. Some anti-spyware, anti-virus & firewall programs can prevent MTTY from gaining the port access it needs. McCaffee in particular should be temporarily disabled & some firewall programs may also need to be disabled.

don't work damn
this is my pda
RUUNBH
KAIS 130
SPL-1.93.0000
CPLD-8
USB
this is mtty
cmd
Command error !!!
Cmd>boot
Command error !!!
Cmd>

this rom RUU_Kaiser_ATT_WWE_1.51.502.0_Radio_sign_22.45.88.07_1.27.11.31_Internal.exe start, but at 1% kaiser reboot...

anyone know how much htc customer care ???

pedro_se_rooot said:
anyone know how much htc customer care ???
Click to expand...
Click to collapse
When I sent mine in to look at a problem with connecting via 3G, I was quoted:
a) I'm responsible for shipping to the centre in Texas, US. (Don't know if there might be one closer to you).
b) There would be a charge of USD$28 for diagnosing the problem and producing an estimate to fix. They would call me with the estimate.
c) If I agreed to the fix, the $28 charge would be waived and I would be charged the estimated amount.
d) If I decided against the repair, I would be charged the $28 fee.
e) They would also charge for shipping the unit back to me, typically, about USD$50 for North America.
In my particular case, however, they have repaired the phone and shipped it back -- apparently at no cost to me, other than getting it down there. I guess they figured it was a 'in warranty' problem.
/drt

Hi there,
Is your device dead or still responding?
Can you come into bootloader?
Did you follow this step before you connected your device and opened MTTY?
It's very important you do!
1) Kill activesync processes: Ctrl+Shift+Esc in Windows to bring up Task Manager. Kill wcescomm.exe and WCESMgr.exe (by selecting the task on the processes tab, and clicking the End Process button below)
Please tell me?
pedro_se_rooot said:
don't work damn
this is my pda
RUUNBH
KAIS 130
SPL-1.93.0000
CPLD-8
USB
this is mtty
cmd
Command error !!!
Cmd>boot
Command error !!!
Cmd>
Click to expand...
Click to collapse

the device iss not dead (i think) but with Mtty work only info and task 8.
i've follow all the step and killed active sync.

EUREKAAAAAAA
i've follow this guide
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
3. put your device into the cradle
4. Run mtty (from downloaded) Choose WCEUSBSH001
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.

o2 P863MTTY操作后不开机安装驱动可以连接求救（operation will not boot, install the driver can be conne）

o2 P863MTTY操作后不开机安装驱动可以连接求救（operation will not boot, install the driver can be conne）
Polaris o2 P863MTTY操作后不开机，安装驱动可以连接求救！！
Polaris o2 P863MTTY operation will not boot, install the driver can be connected for help！！
P863是在MTTY下执行了task 2a出现下面显示后就手机不能开机，也进不了三色屏，用数据线连接到计算机后，有提示找到硬件并且成功安装 驱动！！
P863 is carried out under the MTTY appear task 2a shown below after the phone can not boot, but also could not enter tri-color screen, using data lines to connect to the computer, there are tips to find the hardware and successfully install the driver! !
Enter Radio Image
POWER OFF PMIC VREG_USB : SUCCESS!
C VREG_USB : SUCCESS!
F PMIC VREG_USB : SUCCESS!
R OFF PMIC VREG_USB : SUCCESS!
POWER ON PMIC VREG_USB : SUCCESS!
启动MTTY，执行 setboot 0 和 cego 两条指令，手机不能退出OEMSBL。
Start MTTY, implementation and setboot 0 Cego two commands, the phone can not withdraw from the OEMSBL.
按照此文章方法（In accordance with the methods of this article）：http://forum.xda-developers.com/showthread.php?t=393337
到（7) Run MTTY (COMn) and carefully enter following commands:
echo_on (the reply in MTTY should be "ECHO ON MODE")
setboot 1）这一步就进行不下去了！！！希望机可以救活！（This step does not go on to carry out! ! ! Looks can be saved!）

The Franken Kaiser tool is for Kaiser's only and requires that you have a certain radio version installed (1.65.17.10).
It will require changing to run on other devices (even if they are similar) and requires the "Radio from hell" also.
EDIT:
Also, doing a task 2a has probably formatted the entire NAND including the SPL (bootloader). task 2a should "NOT" be run on newer HTC devices.
Thanks
Dave

As my Polaris (o2 P863, HTC P860) how it can be resumed？？？

I can not accept not completed end-of-life can not be repaired, Vogue can，
Caesar can

So is your polaris stuck in OEMSBL ???I Cant read the thread title .Is your polaris security unlocked ?? might be able to recover if it is ? try set info and see if your secur_flag is 0,0.

Stuck in oemsbl
Hi,
My TC also cannot boot, and I think it's stuck in oemsbl after task 2a.
It is security locked, So it can be fixed?
Thanks

Hi Experts,
Pls help....

[HELP!] My NAND is faulty. What can I do?

Hi there! This was my experience with Android:
http://forum.xda-developers.com/showthread.php?t=792004
I had a couple problems when I was with WM. Sleep of death and so on.
Changed SD card and it seemed to be working fine.
Now, I need my phone so switched back to WM.
Install wizard went fine. But now it doesn't boot
Linux Kernel keep saying me "block xxx bad" where xxx is a number (578, 543 and 643).
What can I do?
Pleeease help! =(
Thanks a lot!

hi
same thing nappened on my polaris 200. 2 bad blocks on nand. android works fine. task 28 helps (format nand). is there a solution to skip bad sectors?

ion_plugged said:
same thing nappened on my polaris 200. 2 bad blocks on nand. android works fine. task 28 helps (format nand). is there a solution to skip bad sectors?
Click to expand...
Click to collapse
Android works, too. But it doesn't take too much to hang and start with those force-closes errors.
I did task 29. I don't know if it's the same.

Hi! I was out for exams at University.
Last thing I tried was doing task 2a at MTTY.
I know, BIG BIG mistake. Polaris is dead since then.
I'm living now with a Siemens [email protected] LOL.
Is there any new with this? Is there any procedure I can do to bring it back?
I don't have enough money to send it to service

Seems the polaris gets to an end because of hardware reasons.
i have the first bad block as well.. dont know.. i cant get wifi to work atm i hope its working after wimo flash again.
As far as i know after your 2A the device is dead.
I think repair would be more than buying a new device.
Maby you can try your luck on a wildfire. Here in germany was a action, offering it for 100€ and many people bought more thanh one device to set it on ebay.

Moved of: HTC Polaris: Touch Cruise > Touch Cruise ROM Development
To: HTC Polaris: Touch Cruise > Touch Cruise General
Please put your questions to: Touch Cruise General

dertester123 said:
As far as i know after your 2A the device is dead.
Click to expand...
Click to collapse
There is a patched version of frankenkaiser for the polaris to recover from a task 2a.

dertester123 said:
Seems the polaris gets to an end because of hardware reasons.
i have the first bad block as well.. dont know.. i cant get wifi to work atm i hope its working after wimo flash again.
As far as i know after your 2A the device is dead.
I think repair would be more than buying a new device.
Maby you can try your luck on a wildfire. Here in germany was a action, offering it for 100€ and many people bought more thanh one device to set it on ebay.
Click to expand...
Click to collapse
I read somewhere that bad blocks are common, even if the device is brand new. The point is that it seems there are certain blocks that cause bad functionality if they're damaged. :/
Buying a new phone isn't a solution for me, since I don't have enough money for that.
mmelo76 said:
Moved of: HTC Polaris: Touch Cruise > Touch Cruise ROM Development
To: HTC Polaris: Touch Cruise > Touch Cruise General
Please put your questions to: Touch Cruise General
Click to expand...
Click to collapse
You're right, wrong forum.
Thanks for moving!
meknb said:
There is a patched version of frankenkaiser for the polaris to recover from a task 2a.
Click to expand...
Click to collapse
I tried the patched version made by jpg001. But it gets stuck in
Code:
Just be patient while I'm working ...
7e 4e 7e
I'll give a try again tonight with every FrankenKaiser version possible.
I really need my Polaris back

Those numbers don't look right
Code:
Just be patient while I'm working ...
7e 4e 7e
are the motoq drivers installed ?are using the right port ? don't try another frankenkaiser version as they will flash the kaiser spl which won't work you need a copy of a original spl.nb.

meknb said:
Those numbers don't look right
Code:
Just be patient while I'm working ...
7e 4e 7e
are the motoq drivers installed ?are using the right port ? don't try another frankenkaiser version as they will flash the kaiser spl which won't work you need a copy of a original spl.nb.
Click to expand...
Click to collapse
That happens in step 10.
MotoQ drivers installed works with mtty, QPST and the step 7 of the guide.
I'll try downloading new ones tonight

The drivers seem fine if you can connect with mtty ect.What is your SECU_FLAG "security unlocked" in mtty try setinfo 8,the button combo for 8b is keep your finger on the green send button and the power button,that will boot into oemsbl on a security unlocked polaris.

meknb said:
The drivers seem fine if you can connect with mtty ect.What is your SECU_FLAG "security unlocked" in mtty try setinfo 8,the button combo for 8b is keep your finger on the green send button and the power button,that will boot into oemsbl on a security unlocked polaris.
Click to expand...
Click to collapse
Thanks A LOT for your response.
I'm not at home right now. Tonight I'll post the results, but as far as I remember, every field was blank.

Faulty nand
Well i am here after a task 2a. android and wm wont flash, redio did not change and i formated the nand. i have moto q drivers and i am connected to mtty but i don't have a workuing frakin kaiser for polari (some dll mising and corrupted archives) and i don't have an original spl. from where can i take one?

meknb said:
The drivers seem fine if you can connect with mtty ect.What is your SECU_FLAG "security unlocked" in mtty try setinfo 8,the button combo for 8b is keep your finger on the green send button and the power button,that will boot into oemsbl on a security unlocked polaris.
Click to expand...
Click to collapse
Ok, this is my output:
Code:
SetHTCRegionInfo: block=0, CID=, PID=, IMEI=, SECU_FLAG=0
oemsbl 1
Later I'll screenshot every step. Maybe I'm doing something wrong.
ion_plugged said:
Well i am here after a task 2a. android and wm wont flash, redio did not change and i formated the nand. i have moto q drivers and i am connected to mtty but i don't have a workuing frakin kaiser for polari (some dll mising and corrupted archives) and i don't have an original spl. from where can i take one?
Click to expand...
Click to collapse
Here you are:
CYGWIN1.DLL: http://www.mediafire.com/?l7m92ix5cdknmum
And for SPL, you should extract it by using "NBHEXTRACT" (search this forums for it), and run it with your stock ROM. It will give you the original SPL file.
Regards!

Sorry for double-posting. I'm acting like a total noob. I am.
This is what I did:
Notes:
- I usually get some error after typing the first command.
- CYGWIN1.DLL used is the same as I posted before. Got it from the Internet.
4) Connect MTTY COM4.
Type "setboot".
Type "radata 90000000 1". Nothing is echoed to screen.
Close MTTY.
5) Replug USB cable.
(I called FrankenKaiser.exe as fkaiser, for faster typing)
6) Run FrankenKaiser in a DOS box: fkaiser.exe /dev/com4 SSPL.nb.
Got "7e 02 6a d3 7e"
Replug USB cable.
7) Run MTTY and type:
Code:
echo_on
setboot 1
mb 9debbc
mw 9debbc 1 31313131
mw 9debc0 1 31313131
mw 9debe4 1 00000000
mb 9debbc
(as I did this many many times, nothing is changed).
Code:
setinfo
powerdown
Close MTTY
8a) Unplug usb cable, remove and reinsert battery, replug usb cable.
Connect with MTTY:
Code:
echo_on
setboot 1
Close MTTY.
Uploaded with ImageShack.us
8b) Unplug usb cable, remove and reinsert battery, replug usb cable.
Connect with MTTY:
Code:
echo_on
dload
Close MTTY.
Right before "dload" command, I'm pressing Send (green button) and power button all togheter.
9) Replug USB cable and then wait 10 seconds.
10) Run FrankenKaiser in a DOS box: FKaiser.exe /dev/com4 SSPL2.nb
NOTE: My SSPL2.nb was extracted from HERE (XDA FTP) with NBHExtract.exe.
Get "7e 4e 7e", not "7e 02 6a d3 7e"
11) Replug USB cable, wait 10 seconds.
Run MTTY:
Code:
echo_on
setboot 0
cego
Pressing camera button right before typing "cego".
MTTY doesn't show anything. Typed 3 times "echo_on", and nothing. Tried anyway to proceed, but unsuccessfully .
Here is the link of the extracted SPL from the original ROM, and the extracted SMI.BIN from QPST, if it helps for something.
Original SPL: http://www.mediafire.com/?pt4958k9isw77k2
SMI.BIN: http://www.mediafire.com/?bmupdccl78sicu0

Your phone is security unlocked so you wont need to run the mb mw commands in step 7 again that's just for security unlocking, its just step 10 where it's failing you could try setboot 1 before dload ie
Code:
echo_on
setboot 1
dload
Do you know which radio version you have?

meknb said:
Your phone is security unlocked so you wont need to run the mb mw commands in step 7 again that's just for security unlocking, its just step 10 where it's failing you could try setboot 1 before dload ie
Code:
echo_on
setboot 1
dload
Do you know which radio version you have?
Click to expand...
Click to collapse
Thank you very much for your response.
As MTTY says, my radio version is 1.59.46. It should work with FrankenKaiser.
Maybe the SSPL2.nb I'm using is not the correct one.
I'll try right now
EDIT: I tried with setboot, without doing all the steps, but FrankenKaiser keeps me throwing "7e 4e 7e".

The only other thing i can think of is try booting with the power button and the end key "red one" i cant remember what mode that boots.If you have qpst you can check what mode your phone is in once you find out its in dload mode run frankenkaiser.
The original spl's are all here

meknb said:
The only other thing i can think of is try booting with the power button and the end key "red one" i cant remember what mode that boots.If you have qpst you can check what mode your phone is in once you find out its in dload mode run frankenkaiser.
The original spl's are all here
Click to expand...
Click to collapse
You're right, thanks. I'll check with QPST which mode is my phone in.
By now, I tried the following combinations:
Power + Camera + Send
Power + Camera + End
Camera + Reset press
And still "No phone". I'll let you know any news
EDIT: Tried every combination possible, still nothing.
When i enter "dload", any command written on mtty won't response. And QPST still saying "No Phone".
I know the device is security unlocked because if I write "h" I get this command list:
Code:
For a help screen, use command ? or h
Available monitor commands are:
? [command]
h [command]
mb [StartAddr [Count [Filler]]]
mh [StartAddr [Count [Filler]]]
mw [StartAddr [Count [Filler]]]
setboot [0/1/2/3]
setatcmd [0:SIO/1:UART/2:USB/3:DPRAM]
setsmdloop [0:disable/1:enable]
setmpatch [0x1: CPU Freq/0x2: acoustic/0x4: simdoor/0x8: RTC]
setiot [0:Disable/1:Enable]
eraseall [erase all setting flags]
setdiag [0:USB/1:UART/2:DPRAM/3:SIO]
partition
checksum
format
setinfo
readadc
cego
setgpio
getgpio
gpio
version
powerdown
platformid
radata
showexplog [n]
usbdppulldown [n]
usbdmpulldown [n]
usbdppullup [n]
usbdmpullup [n]
Headsetpullhigh [n]
rfid
wpmic [PM_VREG] [0/1]

Have you checked the port's on qpst under add new port untick show serial and usb/qc diagnostic ports.I've just checked on mine if i power on with my finger on the end key it say *download* in qpst.

Frankenkaisers for different radio versions

In this threat i gonna upload some patched frankenkaisers for different versions.
With "FrankenKaiser" you can unbrick "task 2a" bricks:
There is no SPL, Splash and OS present as "task 2a" formats the entire application area.
Before FrankenKaiser there was no method available to unbrick and therefore they were called "hard bricks"
With frankenkaiser you can also revive kaisers where you don't see anything on it but is detectable (after turning on your device) in windows as an other device:
you got stuck in the OEMSBL and you can only talk to your device with mtty.
Credits goes to Jocky Wilson who created the original frankenkaisers. (Paypal to [email protected])
I've only changed them to work with different versions.
These versions are created at forum user requests.
Method to dump your rom:
1. connect your bricked phone and power it on
2. connect with MTTY to diag port COM#: (look up # in device manager)
3. type "radata" followed by enter (you'll see a parameter error message)
4. type "GO2AMSS" followed by enter
5. your phone should now change to "QC download mode"
6. use "QPST Memory Debug" tool to dump smi.bin and ebi.bin
7. zip smi.bin and upload it to Rapidshare (or any fileshare service) and send me the link
oemsbl: V1.9309
Radio: V1.71.09.XX
Verified.

oemsbl: V1.9519
Radio: V1.70.19.XX
20110823: new version uploaded

oemsbl: V1.9529
Radio: V1.65.29.21

oemsbl: V1.9518
Radio: V1.70.18.xx

Frankenkaiser for other versions can be created in this thread

Excellent work massivekid, just what I needed to fix the 600+ bad blocks on my spare Kaiser! Thank you!
You da MAN!!!

Turns out I cannot use any of this because my laptop has NO COMM ports.
Unless I can find a USB to serial adapter and force a COMM port, I'm stuck.

You don't need a com port. If your phone is in OEMSBL then it will ask for a different driver. This driver will create a virtual com port on your computer thru USB.

First of all, thanks for creating frankenkaisers for different radio versions,
but I need some help, my radio is version V1.71.09.XX, I did all the steps to rescue the phone up to step 11, and when I connect the usb to computer, windows shows an error and wont recognize the usb connector, not allowing me to flash the hard spl through usb. would be absolutelly happy if you would help me solving this.

Do you see the tricolor screen?
Did you disconnect and reconnect the usb cable again and do you see USB on the tricolor screen?
if no usb is seen, redo steps 7-10 again (after pulling your battery) but this time in step 9 run FrankenKaiser with the other SPL "sspl-0.92-jumpspl-force-usb.nb".
this will force usb detection.

i redid steps 7-10 at least 10 times already, tri-color screen shows up with the first spl and gives problem when connecting the usb, when I try the 0.92 spl the screen stays black (I tried connecting the usb even with it staying black and the same error message showed up)
*During the whole step by step the only difference I saw between my results and the screenshots was the oesmbl version on screenshot 7, where instead of a "2" there was a "1"

And did you tried the "sspl-0.92-jumpspl-force-usb.nb" at step 9?

If you enter mtty and type ? or h what is the output of the command?
if you see a lot of commands, then your device is security unlocked.
the "sspl-0.92-jumpspl-force-usb.nb" file is to force USB connection so you can connect with usb.
If that doesn't work, try with the original spl and after cego, pull the usb cord quickly and if the tricolor appears, try to connect the usb again.

after typing "h"
Available monitor commands are:
? [command]
h [command]
mb [StartAddr [Count [Filler]]]
mh [StartAddr [Count [Filler]]]
mw [StartAddr [Count [Filler]]]
setboot [0/1/2/3]
setatcmd [0:SIO/1:UART/2:USB/3PRAM]
setsmdloop [0:disable/1:enable]
setmpatch [0x1: CPU Freq/0x2: acoustic/0x4: simdoor/0x8: RTC]
setiot [0isable/1:Enable]
eraseall [erase all setting flags]
setdiag [0:USB/1:UART/2PRAM/3:SIO]
partition
checksum
format
setinfo
readadc
cego
setgpio
getgpio
gpio
version
powerdown
platformid
radata
showexplog [n]
usbdppulldown [n]
usbdmpulldown [n]
usbdppullup [n]
usbdmpullup [n]
Headsetpullhigh [n]
rfid
wpmic [PM_VREG] [0/1]
the "sspl-0.92-jumpspl-force-usb.nb" gives only blackscreen on the phone, no tri-color.
I`ll try the first spl and take out the usb quickly.
Same result after pulling usb quickly after doing the command "cego"
Tried the same with sspl-0.92 and the blackscreen apears the same way, and the error message on windows is the same:
(translation might no be exact because my windows is in portuguese)
"One of the usb devices connected to this computer had a problem and windows can not recognize it. to get help click on this message.
After clicking it shows a windows with a root usb hub, 4 usb doors being one of them the one where the phone is connected with a red X before it.
Ps.: I`m not exactly sure, and I don`t know if this might influence on anything, but if I remember right, when first unlocking my phone, the JumpSPL1.56-KAIS.exe wasn`t effective, I needed using one of the other 2 jumpspl available on that thread.

With "sspl-0.92-jumpspl-force-usb.nb", you can also try after cego to press and hold camera to enter tricolor bootloader mode
Also you can try this spl: SPL3.56-patch-nostuckinSPL-FORCEUSB.nb at step 9?
Just unzip it in your folder and use it.

when using the sspl0.92 it wont go out of the blackscreen (even holding camera button), and the same error message is shown on usb
when using the new spl3.56 the usually blinking green led stay orange after the cego command and the screen stay black, tried holding the camera button, to no effect in either "spls".
Same usb error on three spls...

The error states that the device is halted and is not handling usb functions anymore. The one that has the tricolor screen, should work, but some devices are not detecting the usb correctly. Therefore the usb force spl are created.
I'll try to find out how we can overcome this...

thank for your attention and taking your time to help me, hope you can find a solution, surelly you will help many kaiser owners that got many "bad blocks" in memory...
(shouldn`t ever have tried to put android on nand...)
keep me informed on any kind of progress and let me help you on testing.

Ok, try this one:
Remove and reinsert battery, then hold the send button and power on. Connect with MTTY (COMn) and this time enter "dload" to put phone in dload mode Continue with step 9.
Try SPL1.56-KAIS-unbricker.nb then or sspl-0.92-jumpspl-force-usb.nb

tried it, no letters under the: "Just be patient while I'm working ..."
believe the phone hunged up, will try again.
(also tried using the send button whenever turning the phone on in the steps 7 through 10, nothing different happened, I believe the jumpspl can only be loaded while in setboot 1 I`m thinking about trying to use "cego" without typing setboot 0 before...)
Phone will absolutelly lock if I dont enter setboot 1 in the step before typing dload,
frankenkaiser isn`t able to access it (no letters under te message to wait) and it locks after the frankenkaiser attempt (wont accept mtty commands), removing battery returns to "normal" (as in dead kaiser).