Database Develop

Help i dont know what brand is my PDA

hi, i wanne know what brand is my pda for update, i checked this with Getdevicedata my result is it:
PH20B
0 B
ENG
G
11111111
0.99.00
0 0
0.99.111
0.91.00
91.00
my device look Blue Angel with Camara.
thank you

The info looks wrong, check the info that you get out of devce device info under settings-> system.

Device Information:
ROM version: 0.99.00 ENG
ROM date: 06/09/04
Radio version: 0.91.00
Protocol version: 1337.27
ExtROM version: 0.99.111 WWE
Hardware:
CPU: Intel (R) PXA263
Speed: 400 MHZ
RAM size: 128 MB
Flash size: 32 MB
Flash chip type: 28F128K3
Data bus: 32 bits
Storage size: 43.26 MB
LCD: 240 x 320 TFT
Color: 65536
Identity:
Model No.: PH20B
Platform: Pocket PC
IMEI: 35303000002xxxx

Not sure, but i think you should remove your IMEI number from this post.

Model No.: PH20B
Platform: Pocket PC
IMEI: 35303000002xxxx
you've got the slider keyboard then your phone is a xdalls (blueangel)

Well that is a unknow rom and radio version
PLEASE POST
Ce version found under About in settings.

joelmax18 said:
Device Information:
ROM version: 0.99.00 ENG
ROM date: 06/09/04
Radio version: 0.91.00
Protocol version: 1337.27
ExtROM version: 0.99.111 WWE
Hardware:
CPU: Intel (R) PXA263
Speed: 400 MHZ
RAM size: 128 MB
Flash size: 32 MB
Flash chip type: 28F128K3
Data bus: 32 bits
Storage size: 43.26 MB
LCD: 240 x 320 TFT
Color: 65536
Identity:
Model No.: PH20B
Platform: Pocket PC
IMEI: 35303000002xxxx
Click to expand...
Click to collapse

can i update this telephone?
what rom i need?

joelmax18 said:
can i update this telephone?
what rom i need?
Click to expand...
Click to collapse
Looks like the Qtek 9090!

QTEK 9090
yes... this is QTEK 9090 they also sale in Netherland

MDAIIIUser said:
Well that is a unknow rom and radio version
PLEASE POST
Ce version found under About in settings.
Click to expand...
Click to collapse
That's a Blue Angel, so you can flash it with another BA ROM.
But please first try what MDAIIIUser said first before you flash over this unknown ROM version, so not under 'Device Information', but under 'About'.
As far as i know it doesn't really matter what 'brand' the phone is. They are all the same (HTC Blue Angel) except for the logo's printed on them.
I have an Orange SPV M2000, but i've had the Imate and O2 Asia ROM on it and i'm currently using the latest Qtek ROM.

About:
Windows Mobile 2003 Second Edition Version 4.21.1088 (Build 14132)
1996 - 2004 Microsoft Corporation.
All rights reserved.
This Computer program is protected by U.S. and International copyright laws.
Processor: Intel (R) PXA263
Memory: 125.77 MB
Expansion slot: In use

hey you can check your IMEI here
you can also see where your device is born at
http://www.numberingplans.com/index.php?goto=imei

IMEISV number analysis results
Manufacturer High
Model type Qtek 9090
Reference TW
Production date 08-11-2004
Phone version 0.1
Phone GSM phase GSM Phase 2 or higher
Country of handset approval
Official full name Republic of Finland
Short name FINLAND
ISO 3166-1-alpha-2 code FI
ISO 3166-1-alpha-3 code FIN
ISO 3166-1-numeric code 246
Time zone range (UTC) 2:00h UTC
Country / Destination flag
IMEISV number break-down
Type Approval / Allocation Code (TAC) 35xxxx
Final Assembly Code (FAC) 00
Serial Number (SNR) 00xxxx
Check Digit (CD) 5
Full IMEI presentation 353030-00-xxxxxx-x-xx

