Related
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: )
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 )
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
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.......
Hello! Today my Kaiser (a T-Mobile Vario III) decided to brick. It ran out of power, I charged it up & back on, some texts were missing, performance was very sluggish, restarted it... & now it doesn't get part the T-Mobile startup screen, i.e. Windows Mobile doesn't boot.
Searching around draws me to only one place - here , where people modify their ROMS and troubleshoot similar problems. EXCEPT I haven't modded a ROM at all; this is a vanilla phone that just locks up as if the ROM has bricked.
T-Mobile support just tell me to upgrade Windows via ActiveSync, which of course I can't do as it won't boot. :headdesk:
I've used mtty.exe to try and READ data from the phone, & in the process read the FAQ, learnt about the bootloader, etc. I have not made ANY writes to the phone.
I suspect the phone is nearly physically full, somehow leading to filesystem corruption.
I have NOT yet tried a hard reset, as some pictures/texts from today would be lost, & I'd like to avoid that & somehow recover the data.
So:
Is there a way to copy filedata (photos, etc.) from the phone via the bootloader/mtty? I doubt it from my searches, but it's worth asking.
Is there a way to check/fix phone contents WITHOUT wiping it with another ROM?
Is there anyone who can help with the output from mtty.exe below? (Phone locks up at "UserStorageSIPreload" )
Or will I just have to suck it up & do a hard reset?
Code:
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 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 887 (0x377) is bad block
BLOCK 1189 (0x4A5) 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=0x8800
Partition[3], type=0x4, start=0x9540, total=0x11D80
CE Total Length(with sector info) = 0x4AEAA00
CE CheckSum Length(without sector info) = 0x4AA0000
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
Thanks, thanks, thanks in advance!
1-try removing ur battery for 10min then placing it back in.
2-If u have data on ur SD then its shouldnt matter if u hard reset.
3-final option, Hard Reset or upgrade ur rom.
Or be patient, maybe someone has better suggestions than me and will chime in for sure
GL
I tried those options, & a thorough search & trying out of the various tools - it didn't seem possible via the bootloader. It was just my texts & some pictures held on there which I deliberately didn't back up, & I'm fighting my urge to semi-obsessively document my life, so I let them go & hard-reset... thanks anyway guys.