Database Users

Wi-Fi problem (WM6 / WM6.1 rom )

hi ı am not spaek eng.
wifi problem wm6 and wm6.1 ı loaded but wi-fi problem.
entered once to the cırcuıt.
WM5 there isnt the problem.
wm6 only is becoming problem
What can ı do ?
ı am sorry speak eng. bad
T-Mobil MDA WM5
G3 unlock
ipl spl = 1.01
rom = 1.1.93
rom date =9/16/05
radio =01.01.10
protocol = 4.0.13.16
extROM = 1.1.9.104

Many of the wm6 and wm6.1 do not auto connect to your network. You need to go to settings - connections - wifi, and manually connect to your network.
Give it a try

bill_in_mtl said:
Many of the wm6 and wm6.1 do not auto connect to your network. You need to go to settings - connections - wifi, and manually connect to your network.
Give it a try
Click to expand...
Click to collapse
bill_in_mtl thanks
manually isnt being useful in this method to the work.
but once find but be fastened
only WM5 isnt wi-fi problem.Why didnt ı understand

Wizard Service Tool v4.2.2
08/05/08 00:31:47
CPU Manuf. FAILED
MODEL: Wizard
IMEI: 35792700*******
=> Bootloaders:
IPL: 1.01 (G3 device)
Built on Sep 19 2005 at 18:00:32
Copyright (c) 2003 High Tech Computer Corporation
=> Firmware:
OS: 5.1.xxx (Build 14402.1.1.0)
ROM: 5.1
Registry AKU: .1.1.0
Radio values FAILED
=>Extended_ROM:
Version: 1.1.9.104
Name: Extended_ROM
Status: hidden
=> DOC chip unique ID:
0000000057340204181d04b709090516
Key Index: 24
----------------------------
Reading CID block...
Calculating CID block sum...
CID checksum: 8A1C7412
Decrypted stored sum: 3DC9DB45AAE46633
Decrypted calcd sum: 3DC9DB45AAE46633
Key index : 24 - Block index: 170
CIDkey: MODULESN
CID IMEI: 35638100005****
CID: 11111111 (SuperCID)
Phone is already CID unlocked!
-------------------------------
Reading CID block...
Calculating CID block sum...
CID checksum: 8A1C7412
Decrypted stored sum: 3DC9DB45AAE46633
Decrypted calcd sum: 3DC9DB45AAE46633
Key index : 24 - Block index: 170
CIDkey: MODULESN
CID IMEI: 3563810000*****
SIM lock status: 0000000000000000
Your phone is already SIM unlocked!
What is the problem according to you ??
All Done.

ferfecir said:
Wizard Service Tool v4.2.2
08/05/08 00:31:47
CPU Manuf. FAILED
MODEL: Wizard
IMEI: 35792700*******
=> Bootloaders:
IPL: 1.01 (G3 device)
Built on Sep 19 2005 at 18:00:32
Copyright (c) 2003 High Tech Computer Corporation
=> Firmware:
OS: 5.1.xxx (Build 14402.1.1.0)
ROM: 5.1
Registry AKU: .1.1.0
Radio values FAILED
=>Extended_ROM:
Version: 1.1.9.104
Name: Extended_ROM
Status: hidden
=> DOC chip unique ID:
0000000057340204181d04b709090516
Key Index: 24
----------------------------
Reading CID block...
Calculating CID block sum...
CID checksum: 8A1C7412
Decrypted stored sum: 3DC9DB45AAE46633
Decrypted calcd sum: 3DC9DB45AAE46633
Key index : 24 - Block index: 170
CIDkey: MODULESN
CID IMEI: 35638100005****
CID: 11111111 (SuperCID)
Phone is already CID unlocked!
-------------------------------
Reading CID block...
Calculating CID block sum...
CID checksum: 8A1C7412
Decrypted stored sum: 3DC9DB45AAE46633
Decrypted calcd sum: 3DC9DB45AAE46633
Key index : 24 - Block index: 170
CIDkey: MODULESN
CID IMEI: 3563810000*****
SIM lock status: 0000000000000000
Your phone is already SIM unlocked!
What is the problem according to you ??
All Done.
Click to expand...
Click to collapse
wi-fi problem

