Australian (telstra) HTC desire on Telus

[cmstlist]

If it works fine when swapped, maybe you should just keep it that way?

You could take a Titanium and nandroid backup of both phones, swap SIM and SD, and then restore, and you'll both have everything you had before.

Sent from my Nexus One using Tapatalk

[HC - NO "i"]

chunkdude,

It has eliminated another possibility then. I think there is some difference in the configurations for the SMS (in the baseband software as well?) besides baseband hardware difference. Well, if firmware update is available to your Telstra HTC Desire, you may give it another try. BTW, do you have access to a Rogers or Fido SIM card?

cmstlist,

You have the good suggestion. But what version of Android the TELUS and Telstra Desire are running? Both have got the same build of Froyo? I wonder if it will bumped into problem with the restore if both variants of Desire are running on different build of Android. Not to mention, it requires root to use Titanium backup.

[cmstlist]

I think the main incompatibility would be attempting to run the Telstra Eclair ROM on the Telus device, as the first ROMs for AMOLED Desires didn't support SLCD screens. Once Froyo arrived, the same ROM provided universal hardware support for both types of screen.

Also, I believe the HTC Desire radio software is designed to work with whatever the phone has. You can flash the same baseband on a 850/1900, 850/2100, 900/2100 Desire and you'll still end up with all the phone's hardware bands functional.

I wonder if you might see different results if you flash an unbranded firmware RUU instead of Telstra's. You'll of course want to take Titanium and nandroid backups first to be safe. All of this only if you're comfortable hacking the phone.

Sent from my Nexus One using Tapatalk

[HC - NO "i"]

cmstlist,

Thanks for your sharing. Learn something today

As for the modem / radio file (baseband software) mix and match... so it is the exact case with the Samsung and other makes, isn't it? Of course, it does not matter if someone tries to put the 850/1900 baseband in a 850/2100 variant, the baseband hardware remains unchanged. But it leads me to another question with the significant difference between the Telstra and TELUS' variant software... are there anything in the way, so chunkdude would experience the mentioned service problems?

[cmstlist]

cmstlist,

Thanks for your sharing. Learn something today

As for the modem / radio file (baseband software) mix and match... so it is the exact case with the Samsung and other makes, isn't it? Of course, it does not matter if someone tries to put the 850/1900 baseband in a 850/2100 variant, the baseband hardware remains unchanged. But it leads me to another question with the significant difference between the Telstra and TELUS' variant software... are there anything in the way, so chunkdude would experience the mentioned service problems?

Some brands are very sensitive to which baseband you flash: Motorola, sometimes LG, sometimes Samsung. So if you flash an 850/1900 baseband to a 900/2100 Motorola Defy, not only do you lose 3G but you also get very poor 2G signal. HTC seems to ship with universal ratio software for all hardware revisions - *exception, the Inspire 4G/Telus Desire HD has audio problems if you flash an Asian or European baseband.

I have no idea why one version would miss messages though, especially when it happens on Telus but not Bell!

Sent from my Nexus One using Tapatalk

[chunkdude]

to be clear, both phones are running froyo. the telstra phone is running the telstra froyo update, and the telus/bell phone is running a clean unbranded copy of sense froyo, so i dont think the screens have anything to do with it.

if i flashed her phone with the same unbranded clean copy of sense froyo, would that make a difference? or are the radio frequencies hardware based and flashing clean froyo wouldnt do much?

some stats from the about phone section:

TELSTRA PHONE RUNNING ON TELUS - A8183

Baseband version
32.48.00.32U_5.11.05.14

Kernel version
2.6.32.15-g5d39305
htc-kernel@and18-2 #1

Build number
2.26.841.2 CL258170 release-keys

Software number
2.26.841.2

Browser version:
Webkit 3.1

-----

TELUS PHONE RUNNING ON BELL - A8181

Baseband version
32.49.00.32U_5.11.05.27

Kernel version
2.6.32.15-gf5a401c
htc-kernel@and18-2 #1

Build number
2.29.405.2 CL263770 release-keys

Software number
2.29.405.2

Browser version
WebKit 3.1

[cmstlist]

