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.
Has enyone found a solution yet? It seems like the problem can be fixed by flashing again the wlan eeprom. Solution found for other phones like hermes but not for touch cruise...
just hard reset your device...
hard rest does nothing. I reflashed the phone again with 6.1 rom but still nothing
info 8 show bad block. maybe has something to do with the wlan?
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 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 1252 (0x4E4) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x780
Partition[2], type=0x25, start=0xDC0, total=0xCA80
Partition[3], type=0x4, start=0xD840, total=0xDA80
CE Total Length(with sector info) = 0x6C8C200
CE CheckSum Length(without sector info) = 0x6C20000
task 37 ff
something is corrupt... any help
IOCTL_FMD_NAND_READ_WLAN_DATA
01/25/2010 20:41:18 Write WLAN Data
01/25/2010 20:41:18 ++HTC_OEM_ReadNand
01/25/2010 20:41:18 --HTC_OEM_ReadNand
[W00:00:04:282]WLANMSG: VirtualAlloc reservation @00150000
[W00:00:04:284]WLANMSG: VirtualCopy returned: 1
[W00:00:04:285]WLANMSG: EEPROM signature=0xee1251, length=661
[W00:00:04:286]WLANMSG: EEPROM ver=6.3.2
DEXDEX_CMD_COMP
_CMD_STATUS_COMPLETE
DEXCORE:loop=141
01/25/2010 20:41:18 Turn on PMIC VREG[0x100000].
dwStart4KAddr=0xb2e00000, dwEnd4KAddr=0xb2e01000, dwReturnSize=0x1000
dwStart4KAddr=0xb2e00000, dwEnd4KAddr=0xb2e01000, dwReturnSize=0x1000
dwStart4KAddr=0xb1400000, dwEnd4KAddr=0xb1401000, dwReturnSize=0x1000
[W00:00:04:586]ERROR: CMD5 failed...(errcode=0x2BAD0002)
[W00:00:04:701]ERROR: CMD5 failed...(errcode=0x2BAD0002)
[W00:00:04:816]ERROR: CMD5 failed...(errcode=0x2BAD0002)
[W00:00:04:931]ERROR: CMD5 failed...(errcode=0x2BAD0002)
[W00:00:04:931]ERROR: Out...No response from chip!!
[W00:00:04:932]WLANMSG: Turn Off WLAN power...
DEX_DEX_CMD_COMP
CMD_STATUS_COMPLETE
The weird stuff!!!
Installing Adroid the wifi works!!!
This is from a polar200 with working wifi
IOCTL_FMD_NAND_READ_WLAN_DATA
01/25/2010 20:34:59 Write WLAN Data
01/25/2010 20:34:59 ++HTC_OEM_ReadNand
01/25/2010 20:34:59 --HTC_OEM_ReadNand
[W00:00:06:449]WLANMSG: VirtualAlloc reservation @001c0000
[W00:00:06:453]WLANMSG: VirtualCopy returned: 1
[W00:00:06:453]WLANMSG: EEPROM signature=0xee1251, length=661
[W00:00:06:454]WLANMSG: EEPROM ver=6.3.2
DEX_DEX_CMD_COMP
CMD_STATUS_COMPLETE
DEXCORE:loop=159
01/25/2010 20:34:59 Turn on PMIC VREG[0x100000].
dwStart4KAddr=0xb2e00000, dwEnd4KAddr=0xb2e01000, dwReturnSize=0x1000
dwStart4KAddr=0xb2e00000, dwEnd4KAddr=0xb2e01000, dwReturnSize=0x1000
dwStart4KAddr=0xb1400000, dwEnd4KAddr=0xb1401000, dwReturnSize=0x1000
[W00:00:06:684]WLANMSG: entryMiniportInitialize+ 4.03
[W00:00:06:696]ERROR: Out...Could not open temp firmware image file(Err=0xC001001B)
[W00:00:06:702]WLANMSG: Wlan Monitor thread create...
[W00:00:06:775]WLANMSG: EEPROM CountryID=0x30
[W00:00:06:950]WLANMSG: map CountryID=0x30 to channel table
[W00:00:07:216]WLANMSG: TnetwDrv_Init+
[W00:00:07:219]WLANMSG: TNETWIF_ConfigCb: stage 0
[W00:00:07:222]WLANMSG: whal_hwAccess_Config
[W00:00:07:223]WLANMSG: whal_hwAccess_Config status=0x0
[W00:00:07:224]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:07:231]WLANMSG: whal_FwCtrl_EepromlessStartBurstSm+
[W00:00:07:232]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:07:241]WLANMSG: whal_FwCtrl_LoadFwImageSm+
[W00:00:07:241]WLANMSG: FW image length=0x2d424
[W00:00:07:242]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:07:243]WLANMSG: Image addr=0x1d0030, Len=0x2d42c
[W00:00:07:258]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:07:273]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:07:274]WLANMSG: Finished downloading firmware.
[W00:00:07:274]WLANMSG: whal_FwCtrl_FinalizeDownloadSm+
[W00:00:07:275]WLANMSG: ACX_REG_ECPU_CONTROL IS 1
[W00:00:07:275]WLANMSG: Firmware running
[W00:00:07:276]WLANMSG: CHIP ID IS 7020101
[W00:00:07:287]WLANMSG: read intr data =0x4000
[W00:00:07:287]WLANMSG: TNETWIF_WriteRegOpt status=64
[W00:00:07:288]WLANMSG: uFinStage=6, uFinLoop=0xa2
[W00:00:07:288]ERROR: Firmware init complete[W00:00:07:289]WLANMSG: CmdMBox_ConfigHw status=0x40
[W00:00:07:289]WLANMSG: uFinStage=7
[W00:00:07:290]WLANMSG: eventMbox_ConfigHw status=0x40
[W00:00:07:290]WLANMSG: uFinStage=8
[W00:00:07:291]WLANMSG: +whal_hwAccess_SetPartitionsAsync:1
[W00:00:07:292]WLANMSG: write HI_CFG data=0xbc, status=0x40
[W00:00:07:295]WLANMSG: whal_hwCtrl_FinalizeDownload+
[W00:00:07:296]WLANMSG: whal_hwCtrl_FinalizeDownloadCb1
[W00:00:07:297]WLANMSG: whal_hwCtrl_FinalizeDownloadCb2
[W00:00:07:305]WLANMSG: whal_hwCtrl_ConfigHw
[W00:00:07:336]WLANMSG: Retrieve FW info: preamble=0, fwVer=Rev 6.0.4.40, radioType=0x3, EepromVer=6.3.28.0
[W00:00:07:337]WLANMSG: FW Version = Rev 6.0.4.40 Station Id=00-18-41-5B-63-BD
[W00:00:07:395]WLANMSG: whal_hwCtrl_FinalizeDownload-
[W00:00:07:396]ERROR: [whal_FwCtrl_LoadFwImageSm] Firmware successfully downloaded!!
[W00:00:07:396]WLANMSG: configMgr_init done!
Time[20:35:00]
[W00:00:07:407]WLANMSG: Read Key value = 1
[W00:00:07:426]LEAP: +++ Current timer setting in Zero Config +++
[W00:00:07:429]LEAP: !!! Failed WZCQueryContext. Err = [0x2] !!!
[W00:00:07:430]LEAP: !!! Failed WZCSetContext. Err = [0x2] !!!
[W00:00:07:437]WLANMSG: [Wifi-TCXO] Turn off wifi clock, reason: Finish MiniportInit[SER_MDD][SER_DllEntry]serial port process attach
SMD DLL attach, smd_sio_initialize 0, 1 process attach
01/25/2010 20:35:00 [K :: KERNEL] OEMInterruptEnable: SYSINTR_FIRMWARE+55
[INT-En]SYSINTR_55
Q: q_lock_init Mutex
Q: q_ptr:0x1d50790 mutex:0xc6ad8f4e (0x1d5079c)
Q: q_lock_init Mutex
Q: q_ptr:0x1d4e590 mutex:0xc6a95756 (0x1d4e59c)
smd task started 0x224b008, sighandler 0x0 procCount 0
ISR: Reset button triggerred
[W00:00:08:364]ERROR: whal_hwAccess_ReadReg: Error in reg read RegAddr=0x000004A4 status=0x2BAD0001
[W00:00:08:365]WLANMSG: whal_hwAccess_ReadRegAsync error
[W00:00:08:367]ERROR: whal_hwAccess_ReadMem: Bus error...
[W00:00:08:368]ERROR: whal_hwAccess_WriteReg: Bus error...
[W00:00:08:369]WLANMSG: whal_hwAccess_WriteRegAsync addr=0x494, data=0xfffffdc4 error
[W00:00:08:370]ERROR: whal_hwAccess_WriteReg: Bus error...
[W00:00:08:371]WLANMSG: TNETWIF_WriteRegSync fail
[W00:00:08:372]ERROR: whal_hwAccess_WriteReg: Bus error...
[W00:00:08:373]WLANMSG: whal_hwAccess_WriteRegAsync addr=0x494, data=0xffffffff error
[W00:00:08:374]ERROR: whal_hwAccess_ReadReg: Bus error...
[W00:00:08:375]WLANMSG: whal_hwAccess_ReadRegAsync error
[W00:00:08:375]ERROR: whal_hwAccess_ReadMem: Bus error...
[W00:00:08:376]ERROR: whal_hwAccess_WriteReg: Bus error...
[W00:00:08:377]WLANMSG: whal_hwAccess_WriteRegAsync addr=0x494, data=0xfffffdc4 error
[W00:00:08:378]ERROR: whal_hwAccess_WriteReg: Bus error...
[W00:00:08:379]WLANMSG: TNETWIF_WriteRegSync fail
WLAN:RC(8380)
[W00:00:08:380]WLANMSG: event 3: recovery process is about to run...
[W00:00:08:382]ERROR: WriteReg Error (addr=0x00000494 data=0xffffffff, status=0x2BAD0001)
[W00:00:08:383]WLANMSG: TNETWIF_WriteRegSync fail
WLAN:rc(8383)
[W00:00:08:389]WLANMSG: healthMonitor_proccessFailureEvent+++
[W00:00:08:390]WLANMSG: Perform recovery, event = 3
[W00:00:08:391]WLANMSG: REC_MGR_STATE_IDLE
01/25/2010 20:35:00 [K :: KERNEL] OEMInterruptDisable: SYSINTR_FIRMWARE+11
SYSINTR_WLAN Disable [W00:00:08:392]WLANMSG: REC_CTRL_STATE_IDLE
[W00:00:08:392]WLANMSG: REC_CTRL_STATE_WAIT_END_CURR_TXN
SDCC_DisableController, SdcNsRegs = 0xfff60079
[W00:00:08:431]WLANMSG: whal_hwAccess_SetPartitions:0
[W00:00:08:433]WLANMSG: whal_FwCtrl_EepromlessStartBurstSm+
[W00:00:08:434]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:08:447]WLANMSG: whal_FwCtrl_LoadFwImageSm+
[W00:00:08:447]WLANMSG: FW image length=0x2d424
[W00:00:08:448]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:08:449]WLANMSG: Image addr=0x1d0030, Len=0x2d42c
[W00:00:08:471]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:08:494]WLANMSG: +whal_hwAccess_SetPartitionsAsync:0
[W00:00:08:496]WLANMSG: Finished downloading firmware.
[W00:00:08:497]WLANMSG: whal_FwCtrl_FinalizeDownloadSm+
[W00:00:08:497]WLANMSG: ACX_REG_ECPU_CONTROL IS 101
[W00:00:08:498]WLANMSG: Firmware running
[W00:00:08:498]WLANMSG: CHIP ID IS 7020101
[W00:00:08:509]WLANMSG: read intr data =0x4000
[W00:00:08:510]WLANMSG: TNETWIF_WriteRegOpt status=64
[W00:00:08:510]WLANMSG: uFinStage=6, uFinLoop=0x67
[W00:00:08:511]ERROR: Firmware init complete[W00:00:08:511]WLANMSG: CmdMBox_ConfigHw status=0x40
[W00:00:08:512]WLANMSG: uFinStage=7
[W00:00:08:512]WLANMSG: eventMbox_ConfigHw status=0x40
[W00:00:08:513]WLANMSG: uFinStage=8
[W00:00:08:513]WLANMSG: +whal_hwAccess_SetPartitionsAsync:1
[W00:00:08:515]WLANMSG: write HI_CFG data=0xbc, status=0x40
[W00:00:08:515]WLANMSG: whal_hwCtrl_FinalizeDownload+
[W00:00:08:516]WLANMSG: whal_hwCtrl_FinalizeDownloadCb1
[W00:00:08:517]WLANMSG: whal_hwCtrl_FinalizeDownloadCb2
[W00:00:08:518]WLANMSG: whal_hwCtrl_ConfigHw
[W00:00:08:522]WLANMSG: whal_hwCtrl_ConfigHw:whal_hwCtrl_ConfigHwCb1
[W00:00:08:551]WLANMSG: REC_CTRL_STATE_INIT_CMPLT
[W00:00:08:555]WLANMSG: REC_CTRL_STATE_END_RECONFIG
[W00:00:08:555]WLANMSG: REC_MGR_STATE_WAIT_TWD_RESTART
[W00:00:08:556]WLANMSG: CHIP ID = 7020101
[W00:00:08:558]WLANMSG: .....recoveryMgr: End Of Recovery
[W00:00:08:558]WLANMSG: whal_hwCtrl_FinalizeDownload-
[W00:00:08:559]ERROR: [whal_FwCtrl_LoadFwImageSm] Firmware successfully downloaded!!
smem_init_internal done
Have you tried android as we read the firmware from the file Fw1251r1c.bin not the nand so might tell you if it is the nand or hardware "faulty wifi chip"?.
Yes it works perfectly with Android!!
So is the nand...
My polaris is now officially dead!!
i run task 2a in mtty and format everything on Nand.
Disconnected the usb cable before reflashing bootloader and now my polaris does't boot at all!!
I've got the same problem. wifi doesn't start.. is there any service mode in polaris, or service program to check wifi module?
ppj1 The easiest and safest way to test wifi is with android "theres plenty of threads how to load it" if it works on android it's probably your nand.
Be careful with mtty it can brick your phone
The other way is to use mtty and use the command task 37
mamrai1 was your phone security unlocked??
If it is maybe you can connect to the oemsbl and flash a spl?
With your phone plugged into your computer press the power button with your finger on the green button.If your phone goes into oemsbl you will need The QC diag drivers "do a search for QC diag drivers or MotoQ drivers"
too late ...
i run task 2a and bricked my phone. it was security locked since i can't run mw/mb to flash a new spl. i 'll need a custom frankenkaiser ...
So I installed android and.... wifi works!!
Now what is that mtty?
ok so I did MTTY it found bads, flashed it, I did the new radio rom, system.. anstill cant run wifi........
ok my phone goes on oemspl. how i flash an spl now?
----problem WIFI still wont start---- General View of my problem
So till now I've already done:
1. ROM rom original to Megan
2. Radio ROM (about 3 different radio roms)
3. Installed ANDROID >> WIFI WORKS SUPERB
4. Flashed in MTTY (2 ways) still nothing..
-here is raport wrom MTTY
Cmd>set 14 0
HTCST ÚČŇHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 288 to 309
Storage start sector=0xD840, total sector=0xDA80
Storage start block=886, total block=874
Total Bad Block in CE: 0
Erase physical block from 1176 to 2048
formatstorage Bad block found: 1688
formatstorage Bad block found: 1756
formatstorage Bad block found: 1757
formatstorage Bad block found: 1758
formatstorage Bad block found: 1759
formatstorage Bad block found: 1767
formatstorage Bad block found: 1769
formatstorage Bad block found: 1770
formatstorage Bad block found: 1771
formatstorage Bad block found: 1772
Format end
Cmd>task 0
Cmd>boot
InitDisplay: Display_Chip=1
CpldSetSystemLED2 [1],gdwLED2Status=0.
No this System Led2 Behavior [1]
Fill RSVD information for block 288 to 309
Storage start sector=0xD840, total sector=0xDA80
Storage start block=886, total block=874
Total Bad Block in CE: 0
Erase physical block from 1176 to 2032
formatstorage Bad block found: 1688
formatstorage Bad block found: 1756
formatstorage Bad block found: 1757
formatstorage Bad block found: 1758
formatstorage Bad block found: 1759
formatstorage Bad block found: 1767
formatstorage Bad block found: 1769
formatstorage Bad block found: 1770
formatstorage Bad block found: 1771
formatstorage Bad block found: 1772
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
5. Back to original ROM 6.1
and I STILL can't make running this WIFI
please help!
Can anyone dump the eeprom area of a working wifi polaris at address 50100000?