yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Snowflake_NZ:
Hi dgaud007

apologies for only replying now, life kind of took over ;-)

I completely forgot about SynCE - works okay with a long process, but it's working
[Desire General] Sideburnt:
Does anyone know of any possible way to make HTC Sync work with a non HTC ROM?.

I love the new OpenDesire ROM but wiss syncing with Lotus Notes at work.
[Desire General] foxmeister:
I'd imagine that it is quite unlikely.

Sense is more than just a home replacement, as it makes some quite deep changes in the frameworks.

Your best bet would be to strip as much as you can from a Sense ROM, and try to make it more like OpenDesire, rather than the other way around.

Regards,

Dave

EDIT: Have you looked at 3rd party syncing solutions as well? E.g. CompanionLink.
[Desire General] steve228uk:
While I doubt it works, the new HTC Sync install an APK to the device via ADB when you connect which is why it goes into debugging mode.

You could always try installing the APK, launching it and seeing if it works with HTC Sync.
[Desire General] TDO:
And how can I find this apk file?
[Galaxy S I9000 Android Development] Benjamin Dobell:
It has come to my attention that different versions of the Galaxy S may use different hardware IDs. This is problem as you need to know the hardware IDs of devices both in order to interact with them but also to install the drivers.

So I've decided to compile a list of hardware IDs. If your phone isn't yet supported by Heimdall (and it's not already on this list) please follow these instructions to add your device to the list:

Windows Vista / Server 2008 (Should be similar for XP & 7)

1. Open up Device Manager on your PC (Control Panel -> System -> Device Manager).

2. Under Universal Serial Bus Controllers right click on the Samsung composite driver (if in download mode) or your Galaxy S driver (if not in download mode) and chose Properties.

UPDATE: Turns out the Galaxy S and Windows aren't playing nice, even though Heimdall uses download mode we need information from when the device is NOT in download mode.

3. Go to the Details tab and select "Hardware Ids" from the "Property" drop down list.

4. Copy and paste your hardware IDs and fill out the rest of the form below.

---------- FORM ----------

Phone Name: <official name of the phone>

Country: <country name>

Carrier: <carrier you purchased from or N/A>

Hardware IDs:

<paste hardware IDs here>
[Galaxy S I9000 Android Development] jodue:
tried it on the virtual box with a windozexp but there is no "Samsung composite driver" option in the "Universal Serial Bus Controllers"... as virtual box just tunnels the usb through it should also be possible to get those values?

lsusb says (if this is the hardware id you are looking for?!):

Bus 001 Device 007: ID 04e8:681c Samsung Electronics Co., Ltd
[Galaxy S I9000 Android Development] DocRambone:
---------- FORM ----------

Phone Name: I9000

Country: Swden

Carrier: Tele2

Hardware IDs:

USB\Vid_04e8&Pid_681c&Rev_0223

USB\Vid_04e8&Pid_681c
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry I think it will only display "Samsung composite driver" if you're in download mode, I've updated the original post to reflect this. However you can still access the values using any of the Samsung drivers that your phones uses.

Thanks for the hardware IDs, those two values VID: 04e8 and PID: 681c and they seem to match the Australian hardware IDs. Perhaps my UK bought phone is not the international version after all.
[Galaxy S I9000 Android Development] us1111:
Phone Name: Galaxy S / I9000

Country: Netherlands

Carrier: KPN

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0400

USB\VID_04E8&PID_681C

Note: Also, when in debug mode, the device is also seen as Composite Device.
[Galaxy S I9000 Android Development] gunnarhafdal:
Phone Name: Samsung Galaxy S I9000

Country: Denmark

Carrier: 3

Hardware IDs:

Using a Mac but the ID's match the one from the Netherlands.

Product ID: 0x681C

Vendor ID: 0x04E8

Version: 4.00
[Galaxy S I9000 Android Development] shootr:
Phone Name: Vibrant T959

Country: USA

Carrier: T-Mobile

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0400

USB\VID_04E8&PID_681C
[Galaxy S I9000 Android Development] Aery:
---------- FORM ----------

Phone Name: Samsung Galaxy S GT-i9000

Country: Germany

Carrier: T-Mobile

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0400

USB\VID_04E8&PID_681C
[Galaxy S I9000 Android Development] darksnarfer:
---------- FORM ----------

Phone Name: Samsung Galaxy S (GT-i9000)

Country: UK

Carrier: Unlocked

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0223

USB\VID_04E8&PID_681C
[Galaxy S I9000 Android Development] mike.sw:
---------- FORM ----------

Phone Name: Samsung Galaxy S (GT-i9000)

Country: Bought from UK (clove)

Carrier: unlocked.

Hardware IDs:

USB\VID_04E8&PID_6601&REV_021;

USB\VID_04E8&PID_6601
[Galaxy S I9000 Android Development] veenone:
---------- FORM ----------

Phone Name: Samsung Galaxy S (GT-i9000)

Country: Indonesia

Carrier: unlocked.

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0400

USB\VID_04E8&PID_681C
[Galaxy S I9000 Android Development] tylerham:
Phone Name: Samsung Galaxy S Vibrant (GT-I9000M) --- Note, it's not a T-Mobile Vibrant, rather almost exactly the same as the International GT-I9000.

Country: Canada

Carrier: Bell

Hardware IDs:

USB\VID_04E8&PID_6877&REV_0400

USB\VID_04E8&PID_6877
[Galaxy S I9000 Android Development] Benjamin Dobell:
Yeah the Bell Vibrant has different hardware IDs though because it supports 850 MHz. I'll provide an updated Heimdall alpha to recognise the phone in 5-10 minutes.
[Galaxy S I9000 Android Development] Android Newbe:
Phone Name:

Samsung Galaxy S GT-i9000

Country:

Australia

Carrier:

Optus (Unlocked)

Hardware ID's:

USB\VID_04E8&PID_6601&REV_021;

USB\VID_04E8&PID_6601
[Galaxy S I9000 Android Development] seraphimserapis:
How can I get the data when using my MAC?

I want to support this :)
[Galaxy S I9000 Android Development] Silverdragondk:
---------- FORM ----------