ok, when i tried the upgrade this happened error
Radio bootloader version error
please contact vender for helping

Read this guide. It should explain enough.
http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade

Well the Ce software is old
http://wiki.xda-developers.com/index.php?pagename=BA_Versions
which means that the rom veraion 0.99 is not a leaked ver 5.0. (which is why I asked the question)
Upgrade should work based on info in wiki.

strange thing..
my BA is from imate but the website says its qtek9090
IMEI number analysis results
Manufacturer High
Model type Qtek 9090
Reference TW
Production date 08-11-2004
Phone version N/A
Phone GSM phase GSM Phase 2 or higher
Country of handset approval
Official full name Republic of Finland
Short name FINLAND
ISO 3166-1-alpha-2 code FI
ISO 3166-1-alpha-3 code FIN
ISO 3166-1-numeric code 246
Time zone range (UTC) 2:00h UTC
Country / Destination flag

hehe mine too, i guess that site isn't very accurate.

joelmax18 said:
hi, i wanne know what brand is my pda for update, i checked this with Getdevicedata my result is it:
PH20B
0 B
ENG
G
11111111
0.99.00
0 0
0.99.111
0.91.00
91.00
my device look Blue Angel with Camara.
thank you
Click to expand...
Click to collapse

Trinity bootloader

i'm using the hermes/artemis reference to see what works and not
first: almost every other commands give the "Command Error"
the wdata exists and gives: Command is Locked!
The first thing will be to get into the radio bootloader - seems that the password is fixed. As far as the bootloader I hope that it can be downgraded.
---
info 2:
HTCSHTC__102Ã;¿HTCE
info 3:
HTCST
info 4:
IsAllBytesTheSame-: dwLength=8, bResult=0
HTCSHTC__102Ã;¿HTCE
info 6:
HTCST ÚÈÒHTCE
info 7:
HTC Integrated Re-Flash Utility, Common Base Version : 1.51b
Device Name: TRIN100, Bootloader Version : 1.06.0000
Built at: Oct 19 2006 20:31:29
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0xA
Main Board version=0x5
info 8:
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x18700
Partition[3], type=0x4, start=0x1B700, total=0x1F100
CE Total Length(with sector info) = 0x37BB800
CE CheckSum Length(without sector info) = 0x36E0000
-----
task 32 : Level FF
-----
checkimage
IPL CRC checksum = 0x96BE3C47
SPL CRC checksum = 0xBA45D40C
CE CRC checksum = 0xE86D6EC6
ExtROM CRC checksum = 0x3FBE8D13
Radio Image CRC checksum = 0xAB599ED8
-----
progress - shows bar

SD Upgrade
I tried the SD upgrade method.
I placed an nbh file on it called TRINIMG.nbh but after cheking gaves me "NOT ALLOW" 00028002
Any ideea ?

As your seclevel is FF, the CID on the NBH should be the same on your device. info 2 shows your CID = HTC__102 (HTC Germany), so you need to put an HTC german rom in the TRINIMG.nbh file or CID unlock your device.
Nice work on the bootloader

I've just decoded Trinity radio, it is very very similar to Hermes radio (Same Qualcomm JNAND Identification block), so radio bootloader commands should be the same in Trinity as on Hermes (and radio patch for SIM/CID unlock too!).
Normal bootloader commands should be quite similar too, but not necessarily the same, this is what I found on Trinity's SPL:
getdevinfo
ResetDevice
progress
ruustart
rbmc
password
info
task
emapi
btrouter
wdata
lnbs
erase
checkimage
checksum
wdata
wdatah
Click to expand...
Click to collapse
There's also the static password: BsaD5SeoA
Can you add all this info to the wiki?

