Database Develop

Kaiser boots and resets, and boots, and resets, and...

Let me rephrase my problem as I've been reading here and didn't find a similar one. The problem is my Kaiser boots showing vodafone logo, then restarts after 15-20 secs.. and then it boots and restarts again and again and again.. I can go to BootLoader and has hardSPL, reflashed again but still the same problem happens!
I've flashed my Kaiser with RUU_Kaiser_HTC_WWE_3.03.405.0_radio_sign_25.70.40.02_1.64.06.04 and it worked flawlessly, however when I tried to flash it with Dutty's Ruu_Signed_Duttys_WM6.1_Hybrid_1.64.08.21 [RTM] my Kaiser keeps on rebooting-- I've checked the forums and found similar problems but I think it's unique for every other case (reverse block thingy) so I run mtty and here it shows what info 8 looks like:
Code:
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 20 (0x14) is reversed block
BLOCK 891 (0x37B) is bad block
BLOCK 892 (0x37C) is bad block
BLOCK 1621 (0x655) 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=0x9580
Partition[3], type=0x4, start=0xA300, total=0x10FC0
CE Total Length(with sector info) = 0x51D1800
CE CheckSum Length(without sector info) = 0x5180000
Anybody help please? I've just had this for about a week and this happened!!
EDIT: and by the way, service info is KAIS130 MFG SPL-1.0.OliPof CPLD-8

GLESON3 To The Rescue. If you ask real nice he may help you and be sure to buy him a pint, he will probably save you from getting a week old $500 Paper Weigh.
On another note Be very Careful with Mtty you can make the problem even worse.

That's the only thing I've inputted as I've seen similar guys posting the same problem and sending the same info-- when I bought the Kaiser the guy told me to download mtty because the phone doesn't want to boot without issuing 'boot' in the cmd... then when I flashed it to RUU_Kaiser_HTC it properly booted. Now I wanted to try Dutty's ROM and this happened

That's cool. But I just wanted to stress the importance of messing around at all in Mtty. Its like heart surgery, one slip and its over.
Not just for you but for anyone who stubbes across this thread. Mtty can be very dangerous use wisely.
http://forum.xda-developers.com/showthread.php?t=372305

It's midnight here. I will help you, but it will be tomorrow. Look in your PM's tomorrow, I wil send you my IM address.
YOU SENT ME A MESSAGE ABOUT TASK 2a. DO NOT DO IT!!!! If you do a task 2a & are not completely prepared with all the steps, there will be no helping you, at least for a long while.
I see your issue & believe I can fix it easily, but you'll have to find me in the morning. JUST DON'T DO THE TASK 2a as you suggested, no matter what. There is more to it than issuing the command & flashing a ROM is not it.

GSLEON3 said:
It's midnight here. I will help you, but it will be tomorrow. Look in your PM's tomorrow, I wil send you my IM address.
YOU SENT ME A MESSAGE ABOUT TASK 2a. DO NOT DO IT!!!! If you do a task 2a & are not completely prepared with all the steps, there will be no helping you, at least for a long while.
I see your issue & believe I can fix it easily, but you'll have to find me in the morning. JUST DON'T DO THE TASK 2a as you suggested, no matter what. There is more to it than issuing the command & flashing a ROM is not it.
Click to expand...
Click to collapse
Thanks Leon! will wait for your PM then

bump and just to add, when I flashed to Dutty's it went to 100% and rebooted.. but it's just reboots after 15-20 secs and it does this cycle over and over again

posting info 8 and boot log from mtty.. help please please please?
Code:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0xA300, total sector=0x10FC0
Storage start block=673, total block=1087
Total Bad Block in CE: 0
Erase physical block from 961 to 2032
formatstorage Bad block found: 1179
formatstorage Bad block found: 1180
formatstorage Bad block found: 1909
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++

flashed with stable 6.1 ROM using sd, still the same problem

Ahhh... Did you flash OS only, or the whole rom??? I couldn't tell from your PM.
At any rate, I'm still working on the next step, I hate to do it, but I think we'll need to format the device & flash a new version of SPL. Let me ask a Q of Olipro first.