Phone Name: Samsung Galaxy S (GT-I9000)

Country: Denmark

Carrier: TDC (Unlocked)

Hardware IDs:

USB\VID_04E8&PID_6877&REV_0400

USB\VID_04E8&PID_6877

That can't be the (only) reason. My phone has the same IDs as his, but it doesn't support 850MHz (for 3G).
[Galaxy S I9000 Android Development] Darkyy:
I didn't try yet, but i think with the SYSTEM PROFILER.
[Galaxy S I9000 Android Development] olivier constantin:
Galaxy S

---------- FORM ----------

Phone Name: Galaxy S

Country: France

Carrier: unlocked

Hardware IDs:

USB\VID_04E8&PID_6601&REV_021;

USB\VID_04E8&PID_6601
[Galaxy S I9000 Android Development] Mumps:
---------- FORM ----------

Phone Name: Galaxy S GT-I9000

Country: Spain

Carrier: Movistar

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0223

USB\VID_04E8&PID_681C

--------------------------

From what I gather there's 1 vendor ID, 3 product IDs with 4 different revisions:

USB\VID_04e8&PID_681c&REV_0223 Countries: sw, uk, es

USB\VID_04E8&PID_681C&REV_0400 Countries: nl, dk, us, de, indonesia (unlocked)

USB\VID_04E8&PID_6601&REV_021; Countries: uk (unlocked), aus, fr (unlocked)

USB\VID_04E8&PID_6877&REV_0400 Countries: ca, dk (unlocked)
[Galaxy S I9000 Android Development] VikingDK:
---------- FORM ----------

Phone Name: Galaxy S GT-I9000

Country: Ireland

Carrier: Vodafone

Hardware IDs:

USB\Vid_04e8&Pid_6877&Rev_0400

USB\Vid_04e8&Pid_6877

--------------------------
[Galaxy S I9000 Android Development] titovic:
--------------------------

Phone Name: Galaxy S GT-I9000

Country: Canada (SingTel unit from Singapore)

Carrier: Bell

Hardware IDs:

USB\Vid_04e8&Pid_681C&Rev_0223

USB\Vid_04e8&Pid_681C

--------------------------
[Galaxy S I9000 Android Development] vinny.1967:
Phone Name: Samsung Captivate

Country: USA

Carrier: AT&T

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0400

USB\VID_04E8&PID_681C
[Galaxy S I9000 Android Development] iDeViLFoX:
--------------------------