pof said:
I've just decoded Trinity radio, it is very very similar to Hermes radio (Same Qualcomm JNAND Identification block), so radio bootloader commands should be the same in Trinity as on Hermes (and radio patch for SIM/CID unlock too!).
Normal bootloader commands should be quite similar too, but not necessarily the same, this is what I found on Trinity's SPL:
There's also the static password: BsaD5SeoA
Can you add all this info to the wiki?
Click to expand...
Click to collapse
excellent. i'm in office only with my trusted Universal (i'll fill up all the info tonight).

from artemis Wiki:
Artemis Bootloader Password
Seems that artemis bootloader password is static: BsaD5SeoA
If you enter this password in mtty terminal, you may not be able to boot device into Windows, only in bootloader. Be carefull.
It's meaning that Artemis has the same bootloader (or similar) with trinity.
The question: why it cannot get out from the bootloader ??

decebal said:
It's meaning that Artemis has the same bootloader (or similar) with trinity.
Click to expand...
Click to collapse
No, if you compare SPL they are very different one from the other.
Trinity's SPL is more similar to Hermes SPL, but Artemis SPL is different.
decebal said:
The question: why it cannot get out from the bootloader ??
Click to expand...
Click to collapse
probably you just need to 'set 14 0' or hard reset to go back to OS, I don't know... the wiki edit was done by fdp24, he can probably explain

pof said:
I've just decoded Trinity radio, it is very very similar to Hermes radio (Same Qualcomm JNAND Identification block), so radio bootloader commands should be the same in Trinity as on Hermes (and radio patch for SIM/CID unlock too!).
Normal bootloader commands should be quite similar too, but not necessarily the same, this is what I found on Trinity's SPL:
There's also the static password: BsaD5SeoA
Can you add all this info to the wiki?
Click to expand...
Click to collapse
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSTRIN100HTCE
--
Reset Device - works
--
Progress - works
--
ruustart - blocked - hard reset needed
--
rbmc - not working
--
password works with the password BsaD5SeoA
--
info - works as in wiki
--
task - works as in wiki
--
emapi and btrouter - blocks the device
--
wdata - works with the password provided
--
lnbs - not working
--
erase - working
HTCST ÚÈÒHTCE
--
checkimage - working as in wiki
--
checksum - seems working
--
wdatah - not working

seems that the 1.06 is somehow limited as bootloader. how can we get the 1.04 or other upgrade solution ??
thanks