See this link
Check out this link. Contained therein is a link which directly relates to your problem.
http://forum.xda-developers.com/showthread.php?t=383904
Scroll down the page just a little and I think you should be closer to resolution.
~Gwen

GSLEON3 said:
Ahhh... Did you flash OS only, or the whole rom??? I couldn't tell from your PM.
At any rate, I'm still working on the next step, I hate to do it, but I think we'll need to format the device & flash a new version of SPL. Let me ask a Q of Olipro first.
Click to expand...
Click to collapse
OS only from the file you gave me

SkunkyGwen said:
Check out this link. Contained therein is a link which directly relates to your problem.
http://forum.xda-developers.com/showthread.php?t=383904
Scroll down the page just a little and I think you should be closer to resolution.
~Gwen
Click to expand...
Click to collapse
You are telling me this:
http://forum.xda-developers.com/showthread.php?t=374388
But this didn't help and went cold a month ago

Finally found a similar problem:
http://forum.xda-developers.com/showthread.php?t=345470
but it seems it is not possible to do a task 2a and then recover from it in Kaiser.. now I'm really worried

MY KAISER HAS BEEN RESURRECTED!!
Many thanks to GSLEON3 for the help and patience he has given me
Another pint for you man, hope your work with jocky would be successful! (let me know when it's finished, I think I still need to delete the bad blocks so I won't be scared to re-flash it )

bootloader mode only?

When soft reset my Tilt will go into Bootloader mode if not plugged into USB charger only. Plugged into USB to PC goes to Bootloader when soft reset and as soon as plugged in the screen freezes and is unresponsive to any type of input/buttons. Nothing plugged in goes to Bootloader on soft reset. Won't synch, PC doesn't see it.
Got some help from GSLEON, but his solutions didn't work. I flashed his Jump spl and his Hard spl, worked, kinda, for a day or two, now it's as described above. I think GSLEON grew too busy, or disinterested, he did try but doesn't respond anymore.
Anyone else got a clue? Anyone know how to erase/delete the bad block shown below?
The screen reads;
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
running info 8 via mtty yields;
--- 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 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 221 (0xDD) 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=0x7B80
Partition[3], type=0x4, start=0x88C0, total=0x12A00
CE Total Length(with sector info) = 0x44A4600
CE CheckSum Length(without sector info) = 0x4460000
Any help would be appreciated.
Thanks,
Ed
Tilt running Blackwood rom and radio 1.27.14.0

sorry, but GSLEON knows what he is talking about and if he won't reply anymore I would only assume you weren't following his steps correctly and he got tired of spoon feeding "maybe". Sounds like you keep flashing back an incompatible radio or ROM which would cause it to recurre. If you can get the phone to sync with the PC then I would flash back the original ROM and start back at the beginning, maybe some Wiki reading would help.

I'm assuming he got busy, as he was when we started. Please don't assume I did anything wrong, even if you are sorry.
I followed his steps exactly, as we were on chat at the time. It seemed to work for a day, then went south. There isn't any bad rom or radio on it, they've been working for months. Suddenly a block went bad, hence the problem, according to GSLEON.
I find it hard to believe he is the only person on this site with that kind of knowledge willing to help. He is a good guy, and he doesn't assume incorrectly, he finds the facts.
I've read just about everything in the Wiki pertaining to the Kaiser, and done extensive searching on the problem. I only ask as a last resort, knowing, and understanding why, that newbs get flamed for not doing the research first.
If I could only get it to synch, I could live with it the way it is, alas the problem.
Thanks for your attempt at helping. I appreciate anything coming my way.
Ed
KDKobes said:
sorry, but GSLEON knows what he is talking about and if he won't reply anymore I would only assume you weren't following his steps correctly and he got tired of spoon feeding "maybe". Sounds like you keep flashing back an incompatible radio or ROM which would cause it to recurre. If you can get the phone to sync with the PC then I would flash back the original ROM and start back at the beginning, maybe some Wiki reading would help.
Click to expand...
Click to collapse