Phone Name: Samsung Galaxy S GT-I9000

Country: Malaysia

Carrier: Maxis (Unlocked)

Hardware IDs:

USB\Vid_04E8&Pid_681c&Rev_0400

USB\Vid_04e8&Pid_681c

--------------------------
[Galaxy S I9000 Android Development] FadeFx:
sorry for being so late... ;-)

Phone Name: Samsung Captivate

Country: Austria

Carrier: A1 Telekom Austria

Hardware IDs:

USB\VID_04E8&PID_681D&REV_0400

USB\VID_04E8&PID_681D
[Galaxy S I9000 Android Development] Benjamin Dobell:
You might be a bit late but that's a brand new product ID you've got there (681D) :) I'll have to make a new release that adds support for that product ID.
[Galaxy S I9000 Android Development] Muaddib69:
--------------------------

Phone Name: Samsung Galaxy S GT-I9000

Country: Spain

Carrier: Free/Unlocked (now with Yoigo)

Hardware IDs:

USB\VID_04E8&Pid_681C&Rev_0400

USB\VID_04E8&Pid_681C

--------------------------
[Galaxy S I9000 Android Development] distortedloop:
Can the firmware you've flashed impact this?

My phone is from Singapore, SingTel was the carrier, but it was unlocked and I've flashed it with JM6 for Europe, and I'm using it on AT&T in the US.

My Hardware IDs are the same as the ones from Europe.

Hardware IDs:

USB\Vid_04e8&Pid_681c&Rev_0223

USB\Vid_04e8&Pid_681c

I don't have multi-csc, and since someone reported multiple versions, I wonder if the csc might impact that as well.

PS. On my Mac, in Download mode only, this is reported in Profiler:

Gadget Serial:

Product ID:	0x6601

Vendor ID:	0x04e8 (Samsung Electronics Co., Ltd.)

Version:	2.1b
[Galaxy S I9000 Android Development] Benjamin Dobell:
Nah, flashing the firmware won't have an impact, well it shouldn't anyway. The hardware identifiers are supposed to be stored in and retrieved from the hardware. Nonetheless, Heimdall actually treats all phones the same. The hardware identifiers are just required for installing the drivers and then identifying which USB device to connect to.
[Galaxy S I9000 Android Development] maciejus:
Phone Name: GT i9000

Country: Poland

Carrier: N/A

Hardware IDs:

USB\Vid_04e8&Pid_6601&Rev_021;

USB\Vid_04e8&Pid_6601
[Galaxy S I9000 Android Development] Finguz:
Phone Name: GT-I9000

Country: UK

Carrier: Orange but is Unlocked.

Hardware IDs:

USB\VID_04E8&PID_6877&REV_0223

USB\VID_04E8&PID_6877
[Galaxy S I9000 Android Development] Banger242:
Phone Name: GT-I9000

Bought in Canada - Unlocked/Sim Free

Carrier: Bell

Hardware ID's:

USB\VID_04E8&PID_681C&REV_0400

USB\VID_04E8&PID_681C
[Galaxy S I9000 Android Development] leonsio:
Phone Name: GT-I9000

Bought in Germany (1&1) - Unlocked/Sim Free

Carrier: Vodafone (not branded)

Hardware ID's:

Product-ID:	0x6601

Vebdor-ID:	0x04e8 (Samsung Electronics Co., Ltd.)

Version:	2.1b

Infos form my mac...
[Galaxy S I9000 Android Development] youneek:
Someone else already posted this but I didn't see it on the main Heimdall thread.

Phone Name:Vibrant T959

Country:USA

Carrier:T-Mobile

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0400

USB\VID_04E8&PID_681C
[Galaxy S I9000 Android Development] FadeFx:
i had realized that, thats why i posted here... ;-) you should keep a list in first post with knowen ids, so people dont fill the thread with the same 681c id...
[Galaxy S I9000 Android Development] dutchcow:
USB\VID_04E8&PID_6877&REV_0400

USB\VID_04E8&PID_6877

Mine is bought simfree from the CPW here in London.
[Galaxy S I9000 Android Development] SysTem-X:
Phone Name: Galaxy S GT-i9000

Country: Malaysia

Carrier:Maxis

Hardware IDs:

USB\Vid_04e8&Pid_681d&Rev_0400