Nice work on the wiki decebal
Answers to your comments:
rbmc and lnbs - probably only work on SuperCID devices.
emapi and btrouter - I think it switches to wlan or bluetooth and disables USB connection.
wdata and wdatah - In hermes wdatah is for flash NBH and wdata for flash NBF in preproduction devices. Have you captured a full ROM upgrade using USB monitor?? which one it uses the RUU? Probably it has a dynamic password which enables wdatah for NBH files. Does 'info 3' works as in Hermes (you need to watch usb monitor output, can't see in mtty generally).
decebal said:
seems that the 1.06 is somehow limited as bootloader. how can we get the 1.04 or other upgrade solution ??
Click to expand...
Click to collapse
Generally by flashing a ROM matching your CID with bootloader 1.04.

rbmc is not in spl in Artemis device. On Trinity probably too.
These are some commands for Artemis:
Could be similarity for Trinity
CASE SENSITIVE!
Cmd>fm
Wrong parameters of FM Command!!
Usage:
fm [command] [frequency]
where:
if[command] = i Initialize FM.
if[command] = o Power on FM.
if[command] = f Power off FM.
if[command] = t Tune FM channel to [frequency].
if[command] = a FM auto seek test.
if[command] = m Mono(1) or Stereo(0).
if[command] = v Volume (0x00 - 0x0F).
if[command] = u Mute(0)
if[command] = g AGC(1)
if[command] = h Set seek threshold (0x00 - 0xFF).
if[command] = s Seek Up(1) or Down(0).
if[command] = r Get RSSI (0x00 - 0xFF).
if[command] = c Get current channel [frequency].
if[command] = d Get RDS data (1 - 10 groups of data).
*****************************************************************************************************
Cmd>cpldver
xsvfExecute - CpldType=1
SUCCESS - Completed XSVF execution.
CPLD Ver[0]=1
CPLD Ver[1]=FC
CPLD Ver[2]=26
CPLD Ver[3]=5
SetDsbDBGMSGT
Unknown yet.
*****************************************************************************************************
Cmd>ReadExtROM
Dump Ext ROM to MTTY terminal
*****************************************************************************************************
Cmd>WLANReset
Usage:
WLANReset 1(or0)
set SDIO: 0-WLAN ;1-SDMC.
Cmd>WLANReset 0
WLANReset(FALSE)
Cmd>WLANReset 1
WLANReset(TRUE)
*****************************************************************************************************
Cmd>SDSelect
Usage:
SDSelect 1(or0)
set SDIO: 0-WLAN ;1-SDMC.
Cmd>SDSelect 1
Select SD Card
*****************************************************************************************************
Cmd>emapiWlanMac
Notice: This MAC address takes effect only when your platform is EEPRON-less configuration. Please use (emapiTest) to verify it !
Copying GSM DATA image to SDRAM:00004000
Wlan data header ++++++++++++++++++++
Signature : 0xEE1250
UpdateStatus : 0x2
UpdateCount : 0xA
BodyLength : 0x1A1
BodyCRC : 0x4349311B
Wlan data header --------------------------
0x00000000
0x00000009
0x0000002D
0x000000D2
0x000000D5
0x000000FB
*****************************************************************************************************
Cmd>emapiTest
+emapiTest
1. Power on WLAN
2. Reset WLAN
3. Switch MUX to WLAN
4. Enable WLAN clock
5. Init WLAN SDIO interface
6. DeviceID Test
DeviceID = 4030xxx
EEPROMless configuration!
-emapiTest
*****************************************************************************************************
Cmd>emapiPwrDwn
*****************************************************************************************************
Cmd>emapiRead
Parameter Wrong!!
*****************************************************************************************************
Cmd>getdevinfo
Need password!
*****************************************************************************************************
Cmd>wdata
Usage:
wdata [StartAddr Len]
Write data to memory(if write to ROM, need erase first).
StartAddr : Start address of memory.
Len : How many bytes will be written.
Length must not more than 0x10000 bytes(buffer limitation).
Write to RAM: 4 bytes(CRC checksum limitation).
1 byte(in user mode).
Write to ROM: 4 bytes(CRC checksum limitation).
2(16-bit)/4(32-bit) bytes(in user mode).
Write to ROM(16-bit data bus): 32 bytes(writebuffer mode).
Write to ROM(32-bit data bus): 64 bytes(writebuffer mode).
Length must be 4 bytes boundary(CRC checksum) if not in user mode.
After command execute, then send out the data to terminal.
Data format: HTCS(4 bytes)+DATA+checksum(4 bytes, if not in user mode)+HTCE(4 bytes).
*****************************************************************************************************
Cmd>password
Usage:
password [String]
Enter the password string to enable wdata, erase and rbmc functions.
*****************************************************************************************************
Cmd>set
Usage:
set [Type Value]
Set control flags.
Type(hex) : Control function types.
Value(hex) : Setting values for types.
Type 1(Operation mode): 1(auto) and 0(user).
Type 2(Back color on/off): 1(on) and 0(off).
Type 4(Front color value): 16 bits data
Type 5(Background color value): 16 bits data
Type 6(Set color of screen): Fill color to whole screen one time.
Current flag settings:
Type 1(Operation mode flag): g_cOpModeFlag=(0x0).
Type 2(Back color flag): cBackColorShowFlag=(0x0).
Type 4(Front color): g_dwFColor24bit=(0x0).
Type 5(Background color): g_dwBColor24bit=(0xFFFFFF).
Type 6(Set color of screen): None.
Type 32: Unlock Flash Command
Set control flags.
*****************************************************************************************************
Cmd>SetDebugMethod
Copying GSM DATA image to SDRAM:00004000
Default DebugTransport Value =00000000
Current Usage:
0 No Debug
A UART MTTY Output Debug Message
B USB MTTY Output Debug Message
*****************************************************************************************************
Cmd>checksum
Usage:
checksum addr len
Return CRC checksum of memory.
In user mode: Show 4 bytes of CRC checksum value on display of terminal.
In auto mode: Send 4 bytes of CRC checksum value to terminal with data format.
*****************************************************************************************************
Cmd>ResetDevice
no comments
*****************************************************************************************************
**When CID is locked.
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
Not allow operation!
Error : DownloadImage return error (code = 0xFFFFFFFF)
**When CID is locked.
*****************************************************************************************************
**When CID unlocked
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
start download
==CreateFile err==
**When CID unlocked
*****************************************************************************************************
Cmd>GPSRouting
Dump code to mtty console.
*****************************************************************************************************
Cmd>BTRouting
Dump code to mtty console.
*****************************************************************************************************
Cmd>BTRouting
+GSM_Modem_Init : include DAGON
Copying GSM DATA image to SDRAM:00004000
GSM - dwSize = 3479D
GSM Page0
GSM - dwSize = 45457
GSM Page1
GSM - dwSize = 4B768
GSM Page2
GSM - dwSize = 4E0A9
GSM Page3
GSM - dwSize = 4B4C4
GSM Page4
GSM - dwSize = 4C71F
GSM Page5
GSM - dwSize = 2958E
GSM Page6
GSM - dwSize = E8D8
GSM Page7
Copying GSM CODE image to SDRAM:00000000
ARMBOOT = 1 --> boot from CS3
Reset ARM 7 -- ok
Please close MTTY USB connection and open BT Testing program...
*****************************************************************************************************
*****************************************************************************************************
*****************************************************************************************************
*****************************************************************************************************
*****************************************************************************************************
*****************************************************************************************************
password BsaD5SeoA - this is static password used during flashing device. (USB sniffer)
battery seems to be charging during bootloader.
If you stuck at bootloader during manipulations with commands, try this:
password BsaD5SeoA
ruurun 0
Alternatively, you can run rom flasher even on CID locked device. It will give you error message about Device ID or something, but your device will be back to normal and boot normally.

Still problems with Data crashes error

I have followed the standard procedure to unlock the CID and SIM with the 1.05 button rom and lokiwiz02b.
I'm still running the 1.05 rom and I am stuck with the "data crashes...." error whenever I insert a sim card.
I red the instructions in the following thread:
http://forum.xda-developers.com/showthread.php?t=307558&highlight=data+crashes
With WST tools I found out that I had key index 48 so I used the file that is included in the thread to write back the CID block.
My problem is that I still get the "data crashes ..." error and my CID EMEI is now : FFFFFFFFFFFFFFF
What am I doing wrong? I thought my CID EMEI should be the same number as my EMEI at the label at the back of my device.
This is what WST gives when I read the CID block:
Reading CID block...
Calculating CID block sum...
CID checksum: CB3D5061
Decrypted stored sum: CBC0C8280DA8B6F6
Decrypted calcd sum: CBC0C8280DA8B6F6
Key index : 48 - Block index: 230
CIDkey: MODULESN
CID IMEI: FFFFFFFFFFFFFFF
CID: 11111111 (SuperCID)
Phone is already CID unlocked!

You can close this thread, I was so stupid, I actually flashed the wrong CID file to my phone. It was 40 instead of 48. Now it works like a charm!!!

Wizard Service Tool v4.2.1
31/10/07 17:38:49
CPU: Texas Instruments - OMAP850
MODEL: Wizard
IMEI: 356382007881016
=> Bootloaders:
IPL: 1.01 (G3 device)
SPL: 1.06 (G3 device)
Built on Nov 1 2005 at 16:44:44
Copyright (c) 2003 High Tech Computer Corporation
=> Firmware:
OS: 5.1.xxx (Build 14406.1.1.1)
ROM: 5.1
Registry AKU: .1.1.1
Radio: 01.01.10
Protocol: 4.0.13.16
=>Extended_ROM:
Version: Unknown
Name: Extended_ROM
Status: hidden
=> Drives and partitions:
|--Handle--|---Size---|
8ea13db6 - 10.00M (0xa00000)
eeae8ece - 48.23M (0x303c000)
0fb2af36 - 51.06M (0x3310000)
2fb2ad76 - 2.88M (0x2e0000)
cfb2ad52 - 3.06M (0x30fc00)
=> DOC chip unique ID:
000000008535010715250dcf0e010641
Key Index: 98
All Done.

HELP!"data crashes.contact service center"

hallo.
got a spv m3000 with the following problems:
1. the camera doesn`t work.. it`s shows some sort of green and black horizontal stripes [with a sim in it or not]
2. it works ok without a sim as a pda, but when i put a sim in it.. it shows "data crashes.contact service center"
using the Wizard service tool 4.2.1 i checked and it was cid locked, besides the cid was key 88 and DOC chip unique ID was 66
i followed http://forum.xda-developers.com/showthread.php?t=285435 and installed button`s rom and changed the cid key into 66 using WST and the keys provided ..
AND IT STILL DOESN`T WORK [i did everything fine, a couple of times]
i`m now currently here:
Wizard Service Tool v4.2.1
31/03/08 22:16:27
CPU Manuf. FAILED
MODEL: Wizard
IMEI: 356381000075907
=> Bootloaders:
IPL: 1.01 (G3 device)
Built on Sep 19 2005 at 18:00:32
Copyright (c) 2003 High Tech Computer Corporation
Getting more info...
=> Firmware:
OS: 5.1.xxx (Build 14406.1.1.1)
ROM: 5.1
Registry AKU: .1.1.1
Radio values FAILED
=>Extended_ROM:
Version: Unknown
Name: Extended_ROM
Status: visible
Getting drives,disks and partitions info...
=> Drives and partitions:
|--Handle--|---Size---|
8fb7d622 - 1.87G (0x778e0400)
0fb891ee - 10.00M (0xa00000)
aea14ec6 - 10.00M (0xa00000)
ceae9ece - 48.23M (0x303c000)
cfb2bf36 - 51.06M (0x3310000)
afb2bd76 - 2.88M (0x2e0000)
0fb2bd52 - 3.06M (0x30fc00)
=> DOC chip unique ID:
00000000a93802021223005c0a0905b8
Key Index: 66
All Done.
CID INFO:
Reading CID block...
Calculating CID block sum...
CID checksum: 2BB2824F
Decrypted stored sum: 626DAEC493E695B6
Decrypted calcd sum: 626DAEC493E695B6
Key index : 88 - Block index: 139
CIDkey: MODULESN
CID IMEI: 356382000275596
CID: 11111111 (SuperCID)
Phone is already CID unlocked!
any ideas?
thanks
tintome

not it works..
yey..10x..

tintome said:
not it works..
yey..10x..
Click to expand...
Click to collapse
hmmm, what happened? Did you fix it or not?
Did the Data Crashes Project worked for you? If so leave feedback in its thread. tx

Okay so whats next?

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!

impact12ed said:
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..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..
Click to expand...
Click to collapse
Not sure which file error you got, but you probably need the ROMUpdateUtility_Wizard_NoID.exe to get it to install.

error
impact12ed said:
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!
Click to expand...
Click to collapse
I think, it may because the RUU you are using is a little old perhaps? once, i was uploading a new ROM, but i had to take the nbf file from the ROM i wanted to a RUU folder (different folders)then i was able to flash/upload the new ROM