My Kaiser's playing dead! just boots to boot loader screen

Hi folks,
I wonder if anyone knows the answer to...
I had it flashed with 'Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06', which seemed to be working OK.
Then I soft reset it earlier today and it got to loading my today screen, screamed the battery was dead (it was nearly fully charged) and turned off.
I turned it back on and it was as though it was booting after the soft reset, or like I'd taken the battery out (I hadn't).
I couldn't get this to change, so I flashed it with Sleuth v3.0, one ive used very successfully before - then it had no sound at all once it had booted.
I tried another hard-reset and now it only shows the tri-colour bootloader screen, with the following details:
KAIS130 MFG
SPL-1.0.0.oliPoF
CPLD-8
USB
Anyone know what I can do?
Thanks in advance
'tunes

Check out this thread on MTTY. But be careful! One slip with MTTY and you could forever kill your phone.

done it - same thing!
I'm starting to get worried!
I've kept searching and tried everything I've found, with no rteal luck.
What I have found though, is that if I connect using MTTY, and use 'boot' - my phone boots and works just fine!
However, if I reset te device at all I just end up back at the boot loader screen.
Because I've tried all sorted, Here's the output of a few things from MTTY, it 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
############################################
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 ++
Anyone got any recommendations.....pleease?
A huge thanks in advance,
'tunes
Added details to a thread already discussing this:
http://forum.xda-developers.com/showthread.php?p=2244462&posted=1#post2244462
Feel free to remote this thread
'tunes

Need Help with a Tilt

