LGSilva
29th April 2008, 12:25 AM
=====
Update
=====
I'm updating this thread so I don't spam the board.
After trying all kinds of software solutions, resets and all I gave up. It's a hardware problem (as far I can tell) and there is no way to fix it unless you replace one board on the phone.
This is how I found the problem:
I got another shadow from eBay with a broken screen but working wifi.
I swapped the main board and guess what? No wifi. The only thing I could think is that the other board on the phone, the one connected to the screen and circle pad thing was the problem and probably were the wifi part of the phone resides on.
Once I replaced that part the wifi worked with both boards.
If anyone is a hardware expert or just for curiosity want to see some pictures from both working and non-working boards, PM me.
=========
Original Post
=========
Hello guys, I got a T-mobile Shadow and I can't get the wifi to work. On the wireless info says "driver not loaded".
I tried to re-flash it with the original firmware several times (ok... 4 times).
I tried to use the beta version of wm6.1.
I tried to reset and hard-reset the phone over and over.
I tried to put the "wifiinit.lnk" on my startup folder and even run wifiinit.exe.
I tried to mtty it to check for bad nand block but the commands will not work (info 8). This password will work -> BsaD5SeoA
I can't return it to T-mobile because it was a phone with a broken screen that I bought from eBay.
So this is my last resort before I give up on wifi:
Does anyone know anything I could do to try to fix it?
Thanks :)
ND4SPD
29th April 2008, 02:42 AM
This is kind of an expensive solution, and should be used as last resort, you could try getting a WiFi MicroSD card. I'm guessing only the WiFi radio is having problems even though it says it's the driver.
LGSilva
29th April 2008, 03:01 AM
Thanks ND4SPD for the reply.
I also think it's something wrong with the radio part and I guess as long t-mobile don't release an update I will stuck without wifi.
Keep the good work with the 6.1 rom! :)
I'm using it right now, so long neo interface!
P.S.: If someone find a solution please post it here.
ND4SPD
29th April 2008, 03:59 AM
I just looked up some stuff and found that there are quite a few people have had the same problem after updating to tmobiles update. The only two suggestions they had were to hard reset or try the update again.
LGSilva
30th April 2008, 04:24 AM
I have one idea: flash my shadow with the original rom. The only problem is how to get the original rom? I know that there is the raw dump. Is there a way to make it flasheable?
edit:
Just did, I was able to flash it to the first firmware using the files @ ftp.
But still the same thing, no wifi.
I'll keep looking for a solution for this.
LGSilva
30th April 2008, 08:52 AM
Could someone post this reg info from a wifi working shadow?
[HKEY_LOCAL_MACHINE\Comm\TNETW12511]
"Wireless"=dword:00000001
"ImagePath"="TNETW1251.dll"
"Group"="NDIS"
"DisplayName"="IEEE 802.11b/g Compatible Wi-Fi Adapter"
[HKEY_LOCAL_MACHINE\Comm\TNETW12511\Parms]
"InstanceNumber"=dword:00000000
"PowerSavePowerLevel"=dword:00000000
"defaultPowerLevel"=dword:00000000
"DSCPClassifier03_DTag"="7"
"DSCPClassifier03_CodePoint"="56"
"DSCPClassifier02_DTag"="5"
"DSCPClassifier02_CodePoint"="40"
"DSCPClassifier01_DTag"="1"
"DSCPClassifier01_CodePoint"="8"
"DSCPClassifier00_DTag"="0"
"DSCPClassifier00_CodePoint"="0"
"NumOfCodePoints"="4"
"IPPortClassifier02_DTag"="6"
"IPPortClassifier02_Port"="5003"
"IPPortClassifier02_IPAddress"="0a 03 89 02"
"IPPortClassifier01_DTag"="4"
"IPPortClassifier01_Port"="5002"
"IPPortClassifier01_IPAddress"="0a 03 89 02"
"IPPortClassifier00_DTag"="1"
"IPPortClassifier00_Port"="5001"
"IPPortClassifier00_IPAddress"="0a 03 89 02"
"NumOfDstIPPortClassifiers"="3"
"Clsfr_Type"="1"
"QOS_wmePsModeVO"="0"
"QOS_wmePsModeVI"="0"
"QOS_wmePsModeBK"="0"
"QOS_wmePsModeBE"="0"
"desiredPsMode"="1"
"RatePolicySGRetriesPerRateOfdmA"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRateOfdm"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRatePbcc"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRateCck"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserRetriesPerRateOfdmA"="0,0,0,1,0,0,1,0,0,1,0,0,0"
"RatePolicyUserRetriesPerRateOfdm"="0,0,0,1,0,0,0,1,0,0,1,1,1"
"RatePolicyUserRetriesPerRatePbcc"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserRetriesPerRateCck"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserLongRetryLimit"=dword:0000000A
"RatePolicyUserShortRetryLimit"=dword:0000000A
"RateAdaptationTimeout"=dword:0000012C
"FBLongInterval"=dword:000000C8
"FBShortInterval"=dword:00000028
"RateStepUpThreshold"=dword:00000002
"RateContThreshold"=dword:0000000A
"Beacon_IE_Table"="00 01 01 01 32 01 2a 01 03 01 06 01 07 01 20 01 25 01 23 01 30 01 28 01 2e 01 85 01 dd 00 52 f2 02 00 01"
"Beacon_IE_Table_Size"=dword:00000035
"Beacon_IE_Num_Of_Elem"=dword:00000015
"Beacon_Filter_Stored"=dword:00000001
"Beacon_Filter_Desired_State"=dword:00000000
"ArpIp_Addr"="c0 a8 00 5e"
"ArpIp_Filter_ena"=dword:00000000
"DtimListenInterval"=dword:00000001
"BeaconListenInterval"=dword:00000001
"HTCActiveSyncReconnectWorkaround"=dword:00000001
"dot11AuthenticationResponseTimeout"=dword:000001F4
"dot11MaxAuthRetry"=dword:00000002
"dot11DesiredChannel"=dword:0000000B
"AutoPowerModeDozeMode"=dword:00000002
"ShortSlotTime"=dword:00000000
"Mode4x"=dword:00000000
"MixedMode"=dword:00000000
"SpectrumManagement"=dword:00000000
"MultiRegulatoryDomain"=dword:00000000
"WME_Enable"=dword:00000001
"HTCWiFiLogoMICWorkaround"=dword:00000000
"TxPower"=dword:00000001
"PowerMgmtHangOverPeriod"=dword:00000005
"RSNPreAuthentication"=dword:00000001
"RecoveryEnable"=dword:00000000
"HTCAutoOffInterval4NoActivity"=dword:00002710
"HTCAutoOffIfNoActivityEnable"=dword:00000001
"MinimumDurationBetweenOidScans"=dword:00000005
"FirstConnScanEnabled"=dword:00000001
"WPAMixedMode"=dword:00000001
"RxBroadcastInPs"=dword:00000001
"HTCOutputWLANdebugLog"=dword:00000000
"BThWlanCoexistParamssgAntennaType"=dword:00000002
"BThWlanCoexistParamsnumberOfBtPackets"=dword:00000002
"BThWlanCoexistParamsnumberOfWlanPackets"=dword:00000004
"BThWlanCoexistParamssenseDisableTimer"=dword:00000320
"BThWlanCoexistRate"="0,0,1,0,0,1,1,1,0,1,1,1,1"
"BThWlanCoexistEnable"=dword:00000001
"dot11RTSThreshold"=dword:00001000
"dot11FragmentationThreshold"=dword:00001000
"dot11ShortPreambleInvoked"=dword:00000001
"HTCPreloadLEAP"=dword:00000000
"HTCGetIPWorkaround"=dword:00000001
"HTCAutoOffTimeout"=dword:0001D4C0
"HTCAutoOffMode"=dword:00000000
"HTCPowerMode"=dword:00000002
"ResetOnResume"=dword:00000000
"SysIntr"=dword:0000002B
"BusType"=dword:00000000
"BusNumber"=dword:00000000
Thank you
jockyw2001
30th April 2008, 11:25 AM
Maybe I can help.
Dump the file bk_02_0005.img as described here (http://forum.xda-developers.com/showpost.php?p=1555583&postcount=16)
LGSilva
30th April 2008, 05:44 PM
Hey jockyw2001, thank you for the help.
Here is the file you asked: http://www.lgsilva.com/bk_02_0005.rar
:)
jockyw2001
30th April 2008, 08:25 PM
It's a hardware problem. The wlan configuration data integrity is fine, TI chip is recognized. Maybe you should open it up and check if the wlan/BT antenna is properly connected.
LGSilva
1st May 2008, 04:09 AM
Thanks jockyw2001 for your help. I'll try to check the phone but the thing is... the BT works fine. I just can't enable the wlan on the comm manager.
LGSilva
16th May 2008, 08:02 AM
See first post for update (bump).
jockyw2001
30th May 2008, 04:50 PM
thx for your update!
Have you noticed a little battery on the board u replaced? It's right under a piece of tape. Please measure the voltage. I suspect it ran out of power on the board u replaced.
talwell
31st May 2008, 05:44 AM
Jocky and I spent the entire day trying to resolve this wifi problem.
Unfortunately we have completely disproven your method - it is impossible for your mainboard to work with the non-original daughter board / flexcable.
This board contains your wifi components - they communicate with the main board. The main board firmware is married to the mac address of the wifi controller on your daughterboard. Unless you updated your firmware, your board would never work unless using the board that was originally delivered with the mainboard.
We spent alot of time testing this theory as you threw us off with the mis-information you provided. In the end, we needed to update this thread as it is invalid.
We are now working on tools to read the config of the wifi chip and update the firmware to re-create the married set if you ever need to change this board or your firmware gets corrupted.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.