Database Develop

ATT Tilt Stuck In Bootloader

Hey Guys,
Can anyone help me with this. I tried to use the SIM/CID unlocker here.
http://forum.xda-developers.com/showthread.php?t=375583
--
I did the Hard-SPL, then the Radio Update, but it failed @ 99%. Now my Tilt is stuck on the bootloader. When I remove the battery/put it back in, then turn on it just shows the tri-color screen. It says
Top Right Corner - RUUNBH
Under That - KAIS1*0
Under That - SPL-1.93.0000
Under That - CPLD-8
--
It's a brand new Tilt, no modifications or anything. Thanks!
I'd appreciate any help/suggestions. Can't believe i've been a member since 06, and haven't posted at all!!!
--
I tried re-flashing the Hard-SPL, and the Radio, but no luck.

Also, mtty output.
Cmd>task32
Command error !!!
Cmd>info 2
HTCSCWS__001Ùü¤HHTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1*00CS_0HTCE

One more thing, if my tilt is screwed and I have to return it. Is there any way I can clear all my data E.G. outlook calendar, tasks, etc... before I send it back?

arcdigital said:
One more thing, if my tilt is screwed and I have to return it. Is there any way I can clear all my data E.G. outlook calendar, tasks, etc... before I send it back?
Click to expand...
Click to collapse
i dont know enough about the boot loader process for the kaiser to be of any real help...but as for clearing data...u shouldnt have to worry about that most likly if ur phone woult load...
but if you are making it to boot loader ur still in good shape...try flashing the factory rom...most likly your gonna lose all ur data no matter what way you look at it....
good lucky my friend

Thanks, I don't care about the data if I can fix it, but I want my data gone if i'm returning to ATT. What factory rom should I try to reload? I tried loading "RUU_Kaiser_CINGULAR_WWE_.exe", but It gave me some invalid vendor id error.

Try flashing your Rom from your microsd card. Search the forum for "flashing rom from memory card" and you should find your answer.

what should i flash? The HardSPL?

arcdigital said:
what should i flash? The HardSPL?
Click to expand...
Click to collapse
From what I read it seems that your were successful in flashing the Hardspl but failed with the radio. If so follow this link and read how to flash your rom from your memory card.
http://forum.xda-developers.com/showthread.php?t=336158
Make sure you format your microsd card with Fat32 with 512kb sectors before you copy your rom files to the card.
I think this is a solution for you but I may be mistaken. Just ask me any question you have and Ill do my best to help.

looks like you didnt even get hardspl on the device, the spl version should say olipof if you did it right

what type of machine were u updating ur phone from? xp or vista?

I highly suggest before you brick your device, you quit listening to everyone and contact the only person I know of, who can actually save your device if it is still possible. While everyone is trying to help you, they are more than likely sending you further in to the hole and at some point you will not be able to climb out.
Look up GSLEON3. He can help. I have experienced it first hand. Trust me, I am sure if it is still recoverable, he is the only one I know of who can recover it. Trust me.
GSLEON3

Did I hear my name???
PLEASE don't try flashing a radio!!!!
While it's really nice that everyone wants to help, that last suggestion should ever be, "Flash Something". Yes, sometimes flashing an OEM rom with your CID can fix things, it can also royally screw things up deopending on what went wrong & why it happened. Some of the more troublesome bricks are caused by improper radio flashes & an RUUNBH error is seldomly caused by the radio portion of a flash with the kaiser.
On the other hand, it seems that you've played with MTTY a bit, so hook back up & do a cmd>info 8
That's info "space bar" eight (8), should look like this: cmd>info 8
Post you results so I can see where the bad info is, & I'll tell you how to proceed.
I also need to know what was the last working rom on your device, i.e. the stock AT&T rom, or the upgraded AT&T rom & I need to know everything you've tried to flash so far.

Just got back, i'll do the info 8 in a few. Last working was the stock ATT rom. It's brand new, wo/ any mods @ all. Bought it yesterday from ATT store. I tried flashing the Hard-SPL and then the Radio, but the radio failed, because I think the hard-spl failed but it didn't tell me.

I did all the infos I could think of .
Cmd>info 1
Cmd>info 2
HTCSCWS__001Ùü¤HHTCE
Cmd>info 3
HTCSÒ}¥%l3;}YÑvΞ–¦ù+W)
Cmd>info 4
HTCSCWS__001Ùü¤HHTCE
Cmd>info 5
Cmd>info 6
HTCST ÚÈÒHTCE
Cmd>info 7
CPLD ID=0x8
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 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 96 (0x60) is bad block
BLOCK 220 (0xDC) is bad block
BLOCK 490 (0x1EA) is bad block
BLOCK 491 (0x1EB) is bad block
BLOCK 618 (0x26A) is bad block
BLOCK 619 (0x26B) is bad block
BLOCK 1676 (0x68C) 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
Cmd>info 9
Storage Start Addr=0x55860000, length:0x83A3200
Cmd>info 10
Cmd>info 11
Cmd>

Man, I'm getting good at this.
:Slaps self on back: smiley: )

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.