to be clear, both phones are running froyo. the telstra phone is running the telstra froyo update, and the telus/bell phone is running a clean unbranded copy of sense froyo, so i dont think the screens have anything to do with it.

if i flashed her phone with the same unbranded clean copy of sense froyo, would that make a difference? or are the radio frequencies hardware based and flashing clean froyo wouldnt do much?

The radio frequencies are hardware-based. However the fact that the Telstra device had no problem on the Bell network (which is exactly the same as the Telus network) suggests that something about the Telus *services* running over that network are not talking properly to the Telstra Desire. It's entirely possible that a firmware change could fix that. So yeah, try out the unbranded Froyo and see. Just be a dear and nandroid backup her phone first

[chunkdude]

so i got a hold of my friends rogers sim card, plunked it in, and still inconclusive.

texts sent from the phone, it seems the first time you send someone a text it works, and after that for the most part nothing goes through, with the odd message making its way in

now the new development. when i sent a message to the telstra phone (now on rogers) it receives it just fine, but dates it 4 hours earlier than it actually is.

im gonna flash unbranded froyo on tomorrow and see if there are still problems

[cmstlist]

now the new development. when i sent a message to the telstra phone (now on rogers) it receives it just fine, but dates it 4 hours earlier than it actually is.

Hah, well that's a totally unrelated issue. The Rogers network puts the wrong timestamps on SMS. Androids released for Rogers and Fido have been tweaked to fix this. There is an app in the Market called SMS Time Fix which helps users of unlocked Androids on Rogers to fix this up.

[chunkdude]

hi all. so we're running out of options, as the problems are still persistent. i havent been able to debrand the phone. i debranded my telus phone with a fresh clean copy of 2.2 froyo sense upgrading from 2.1. however, her phone already had 2.2 so im not having luck flashing with an unbranded copy. so you need to be upgrading os versions to do this? at this point we're probably looking for a used desire to use here, since im guessing having only the one band in common is causing all the issues. i cant really deduce anything else other than that.

but yeah, isit possible to flash a phone with a clean unbranded 2.2, even though it has telstra 2.2 on it right now, without rooting?

[cmstlist]

hi all. so we're running out of options, as the problems are still persistent. i havent been able to debrand the phone. i debranded my telus phone with a fresh clean copy of 2.2 froyo sense upgrading from 2.1. however, her phone already had 2.2 so im not having luck flashing with an unbranded copy. so you need to be upgrading os versions to do this? at this point we're probably looking for a used desire to use here, since im guessing having only the one band in common is causing all the issues. i cant really deduce anything else other than that.

but yeah, isit possible to flash a phone with a clean unbranded 2.2, even though it has telstra 2.2 on it right now, without rooting?

Did you use a gold card when trying to flash the RUU? That will usually be necessary. It will also need to have a equal or newer bootloader version. Maybe there is a newer unbranded RUU than the one you tried? Such as this one:
http://forum.xda-developers.com/showthread.php?t=869048
2.29.405.5 World Wide English, newer than the version on either of your Desires.

All other ways to debrand will require root first. You could use unrevoked (or possibly AlphaRevX?) to obtain radio S-OFF, and then it will allow you to debrand regardless of version. If you prefer not to have root, you're free to leave it unrooted after flashing the new RUU.

Sent from my Nook Color!

[chunkdude]

Did you use a gold card when trying to flash the RUU? That will usually be necessary. It will also need to have a equal or newer bootloader version. Maybe there is a newer unbranded RUU than the one you tried?

All other ways to debrand will require root first. You could use unrevoked (or possibly AlphaRevX?) to obtain radio S-OFF, and then it will allow you to debrand regardless of version. If you prefer not to have root, you're free to leave it unrooted after flashing the new RUU.

Sent from my Nook Color!

yeah i tried with a goldcard. i used a goldcard ruu to bring my telus desire up from 2.1 to 2.2 without issue. for hers, the current build number is 2.26.841.2 and im trying to upgrade to a rom thats 2.29.405.2

i have no idea what a bootloader is.

[cmstlist]

I edited my post above with a link to a newer RUU.

Sent from my Nook Color!