USB\Vid_04e8&Pid_681d
[Galaxy S I9000 Android Development] Benjamin Dobell:
Would you mind verifying that slightly? As far as I can tell A1 don't sell the Samsung Captivate but instead sell the GT-I9000, however I could be wrong. Where did you purchase the phone from?
[Galaxy S I9000 Android Development] a-son:
---------- FORM ----------

Phone Name: I9000

Country: Sweden

Carrier: Telia(UNLOCKED)

Hardware IDs:

USB\VID_04E8&PID_6877&REV_0400

USB\VID_04E8&PID_6877
[Galaxy S I9000 Android Development] lealdud1:
Phone Name: GT-I9000

Country: Norway

Carrier: Telenor / Unlocked

Hardware IDs:

USB\VID_04E8&PID_6877&REV_0400

USB\VID_04E8&PID_6877

Same as a-son above.
[Galaxy S I9000 Android Development] USHERROB:
---------- FORM ----------

Phone Name: Samsung Captivate i897

Country: USA

Carrier: AT&T

Hardware IDs:

USB\VID_04E8&PID_681C&REV_0400

USB\VID_04E8&PID_681C
[Galaxy S I9000 Android Development] rjmjr69:
Phone Name: Samsung Epic 4G sph-d700

Country: United States!

Carrier: SPRINT

Hardware IDs:

USB\VID_04E8&PID_6601&REV_021;

USB\VID_04E8&PID_6601
[Galaxy S I9000 Android Development] getmoney2xl:
Can i get a samsung epic...?

---------- FORM ----------

Phone Name: SAMSUNG EPIC D700

Country: UNITED STATES

Carrier: SPRINT

Hardware IDs:

USB\VID_04E8&PID_6601&REV_021;

USB\VID_04E8&PID_6601
[Galaxy S I9000 Android Development] Benjamin Dobell:
Sorry guys forgot to let you know. It turns out that all Galaxy S use the same hardware ID when they're in download mode.

VID: 04E8

PID: 6601

If anyone does find a different ID whilst they're in download mode please let me know. This thread should still be fairly useful though to anyone who wants access to the VIDs and PIDs of numerous devices.

This thread has been reinstated, read the following few posts for information.
[Galaxy S I9000 Android Development] getmoney2xl:
My phone is currently in download mode.... then why didn't windows detect any new drivers in the new Heimdall's drivers folder?
[Galaxy S I9000 Android Development] Benjamin Dobell:
Did you follow the instructions to install the drivers exactly? Your VID and PID match those of the driver info file:

You don't want to just install the driver if it's "newer" than your existing driver. It's a totally different driver (LibUSB) to what Samsung are providing for Kies. You want to install the driver regardless of whether Windows says it's dated newer.
[Galaxy S I9000 Android Development] getmoney2xl:
of course I follow your instructions... carefully.

By the way I never had Kies installed on this machine before...

How do you do that?

I tried to delete or uninstall the current driver from device manager but when I plug it back in... windows is already searching for the driver... and didn't prompt me for input, by then the driver is found. And to update the current driver by myself DID NOT help.

Window Vista.
[Galaxy S I9000 Android Development] Benjamin Dobell:
Hmm, sorry it appears though you are following the instructions correctly.

I'm not entirely sure what is going on as PID 6601 is definitely what Heimdall uses to connect to devices but it appears as though the Galaxy S and Windows aren't playing nice in terms of product IDs. In the device manager the device is listed as having PID 6601. However I'm trying to install a driver using PID 6601 now and Windows refusing to do so. Instead Windows will only install the Heimdall driver when the inf file is using PID 681C, which is the PID of my device when the phone is booted up regularly.

Anyway I will reinstate this thread and provide updated Windows binaries with updated install instructions and so forth. However I'm about to head out so I won't be able to do so for a few hours.

However in order to resolve your problem do the following.

1 Open Drivers/Heimdall.inf in Notepad.

2. Change the line:

to whatever your product ID is when you're not in download mode (it will presumably be one of the IDs listed in this thread, most likely:

3. Follow the original install instructions as per usual but when you get to step 6 chose "Let me pick from a list of device drivers on my computer".

4. Click "Have disk" and then browse to and select the Heimdall.inf file you just modified.

5. Click next and follow the instructions, if you get warned about an unsigned driver don't worry just install it anyway.
[Galaxy S I9000 Android Development] sshvetsov:
Phone Name: Samsung Galaxy S Captivate SGH-I896