First, let me preface my post by stating that I am a noob so be easy on me.
Secondly, let me state that the Tilt in question was NOT my phone. I received it in the state that it is in. With that being said, let me give the background of my situation.
Sunday: My friend woke up to see that his Tilt was giving the RLOD. He brought his phone into the store where the agent stated that he was gettin the RLOD because it had water damage (the strip is a light shade of pink). The agent told him that he would have to purchase a new phone. So he went ahead and purchased a new phone. That night, I'm at his house and I help him put some apps on his new Tilt. After doing so, I decided to try to research the RLOD problem because I wasn't convinced that water damage was the reason that it wasn't workin. He told me that I could keep it if I got it to work.
Monday: After gettin' the RLOD all sunday night and into Monday, I put a new battery into the Tilt and it starts up. So I go to the cingular store and I'm able to get a battery swap. After gettin' this swap, I give the phone to another friend of mine that is VERY familiar with these type of phones. He tried flashing HardSpl but it wouldn't allow him. I noticed that the phone wasn't charging either. Eventually the battery got low and all it would do is boot up into the bootloader screen. I left the battery out all night.
Tuesday: I pop the battery back in and it goes to the bootloader screen. I attempt to flash the original Rom but it said invalid vendor type. The only ROMs I could flash was the 1.51.502.0 Rom (with the 1.50 MFG SPL included), the 1.57.502.1 and the the 1.62.502.0. Running mtty I was able to boot up the first 2. I was unable to boot up the 1.62.502.0 Rom tho (task 8 didn't do anything). With the 1.57.502.1, I tried doing the "set 16 0", "task 28" and "task 0" function but I still had the same issue with where I was only able to boot up the phone through mtty. Everything else would result in bootloader screen. I then flashed the 1.51.502.0 ROM and had the same issues as with the 1.57.502.1. Doing info 8 with each of these ROMs revealed bad blocks. Being that the 1.51.502.0 Rom had the MFG 1.50 SPL included, I read that I could safely do "task 2a". I did task 2a but I got a message saying "Erase block FAIL" for the bad blocks that were there.
Since Tuesday: I realized that after I did that task 2a, i was able to flash the OEM ROM (only situation that I've been able to flash it). With the OEM ROM, the first "boot" through mtty reveals a bad block. The second "boot" does not. I'm still only able to boot the phone thru mtty though. Everything else results in bootloader screen. I kno that I need to flash HardSpl on my phone but I can't do it because a) my activesync won't detect this phone under any circumstance and b) whenever I try to flash a HardSpl with the CustomRUU executable, it stays at 0% and I get the "error 262 update error message."
I've been searching through these boards for three days and I don't kno what else to do right now. Being that I got this phone for free, I would like to get it to work but if i can't then it's no big deal. Any help would be greatly appreciated. Thanks in advance. Currently I have the OEM ROM on the phone (1.57.502.2).
Bootloader screen reveals:
KAIS1*0
SPL-1.56.0000
CPLD-8
Mtty information:
Cmd>info 0
Platform Model ID:KAIS1*000
Platform HW Board ID:31, PVT1
Cmd>info 2
HTCSCWS__001Ùü¤HHTCE
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 78 (0x4E) is bad block
BLOCK 226 (0xE2) is bad block
BLOCK 434 (0x1B2) is bad block
BLOCK 1669 (0x685) 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=0x9E40
Partition[3], type=0x4, start=0xAB80, total=0x10740
CE Total Length(with sector info) = 0x5615C00
CE CheckSum Length(without sector info) = 0x55C0000

So if you could warranty out the battery then you can warranty out the phone?

That wouldn't work. Apparently the battery issue was a common problem so they just switched it out without asking too many questions. If I wanted to get the phone changed, they'd ask more questions and more than likely not change it.

bump.......

[Q] Can't get a hard SPL to take.

Hi,
I am trying to update my Kaiser, so for the last few weeks, I have read LOADS of threads, FAQ's, and Tutorials on the subject.
I am very well versed in PC Hardware, and a bit of a technogeek, but this is the first smart phone I have had (a cast off from a friend of mine).
I have followed the many threads on the upgrading process, and have managed a few bits of the process, but I am now stuck at burning the Kaiser-HardSPL-3.56-Hard2.nbh.
(BTW I picked this because it seemed to be the latest version, and as I will be going to Win 6.5, I just thouight it "best" to start with).
I start up the PDA, wait for the OS, connect the USB cable and sync.
When that is finished, on the PDA, I run explorer and then run JumpSPL1.94-KAIS.exe from device memory.
The PDA reboots to the tri coloured screen and shows:
Security Unlocked
KAIS130
SPL-1.94.0000
CPLD-8
USB
I unplug the USB cable, wait for 15 secs, plug the cable back in.
On the PC, I un-tick 'Allow USB Connections', then I run KaiserCustomRUU.exe (with the .nbh file in the same folder).
The PC reports back that it is checking the information on the PDA, then the progress bar appears on the PC and the PDA.
They both jump to 100% in about 1 sec, then the PDA reboots itself. When I check the information on boot up, or with a 'camera-stylus' reset, the information displayed is exactly the same as it was before the procedure.
I've tried it on an XP (x32) machine using Active Sync, and a Win 7 (x64) machine using Windows Mobile Device Center, and I get the same results every time
I have performed many soft and hard resets of the Kaiser, many reboots of the PC's, and much cursing....
At the moment -
On boot-up, I have:
R 1.70.OliNex
G 25.65.30.04H
D 3.28.00.00
At the tri coloured screen, I have:
Security Unlocked
KAIS130 MFG
SPL-1.0.OliPof
CPLD-8
USB
Output from Mtty 1.42:
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 20 (0x14) is reversed block
BLOCK 648 (0x288) 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=0xAA40
Partition[3], type=0x4, start=0xB7C0, total=0xFB00
CE Total Length(with sector info) = 0x5C3BE00
CE CheckSum Length(without sector info) = 0x5BE0000
Cmd>
The OS is Windows Mobile 6.1 Pro
CE OS 5.2.19212 (Build 19212.1.0.3)
Am I being thick here ? or should the "SPL-1.0.OliPof" on the tri-coloured screen change ?
Please can someone give me a bit of guidance.
Thanks & Regards,
Paul

its done silly

ljohnson1981 said:
its done silly
Click to expand...
Click to collapse
So why doesn't the "SPL-1.0.OliPof" on the tri-coloured screen change to "HardSPL-3.56-Hard2" or something similar ?
Regards,
Paul

Moving to General. Hardly Development related.