Wasn't Sure how this happened, but my Tilt started to display the tri-color screen every time I turned it on. If I connect it to my pc The display will change to USB, and I can flash new roms from usb or sd, currently using Dutty's. But Whenever I finish the flash and the device resets it just returns to the tri-color screen. I am also unable to hard reset the device. The funny part about is that one time the device booted the new rom, and I thought it worked, but after having to reset the device it returned to the tri-color screen. I have searched the forums, and cannot find any way out of this. Thanks in advance.
My Specs:
AT&T Tilt
Hard SPL 1.0.0lipof
Dutty's current rom
mykezia said:
Wasn't Sure how this happened, but my Tilt started to display the tri-color screen every time I turned it on. If I connect it to my pc The display will change to USB, and I can flash new roms from usb or sd, currently using Dutty's. But Whenever I finish the flash and the device resets it just returns to the tri-color screen. I am also unable to hard reset the device. The funny part about is that one time the device booted the new rom, and I thought it worked, but after having to reset the device it returned to the tri-color screen. I have searched the forums, and cannot find any way out of this. Thanks in advance.
My Specs:
AT&T Tilt
Hard SPL 1.0.0lipof
Dutty's current rom
Click to expand...
Click to collapse
Sounds like a bad flash that has thrown up RUU flags. I suggest you look up the name GSLEON3 before you turn it in to a brick.
P1Tater said:
Sounds like a bad flash that has thrown up RUU flags. I suggest you look up the name GSLEON3 before you turn it in to a brick.
Click to expand...
Click to collapse
Can you elaborate on what an RUU flag is?
Can a bad flash be caused by flashing and while in the middle pulling USB cable?
Is this error recoverable?
EXACTLY the same thing happened to me starting last Saturday. Normal power on after a 2 hours off and tri-color screen (2700 miles from home and from a high speed connection). Repeated after every soft and hard reset for 10 minutes. Then took battery out, reinstalled it and then all was normal when turned the thing on again. Flashed Dutty's 19400 on Sunday and all was normal, til normal power on on Monday morning. Then tricolor and it stayed that way for about 8 hours - soft, hard or battery out reset. But it did remain USB visible to the laptop so I installed the apr 16 and the other dutty's versions. ALL flashed good, but when started they ALL went tricolor. Then on a battery out restart all was good again. Spent most of today facing the tricolor again, but have dutty's 19700 (April 29) now installed and its working fine. I have determined that a reset (soft or hard) will likely cause the tricolor, but that sometimes a battery out then resinstall will get a normal restart, but not always. I don't think this is a software or
ROM issue, but a mechanical/electronic issue that HTC or (less likely) ATT should look into.
P1Tater said:
I suggest you look up the name GSLEON3 before you turn it in to a brick.
Click to expand...
Click to collapse
one up on that one....if you dont read and do what GSLEON3 has on these issues...i see you like P1Tater....looking for a new tilt!!!!
renembarr said:
one up on that one....if you dont read and do what GSLEON3 has on these issues...i see you like P1Tater....looking for a new tilt!!!!
Click to expand...
Click to collapse
QFT
Yep , GsLEON3 told p1tater to dip his tilt into water, but he got creative and dip into oil instead. Now the only thing he can do is to flash it with a zippo .
If you flashing it with your girl friend and someone pull you out, thats the worst thing can happen right there. Same for the tilt !!!
Seriously, dont take anyone advice if he is not an expert in unbricking. One wrong move and you follow p1tater fate.
>>>GSleon3 saves the day !
jon_k said:
Can you elaborate on what an RUU flag is?
Can a bad flash be caused by flashing and while in the middle pulling USB cable?
Is this error recoverable?
Click to expand...
Click to collapse
1. GSLEON3 is better equipped to answer this. From what I gather it's just a flag on a block that wont let you overwrite it until you clear the flag.
2. Exactly.
3. Most of the time yes.
Yep, pulling the cable while flashing is never a good idea, LOL.
The RUU Flags are Rom Update Utility "flags", meaning the device is still expecting rom data to be downloaded. Depending on where you were in flashing can determine how hard it will be to recover.
90% of the time there is a quick & easy solution, you know what the other 10% means, a bit more work or a new device.
Does your tri-color screen have the letters RUUNBH anywhere?
Thanks
To Answer GSLEON3 no it did not,
I finaly got it to boot the new dutty rom using MTTY
I used the command "set 16 0" then rebooted.
I am sure this is a temporary soulution, but It is better than a none for now.
When I ran the boot command of MTTY The Screen started to turn purple, then White, then back to tri-color. The computer diplayed that some .txt file failed.
I belive It had Kaiser in the name. I guess I'll lok into it more when I next have to reboot.
mykezia said:
To Answer GSLEON3 no it did not,
I finaly got it to boot the new dutty rom using MTTY
I used the command "set 16 0" then rebooted.
I am sure this is a temporary soulution, but It is better than a none for now.
When I ran the boot command of MTTY The Screen started to turn purple, then White, then back to tri-color. The computer diplayed that some .txt file failed.
I belive It had Kaiser in the name. I guess I'll lok into it more when I next have to reboot.
Click to expand...
Click to collapse
What does the tri-color say? What SPL does it show? Not what you think, but what the tri-color actually says.
On the Tricolor Screen it says:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Then either:
Serial/USB
My MTTY Screen:
Cmd>set 16 0
Cmd>boot
InitDisplay: Display_Chip=1
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 HC card
SD Init OK
SDFATChkConf: RhOpenFile() failed KAISCONF.txt
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
I've only done this twice now and the second time it no longer showed the purple screen after the boot command.
Have you done an cmd>info 8 on the device via MTTY yet? If so post it. If not, do it now.
+1
I flashed last dutty yesterday. no problem so far. and today with a soft reset i have this tricolor screen.
I will try remove the battery :'(
EDIT:
Remove battery didn't change anything.
I booted the kaiser using mmty
(And i did'nt succeed to get active sync connect to the kaiser, so no new flashing)
an other soft reset get me to the tricolor screen.
so here is info 8 log for me:
--- 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 1026 (0x402) is bad block
BLOCK 1199 (0x4AF) is bad block
BLOCK 1732 (0x6C4) 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=0x94C0
Partition[3], type=0x4, start=0xA200, total=0x110C0
CE Total Length(with sector info) = 0x5151000
CE CheckSum Length(without sector info) = 0x5100000
Click to expand...
Click to collapse
AND when i type boot:
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 ++
FMD_ReadSector+, bad block no=0x14880, status:0x0
FMD_ReadSector+, bad block no=0x173C0, status:0x0
UserStorageSIPreload --
OSSIReadBack --
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage crc of Mini-Kernel:0x363F76C8
OEMLaunchImage 80000000
Jump to Physical Address 10300000
Click to expand...
Click to collapse
EDIT again:
another reboot i didn't get someting after
UserStorageSIPreload ++
so i succeed flash "official" roms while in bootloader mode.
but still stuck in booloader and i need to do a "boot" via mtty to get in windows mobile.
but even in windows mobile i can't get active sync recognise my kaiser.
seems windows didn't install proper driver.
so i'm still stuck with no active sync and bootloader after a reset.
should i flash original roms and get it to warranty ? a big bad luck that usb port problem and nand problem in the same time, could it be related ?
but i think a portable stuck in boot loader will never get throught warranty ...
but i will have problem to remove hardspl since i can't get activesync "be green". (I tried to do the method to remove and reinstall hard spl, but i can't since active sync is required)
Same issue on my Tilt
I have been running Dutty's DualTouch v3 Final (WM6) for the past few months happy as a clam. Then in the last few days I've pulled my phone out of my pocket to see a tricolor screen twice (various soft reset attempts, plugging it into my computer, etc. didn't work to enable reboot - it just rebooted while plugged int the computer and I soft reset. I hadn't done any flashing since the dutty ROM months ago... not sure what would cause a bootloader problem now...
Since I've been thinking of flashing to a WM6.1 update anyway, yesterday when it came back up, I pulled down one of the Dutty ROMs for 6.1 and flashed the device.
[I don't know exactly which ROM as I did it at a friends during a party; it did require a Radio update and a ROM update based on the instructions I recall (fyi: margaritas and flashing = fun, but not good.)]
All seemed well. worked great, setp connection to at&t, syn'd device. nice ROM.
Woke up this morning and tricolor again. Can't seem to get it to reboot or play nice yet (soft resets, two soft keys + stylus, plugged into pc or not... nada).
After reading GSLEON3's posting in this thread I decided it would be safe to do a few steps in MTTY. http://forum.xda-developers.com/showthread.php?t=371154)
My tricolor shows:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Serial or USB (depending on connection)
------------after MTTY session using (set 16 0, info 8, boot.)-------------
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 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 1117 (0x45D) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x8A00
Partition[3], type=0x4, start=0x9780, total=0x11B40
CE Total Length(with sector info) = 0x4C0BC00
CE CheckSum Length(without sector info) = 0x4BC0000
Cmd>boot
InitDisplay: Display_Chip=1
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 HC card
SD Init OK
SDFATChkConf: RhOpenFile() failed KAISCONF.txt
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
-----------------------------------------------------
I got it to reboot but subsequent soft resets put me back in tricolor mode.
Any help would be greatly appreciated...Thanks
Ping me on MSN/Live messenger. There are a few things to try, but some aren't for general circulation because the effects can vary depending on device/rom/radio etc. ([email protected])
Working for days - suddenly tri-color glory again
ran MTTY 1.16, connected.
---------------------log of MTTY #1---------------
Cmd>set 16 0
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 1117 (0x45D) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x8A00
Partition[3], type=0x4, start=0x9780, total=0x11B40
CE Total Length(with sector info) = 0x4C0BC00
CE CheckSum Length(without sector info) = 0x4BC0000
Cmd>boot
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 HC card
SD Init OK
SDFATChkConf: RhOpenFile() failed KAISCONF.txt
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage crc of Mini-Kernel:0x9E8EFDF3
OEMLaunchImage 80000000
Jump to Physical Address 10300000
---------End log #1---------------
1) on boot command from MTTY, changed from white screen to tri-color to white screen (painting from center to outside horizontally, not static white)
stuck in tri-color still.
pulled battery
connect viw MTTY #2
---------------log of #2 connection------------------
Cmd>set 16 0
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 1117 (0x45D) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0x8A00
Partition[3], type=0x4, start=0x9780, total=0x11B40
CE Total Length(with sector info) = 0x4C0BC00
CE CheckSum Length(without sector info) = 0x4BC0000
Cmd>boot
InitDisplay: Display_Chip=1
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 HC card
SD Init OK
SDFATChkConf: RhOpenFile() failed KAISCONF.txt
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
-------------------end log #2--------------------
booted to at&t logo and now I'm up and running.
NO FAITH it will continue to work however.
Any ideas? thanks.
Hi All
my name is Alex
i've a problem with my Niki, and a guy in the NIKI forum, sayd me that there are the "CyZeeK's Procedure" that probably can help me for my problem.....
Explain:
my NIKI hang in a blank screen....when you power on, there a re the "vibro", and then BLANK SCREEN.......STOP.....
Ok...i've try MTTY...nothing....this is the LOG:
-------------------------------------------------------------
Cmd>task 32
No card inserted
Level = FF
Cmd>task 28
Format start
Fill RSVD information for block 288 to 309
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>task 2A
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=288, total block of CE=1760
ERASE block 379 FAIL !!!
ERASE block 1315 FAIL !!!
Write 0xFF start page=0x4800, total page=0x1B800
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
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 379 (0x17B) is bad block
BLOCK 1315 (0x523) is bad block
OS NOT FOUND !!!
Cmd>task 8
-----------------------------------------------------
After i start to read the procedure for the ELF......
When i start SNoopyPro in the "usb toggle" mask, i can't find "POCKETPC USB SYNC".....
ok....after some tests, i receive the LOG mask......
save the log.
Use the mtty command decribed on the guide (password, ruurun 0, getdevinfo and ResetDevice....
Put the snoopy log in tinyhex,,,but i can't find the Type of NIKI and the CID
And now??
Where is the misttake???
Someone can help me?
Sorry if i've posted a NIKI problem in the ELF forum, but is very important for me....
Many many thanks
P.S. If someone is italian, can reply me in Italian obviously
^_^
have you the solution for your problem?
i have the same problem!! :-( in my diamond...
qeialto said:
Checking block information
BLOCK 379 (0x17B) is bad block
BLOCK 1315 (0x523) is bad block
OS NOT FOUND !!!
^_^
Click to expand...
Click to collapse
Hi
That's the answer.... your HW is damaged, hence the OS can't run your phone.
Dirk
Hi,
My phone got stuck in bootloader yesterday. It happened when ActiveSync on my Windows XP computer failed to connect to the phone. I restarted the phone, and there I am, can't get past bootloader (tri-color). I have read and tried a lot of tips from older threads but with no luck.
On the bootloader window it says:
KAIS130
SPL-3.29.0000
CPLD-9
If I try to flash in the original rom from HTC RUU_Kaiser_HTC_SVE_3.29.413.0_radio_sign_25.83.40.02_1.65.17.56_Ship.exe (I have never had anyting else in the phone) the instructions says that I must connect to the phone with ActiveSync, that is not possible because I cant get in. Despite the ActiveSync-problem I continue, by klicking next. The flash program can't find any rom on the phone and I start the flashing.
The flashing went through without any errors and my phone restarts, but doesen't come past the bootloader.
I tried 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.
*************
... and get this result:
*********************
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>task 28
Format start
Storage start sector=0xB540, total sector=0xFD80
Storage start block=746, total block=1014
Total Bad Block in CE: 1
Erase physical block from 1037 to 2032
formatstorage Bad block found: 1040
si backup: Erase physical block from 2032 to 2048
Format end
Cmd>task 0
Cmd>
************
The phone does not restart and I do it manually by removing the battery, but there I am again in the bootloader window.
Any ideas what to do ... buy an Iphone?
Now when I look more closely an error message is shown, but it it appears and disappears very quickly in the boot. However if I restart the phone what happens is:
1. The bootloader window appers.
2. It is almost that you manage to see, but a grey window with text "Loading... No Image File!" binks.
3. Back in bootloader window.
So it seems that one of my problems is missing Image File. I tried to format (Fat32) a 2 GB SD and put Dutty's RUU_signed.nbh in the root. But I get same error message.
More info from my device:
Cmd>info 2
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
SD Init OK
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
SD Init OK
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
SD Init OK
HTCSHTC__G09n•xHTCE
*******************************
Cmd>task 32
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
SD Init OK
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
SD Init OK
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
SD Init OK
Level = FF
*********************************************
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 9 (0x9) is reversed block
BLOCK 688 (0x2B0) is bad block
BLOCK 752 (0x2F0) 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=0xA7C0
Partition[3], type=0x4, start=0xB540, total=0xFD80
CE Total Length(with sector info) = 0x5AFAA00
CE CheckSum Length(without sector info) = 0x5AA0000
Cmd>