Country: Canada

Carrier: Rogers

Hardware IDs (using Mac OS X):

Product ID: 0x681c

Vendor ID: 0x04e8 (Samsung Electronics Co., Ltd.)

Version: 4.00
[Galaxy S I9000 Android Development] anarchos:
Hmm, doesn't work with my i9000m (bell). I took the risk of flashing a new kernel using a redbend_ua based app and it totally bjorked it. I don't have a PC, just a mac. I can only get into Download mode, and my mac recognizes it (Using system profiler), but heimdall doesn't recognize the phone (unsupported error). If I sent the ID's from Mac OS X's system profiler, would that help? They seem to be in hex. Anyways, my phone is also my only access to the internet, except at work. Everything on the work PCs are locked down too (tried installing Odin on one), so I'm pretty much screwed. Just need to flash a kernel!

I guess it would have been a good idea to test Heimdall before flashing that kernel, haha! I gave myself a 50/50 chance of it working....I just assumed flashing a kernel from a Mac wouldn't be so hard if something went wrong.

Sorry for the rambling post
[Galaxy S I9000 Android Development] Benjamin Dobell:
Is the phone visible in the system profiler when the phone is in download mode or just composite mode (normal boot)?

Because you need download mode, which is dependent on having a correctly functional secondary bootloader. If you can see the device in download mode (your product ID will be 0x6601) then Heimdall should work. If you can see the phone in download mode and it's still not working then let me know more details in the Heimdall thread. I'll need the exact error you're getting.
[Galaxy S I9000 Q&A, Help & Troubleshooting] sweetzed:
hi

is there a solution to root on my GS the JP3 froyo's verion ?

or it d'oes'nt exist at this moment ?

thank's
[Galaxy S I9000 Q&A, Help & Troubleshooting] sergmarin:
Much simply is to use JP3 firmware from Modaco, pre-rooted / insecure boot / ClockworkMod recovery for Odin.
[Galaxy S I9000 Q&A, Help & Troubleshooting] BlazerRazor:
You should look a little around before you post.

Follow this walkthrough; http://xdaforums.com/showpost.php?p=7461563&postcount=23
[HD2 General] yugius:
Hello Guys,

I'm trying to do a device stage for the HD2, because I think the HD2 is not really good implanted and I want to change this.

The Device Stage is a feature of Windows 7 which bundles all the device informations and functions in one window.

Microsoft released recently a SDK and I got it and tried working a bit.

Now my problems:

First one is that I need the unique hardware id(s) of the HD2. I tried to get it but all I got is:

DOID:TCPIP\WINDOWS_MOBILE_DEVICE

DOID:USB\VID_0BB4&PID_0B40&REV_0000

DOID:USB\VID_0BB4&PID_0B40

The first ID isn't recognised at all and the second and last one do recognise the HD2, but like it seems not all features the phone is capable off.

Do you have infos or tips? Would help me a lot do get a device stage for us all ;)

Below this my very first alpha of the device stage, like I said, just started and have to figure things out.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] flashy:
I use an Exchange account and two imap accounts, i dont want work emails blasting the audible alert off, but i do want the two imap accounts to have audible notifications.

Is this possible?
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
@mods: sticky....?

i will add future roms to the list.

My projects:

HD2O ROM Series

X1O ROM Series

Latest Opera 9.70 thread

HD2 WP7 donation fund for da_g

HD2 haret/linux/android donation fund for devs (cotulla, dcordes, markinus, letama, netripper)

HD2 6.5.3 global bold font fix (by ultrashot)

HD2Owner's youtube channel

Great tools by Barin:

OS Builder (Kitchen)

LEO Advanced ROM Update Utility

Blackstone Advanced ROM Update Utility

Topaz Advanced ROM Update Utility

Kovsky Advanced ROM Update Utility

Whitestone Advanced ROM Update Utility

HTC Splash Tool
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
reserved post 1
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
reserved post 2
[HD2 Windows Mobile 6.5 ROM Development] Rouz.:
Thanks!

thanks for sharing! useful information :)
[HD2 Windows Mobile 6.5 ROM Development] sirgal:
It'd be great if you could indicate the date when the chart was last updated

Thanks!
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
edit:

cleaned up and added some roms.
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
@xmoo:

please help me to find roms missing.
[HD2 Windows Mobile 6.5 ROM Development] xmoo:
Cool stuff you doing here.

Uhhm:

TMOUS 2.04, 2.06, 2.08, 2.12 are MASD_S Roms, Conflipper has those but MASD_S ROMS are very special, and that's why he didn't share them. But they do exist.

Where did you get: 1.34.405.4 from... ? Never heard of it.

I also had a dump of 0.81, but lost it somewhere....

And Radio 1550 is: 1.02.50.11 Protocol 15.12.50.07U
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
new roms added (thanks to xmoo for the roms and infos).
[HD2 Windows Mobile 6.5 ROM Development] xmoo:
Where did you get: 1.34.405.4 from... ? Never heard of it.

0.67

0.67 Pure

3.01

All flashed on a PRO THREE.

The first 7 ROMS did have 320 MB and not 128.

TMOUS 2.02 has the SPL 2.00.1 MFG

TMOUS 2.03 has SPL 2.00.2 (no MFG)

TMOUS 2.09 has also SPL 2.08

The MASD_S all have MFG SPL's.

I didn't know there were 2 versions of the 2.05, Could you upload them both??
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
wich one should i upload:

2.05.531.4 or 2.05.531.6?
[HD2 Windows Mobile 6.5 ROM Development] xmoo:
both plz.

Where did you get: 1.34.405.4 from... ? Never heard of it.
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
1.34.405.4 - saw it on pictures and in a video (don't have this rom)

RUU_Leo_1_5_TMOUS_2.05.531.4

it's just a os.nb inside a rar that states: www.Twitter.com/Xmoo :eek::D

RUU_Leo_1_5_TMOUS_2.05.531.6_Radio_Signed_15.30.50.07U_2.06.50.23_3_Test

rar with LeoCustomRUU.exe and LEOIMG.nbh

i have problems when dumping the roms.
[HD2 Windows Mobile 6.5 ROM Development] xmoo:
Could you give me link of the video and upload the full ruu of the second 2.5

Thx.
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
intresting step-back from 23014 (0.67.405.1) to 23013 (0.67.405.1).

right at the point where the 6.5.x ui-changes became active before 23018.

0.67.405.2 debug rom

pictures can be found here: LINK

[YOUTUBE]<object width="640" height="385"><param name="movie" value="http://www.youtube.com/v/Xaw84roLOUQ?fs=1&hl=de_DE"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/Xaw84roLOUQ?fs=1&hl=de_DE" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="640" height="385"></embed></object>[/YOUTUBE]

http://www.youtube.com/watch?v=Xaw84roLOUQ
[HD2 Windows Mobile 6.5 ROM Development] xmoo:
0.67.405.1

you found the vid link of 1.34??
[HD2 Windows Mobile 6.5 ROM Development] xmoo:
Huh I got RUU_Leo_1_5_TMOUS_2.05.531.6_Radio_Signed_15.30.50 .07U_2.06.50.23_3_Test already and if the other is mine aswell than it's 1 rom.... Just wrong info... I think .6 is the correct one.

And the Oboe has 576MB RAM
[HD2 Windows Mobile 6.5 ROM Development] aniyuth:
latest version rom hd2 leo

Can i get the latest version rom for htc hd2 leo

do let me know asap.
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
3.14.531.0 added
[HD2 Windows Mobile 6.5 ROM Development] chteh2008:
thanks for sharing this useful information
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
thread updated (advanced infos for 3.14.531.1 coming soon).
[HD2 Windows Mobile 6.5 ROM Development] e192326:
Funny I am running Android 2.2 on my HD2 TmoUS and just got a txt from T-Mobile stating a update is available, 3.14.531.1. Located at their website /wmupgrade , what is the chance this is compatible with Android with no issues?
[HD2 Windows Mobile 6.5 ROM Development] HD2Owner:
it is. even the new european roms are android compatible (spl3.03).
[HD2 Windows Mobile 6.5 ROM Development] xmoo:
From 2.01 till 2.05 I believe, the ROMS were tested on a PB81220

TMOUS HD2 with 512MB ROM instead of 1024MB ROM.
[HD2 Windows Mobile 6.5 ROM Development] ADB100:
Anyone have a copy of the leaked 23021 ROM?