Your ROM is not WM6 according to the build number and AKU as revealed by the WST. You must make sure you have upgraded to the latest factory T-Mobile MDA ROM and then upgrade your device to WM6.

jwzg said:
Your ROM is not WM6 according to the build number and AKU as revealed by the WST. You must make sure you have upgraded to the latest factory T-Mobile MDA ROM and then upgrade your device to WM6.
Click to expand...
Click to collapse
RUU_Prodigy_3821_382119_026911_TMO_UK_WWE_Ship (3.08)
and
XM6r5Lite wm6
test negative

The IPL, SPL and radio ROMs are *way* out of date.
You'll want to get up to a 2.x IPL/SPL so you can use a 2.x radio ROM.
Get this file from the T-Mobile US web site:
MDA_software_update_226102_22610105_022511.exe
Update your phone with that file.
This will give you WM5 AKU 2.3 with IPL/SPL: 2.26 and radio: 2.25.11.
Once you have that installed, you can upgrade to any of the WM6 ROMs floating around that are designed for the device such as the TNT ROM.
Since the cooked WM6 ROMs are OS only, they don't have an IPL/SPL to flash and they don't always have a radio ROM either. This is for safety reasons.

Different HERM # on my device

I have browse the wiki, and learned that "info 7" command in mtty will show me the bootloader info, so I try it on my device.
In mtty , it says
---------------------------
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: HERM100, Bootloader Version : 2.10.Olipro
Built at: Apr 22 2007 13:32:26
Copyright (c) 1998-2007 Modified By Olipro - Hard-SPL
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x5
--------------------------
I notice the device name is HERM100, but I always thought of my device as a HERM200 before, cauz 1) the bootloader( tri-color ) screen says HERM200 2) A white paper near the SIM card slot says HERM200 too.
But I has seen some post saying that my device (Cingular 8525 ) should be a "HERM100 and CID is ......" ,because of the bootloader screen and the paper said the same, I just ignore the post, thinking may be my device is just some new born that has not been addressed in that post. Now I wonder...................
What this number actually mean?

The differences between Herm100 and 200 are just cosmetic... have a look at my signature... my phone is a mixture of the two.. so guess mines more of a herm150 lol

Am I missing a step?

I'm kinda of a newbie to the whole flashing the HTC 8125...I've searched and searched and downloaded a couple of ROMS that I would find pretty cool on my phone but...whats next? I got a Cingular 8125...I did the hardSPL..and heres what I got...
Wizard Service Tool v4.2.2
18/02/09 02:08:43
CPU: Texas Instruments - OMAP850
MODEL: Wizard
IMEI: ----------
=> Bootloaders:
IPL: 2.21.0001 (G4 device)
SPL: 2.21.Olip (G4 device w/ HardSPL)
Built on Aug 26 2007 at 19:41:34
Copyright (c) 2007 Olipro & HTC - Hard-SPL
=> Firmware:
OS: 5.1.xxx (Build 14928.2.2.0)
ROM: 2.25
Registry AKU: .2.2.0
Radio: 02.25.11
Protocol: 4.1.13.12
=>Extended_ROM:
Version: 2.25.11.102
Name: Extended_ROM
Status: hidden
=> Drives and partitions:
|--Handle--|---Size---|
ee9df2f2 - 5.00M (0x4fec00)
6ea9d13a - 48.23M (0x303c000)
0fb25f92 - 50.95M (0x32f4000)
0fb25f3e - 2.94M (0x2f0000)
2fb25fb6 - 3.06M (0x30fc00)
=> DOC chip unique ID:
00000000306901051024050918060635
Key Index: 84
All Done.
I still got WB5 on my phone..and I tried TNT.1933 touchflo..by hooking up my phone with a usb and activesync..but when I ran the RUU it said file error..do I have to upgrade to WB 6.1 first and if so...where do I get it (ive searched wiki and everything I could search here) or am I missing a step? Any help would be great, thanks!

need help?
hi there.... it seems you have unlocjed the device...
now, when you try to upload a new ROM. first of all, the device must be "connected to PC" using activesync (v 4.5)
then u have to run RUU.... in fact most roms you download have the RUU inside... so send me message if need help... send message...
GOOD LUCK

Nothings wrong there and you don't have to upgrade first to any rom,All the wm6 or wm6.1 roms can be flashed directly,as its already HardSPL,you can flash any wm6 or wm6.1 roms as much as you like,but just don't flash any official stock rom,it contains IPL/SPL,it'll Brick the phone.
If its a 'File Open' or 'File Read' error,re download the rom package again and run it,it may be the rom you downloaded is corrupt or missing some files.

Problem with my Elf or with my SIM ?

Hello,
Sorry for my english
Big problem with my Elf
Without SIM, it starts without problem.
With SIM:
- power off after smart mobility and obliged to remove the battery
OR
- asks me PUK code (and when I enter the PUK told me he is not good then it's one I on the website of Orange France.. and my other phone not asks me the PUK code, just SIM code !!! (LG KS360))
And often, after reboot, the date and time back to 00:00 01/01/00 !!!
I don't understand
I even reloaded original ROM !!! (IPL, SPL, RADIO, OS, extROM)
Touch version : Elf
Device ID : ELF010000
CID : HTC__203
IPL : 2.20.0002
SPL : 2.20.0000
ROM Version : 2.20.406.1
ExtROM Version : 2.20.406.101
Operator Version: None
AKU Version : 0.4.2
Page Pool (MB) : 8
RAM Size (MB) : 64
ROM Size (MB) : 128
Model No. : ELF0300
Part Number : xxxxxxx
SIM Unlock Code : xxxxxxxx
Problem with my phone or with my SIM ? If it's my phone, do you have ideas ?
PS : battery full
Thanks

Hi
It's very easy to check if the prob is with the sim, try with another sim
If the elf was lost/stolen it might be blocked too.

No problem after 10 reboots with the SIM of my girlfriend. It seems that it comes from my SIM. Sometimes turns off after smart mobility, sometimes it asks me the PIN and it works properly, sometimes it asks me the PUK code after entering the correct code SIM. On my LG KS360, no problem, it's strange no ?
Especially the fact that sometimes extinguished after Elf Smart Mobility is strange...
I thought it came from multiple flash ... (IPL / SPL / OS / RADIO)
tito12 said:
If the elf was lost/stolen it might be blocked too.
Click to expand...
Click to collapse
No, my Elf was not stolen, I bought in store in 2007.
By cons he remained some time with "SIM off" after termination of my subscription (my old number). After he spent more than a year in a drawer without starting...

How did you solved the problem???????
Read my story!!
http://forum.xda-developers.com/showthread.php?t=635263

USB tethering causing BSODs on Windows 8?

Hello everyone.
First I would like to say I wouldn't be opening this thread if I hadn't done extensive research on this issue (aka Googling).
Anyway, recently I upgraded my computer and went from Windows 7 to Windows 8. Problems started right after installation, I was getting frequent blue screens of death. I figured it was a driver problem, so I installed all the windows updates and updated hardware drivers. While BSODs have become less frequent now, they are still present. I installed WinDbg to analyze crash dumps and I noticed that almost all of the crashes were caused by a module called "usb8023x.sys", which is a Remote NDIS USB Driver (the driver which allows the phone to act as an internet sharing device).
In case we have some knowledgeable people here, maybe this latest bugcheck analysis could give some hints of what's wrong
Code:
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
Debugging Details:
------------------
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
TAG_NOT_DEFINED_c000000f: FFFFF800A0DBBFB0
LAST_CONTROL_TRANSFER: from fffff800a11ebf4b to fffff800a106c440
STACK_TEXT:
fffff800`a0db5408 fffff800`a11ebf4b : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff800`a0db5410 fffff800`a10b0774 : fffff880`05b18db5 00000000`000f25ce fffff800`a0db5590 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x145a4
fffff800`a0db5490 fffff800`a1780eca : fffff800`a0db5b10 fffff800`a130a180 fffffa80`08111a40 fffffa80`08111ae8 : nt!KeUpdateTime+0x2ec
fffff800`a0db5670 fffff800`a106501e : 00000024`1d684872 fffffa80`096b8010 fffff800`a17aa580 00000000`00000000 : hal!HalpTimerClockInterrupt+0x86
fffff800`a0db56a0 fffff880`0a2e0d87 : fffffa80`096b8010 fffffa80`04dbf018 fffff800`a130a180 fffff800`a0db5b00 : nt!KiInterruptDispatchLBControl+0x1ce
fffff800`a0db5830 fffff800`a10951ea : 00000000`00000002 00000000`00ec6083 fffff800`a0db5939 00000000`00000000 : usb8023x!CancelSendsTimerDpc+0x5b
fffff800`a0db5870 fffff800`a1093655 : 00000000`00000000 fffff800`a1094cff 00000000`00140001 fffff800`a130e040 : nt!KiProcessExpiredTimerList+0x22a
fffff800`a0db59a0 fffff800`a1095668 : fffff800`a130a180 fffff800`a130cf80 00000000`00000003 00000000`0009045e : nt!KiExpireTimerTable+0xa9
fffff800`a0db5a40 fffff800`a1094a06 : fffffa80`00000000 00001f80`00300080 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
fffff800`a0db5af0 fffff800`a10959ba : fffff800`a130a180 fffff800`a130a180 00000000`00183de0 fffff800`a1364880 : nt!KiRetireDpcList+0x1f6
fffff800`a0db5c60 00000000`00000000 : fffff800`a0db6000 fffff800`a0db0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usb8023x!CancelSendsTimerDpc+5b
fffff880`0a2e0d87 7549 jne usb8023x!CancelSendsTimerDpc+0xa6 (fffff880`0a2e0dd2)
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: usb8023x!CancelSendsTimerDpc+5b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usb8023x
IMAGE_NAME: usb8023x.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 51198a2e
BUCKET_ID_FUNC_OFFSET: 5b
FAILURE_BUCKET_ID: 0x133_DPC_usb8023x!CancelSendsTimerDpc
BUCKET_ID: 0x133_DPC_usb8023x!CancelSendsTimerDpc
Followup: MachineOwner
---------
0: kd> lmvm usb8023x
start end module name
fffff880`0a2de000 fffff880`0a2e9000 usb8023x (pdb symbols) c:\cache\usb8023x.pdb\DBA9FFB075764A7EBBBC828D0809D82A1\usb8023x.pdb
Loaded symbol image file: usb8023x.sys
Mapped memory image file: c:\cache\usb8023x.sys\51198A2Eb000\usb8023x.sys
Image path: \SystemRoot\System32\drivers\usb8023x.sys
Image name: usb8023x.sys
Timestamp: Tue Feb 12 02:17:50 2013 (51198A2E)
CheckSum: 00006293
ImageSize: 0000B000
File version: 6.2.9200.16525
Product version: 6.2.9200.16525
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: usb8023.sys
OriginalFilename: usb8023.sys
ProductVersion: 6.2.9200.16525
FileVersion: 6.2.9200.16525 (win8_gdr.130211-1605)
FileDescription: Remote NDIS USB Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
Everything worked flawlessly on Win 7. I'm open to any kind of suggestions, because I don't know what's there left to do.

you should report your bug to windows

Oops... Report your issue to windows buddy
Sent from my GT-I9100 using Tapatalk 4

simms22 said:
you should report your bug to windows
Click to expand...
Click to collapse
Yeah, will probably do.