Database Users

Upgrade Success

I tool the big leap! It was met with success. Was able to upgrade my Vogue to Rev A/GPS using the Sprint rom. Everything went fine. No issues. The advice I received was most helpful as well as the read me notes that was included within the file. YOU GUYS ROCK!
Now, the real fun begins. Finding a mapping program to use with the GPS. I ran across a rom that requires the user to install a program that will install the 3.37.15 radio version. With the new upgrade to my unit the current radio version is 3.42.30. Isn't this considered a downgrade? Wont it create hardware issues? Feedback is appreciated.

Might want to put this in the correct fourm. This is for the Juno aka TMobile Shadow. The Vogue is a different unit.
Now from a general Radio standpoint, yes technically it would be a downgrade of sorts to go from 3.42.30 to 3.37.15. While it may be considered a downgrade it may be better to use one version over the other for performance issues. I know that on my Wizard, Radio 2.40.11 worked better than any of the newer versions fr use with TMobile in the states. Some people had better luck with other Radio versions using Cingular\ATT in the states and others with different versions in different countries with different providers and so on. It is all a matter of which Radio works best with your ROM\Carrier\Location.

HD2 not turning on after flashing rom

After flashing the stock rom located on the wiki page.
Link to the download is http://rapidshare.com/files/345363601/RUU_Leo_HTC_WWE_1664052_Radio_.exe
The phone will just not turn on now, when I plug it into my computer it recognizes hardware but the screen doesn't turn on at all, any ideas what can be causing this or a way to fix this?
Thank you for your help.

I'm pretty sure you've just turned your device into a shiny, $500 paper-weight.
If the radio you flashed was included... and anything other than what is compatible with the T-MOBILE USA model... then you're ****ed.
For instance, I'm almost certain that the radio value ending in .52 cannot be flashed successfully without bricking the device. Correct me if I'm wrong.
I'm sorry though, this is rather unfortunate.

Reignzone said:
I'm pretty sure you've just turned your device into a shiny, $500 paper-weight.
If the radio you flashed was included... and anything other than what is compatible with the T-MOBILE USA model... then you're ****ed.
Click to expand...
Click to collapse
Correct, the rom is 1.66 for a start, which wont work on tmous. It doesnt say what radio is included, but i can tell you no 1.66 wwe roms include tmous compatible radios.
For instance, I'm almost certain that the radio value ending in .52 cannot be flashed successfully without bricking the device. Correct me if I'm wrong.
Click to expand...
Click to collapse
You actually mean radios with a 51 in them (example 2.09.51.x) kill tmous, not 52.
Radios with a 50 in them and higher than 2.06 will work with tmous. (example 2.08.50.x)
Unlucky. Take it back, play ignorant, get it replaced.

[Q] Which Radio version?

I have NAND Android installed on this phone and I'd like to update the phone to the latest version. But I am not sure which one as some of them works OK, while other doesn't work very well.
My HTC HD2 comes with the following info:
R - 2.07.51.22.2
G - 15.32.50.07U
D - 1.66.76641
Which version of radio should I go with? I am looking for one that has a *very* good 3G connection speed.
Thanks,

Out of all of the radio versions available, IMO the best is 2.15.50.
You can find it here
http://www.multiupload.com/QP0IWGY42F
People have reported that supposedly 2.14.00 gives better battery life but I didn't find this to be the case.

Depends on location and network Im afraid....
I could be wrong but I didnt think that the Radio you mentioned would allow you to run android from NAND.....
Either way... the popular ones are between 2.08.50.xx - 2.15.50.xx
The one I use is in my signature and gives me pretty good 3G reception...
Trial and error though Im afraid.

Sorry, forgot to mention that I am from UK and I'm using the T-Mobile network.

tsutton said:
Sorry, forgot to mention that I am from UK and I'm using the T-Mobile network.
Click to expand...
Click to collapse
That doesn't really matter, all of the good Android radios (2.12.50 and above) will work fine with you, you can either use the one I recommended, or trial and error the other 3.

Thanks all, am currently testing 2.15.50.14

tsutton said:
Thanks all, am currently testing 2.15.50.14
Click to expand...
Click to collapse
That's the most commonly used one.

[Q] Does new radio (6.35) help with 3G issues?

I have a rooted Roger's HTC Magic running ezterry's official OTA 2.2 ROM. It's fantastic except I continue to have problems where my 3G connection will stop working and the only workaround is to cycle Airplane mode.
Does anyone know if installing the new 6.35 radio (and a support ROM) would help with this problem? I've tried to find out more info on the difference between the two radios but there doesn't seem to be much.
Thanks!

tsouthen said:
I have a rooted Roger's HTC Magic running ezterry's official OTA 2.2 ROM. It's fantastic except I continue to have problems where my 3G connection will stop working and the only workaround is to cycle Airplane mode.
Does anyone know if installing the new 6.35 radio (and a support ROM) would help with this problem? I've tried to find out more info on the difference between the two radios but there doesn't seem to be much.
Thanks!
Click to expand...
Click to collapse
The 6.x radio is not compatible with the same rom structure as the 2.x/3.x and requires some new drivers and utilities..
So if you want a rom made for 2.x/3.x to work you can't use 6.x radios..
The problem is presumably you have radio 3.22.26.17 .. this has buggy 3g but is the one rogers will not disable your data without signing the e911 wavier.
If you are not a rogers customer there is no reason to use 3.22.26.17.. return to 3.22.20.17 via fastboot.
If you have signed the e911 wavier you can also downgrade.
The 6.x can work without the wavier but you will need to find roms for it (various in the sapphire section check carz12's work)

ezterry said:
The problem is presumably you have radio 3.22.26.17 .. this has buggy 3g but is the one rogers will not disable your data without signing the e911 wavier.
The 6.x can work without the wavier but you will need to find roms for it (various in the sapphire section check carz12's work)
Click to expand...
Click to collapse
Correct, I am a Rogers customer and have the 3.22.26.17 radio. I tried signing the online waiver but it just keeps telling me to enter a valid serial number. Maybe you have to be cut-off before you can sign the waiver. I'm not interested in getting my data cut off and then have to wait to get it back.
I guess I'll look into a 6.35 Gingerbread ROM.

tsouthen said:
Correct, I am a Rogers customer and have the 3.22.26.17 radio. I tried signing the online waiver but it just keeps telling me to enter a valid serial number. Maybe you have to be cut-off before you can sign the waiver. I'm not interested in getting my data cut off and then have to wait to get it back.
I guess I'll look into a 6.35 Gingerbread ROM.
Click to expand...
Click to collapse
No you just need to call them.. probably best anyway (as it leaves more options available)
That said that isn't to say anything is wrong with a properly created 6.x radio + related rom... just it makes the device something different than the Dream/Sapphire combo I am used to working on .. and something closer related to the HTC Hero.. This while appears to be a very similar device is not identical.

ezterry said:
No you just need to call them.. probably best anyway (as it leaves more options available)
Click to expand...
Click to collapse
OK, I called Rogers and asked to be put on the waiver list and was told that they couldn't put me on the list until I was blocked. I'm not too confident this is the right answer. Do you know if this is true? If not, what is the right thing to say to get them to do this?
Thanks!

[Q] Should I Update Radio On T-Mobile G2?

Rooted T-Mobile G2 with S-off.
Preparing to upgrade my ROM from Stock OTA 2.15.531.3 to stock OTA 2.16.531.5 from the T-Mobile G2 Stock OTA Thread - http://forum.xda-developers.com/showthread.php?t=1314541
Should I also be updating my Radio from the HTC Vision Radio's Thread - http://forum.xda-developers.com/showthread.php?t=970809?
- If yes, what sequence should I follow? Update Radio and then ROM or vice-versa? How-to links, Dummy procedure manuals, etc. would be welcome.
Thanks.

Just popping in, someone will help you out more in depth, but it does not matter which order you do it in BUT....you may want to try the ROM on your old radio to start.
Flashing radios can be dangerous, and their performances vary depending on your location. If after flashing your new rom you have poor signal or battery life, then flash a radio using the instructions in the radio thread. But if everything is peachy keen, if it ain't broke don't fix it.
Sent from my T-mobile G2 using Tapatalk

I have recently flashed this same rom you want to, but came from mexdroid. The way I see it with flashing radios is if it's from T-Mo (and if you're on t-mo) then the update would include the radio anyway if the new radio came with the new update.
I flashed the radio first, but in my experience it doesn't matter. The newest official T-Mo radio is "Vision_Radio_12.62.60.27_26.13.04.19" and download the zip file. To install, rename it to PC10IMG.zip and put on root of SD card. Then hold the down volume button while turning on the phone and follow the prompt from there. This is the safest way to update the radio.
So far, in this build with this radio the time the radio is in use is far less than usual and battery life rocks.

I 'm running the pre-rooted OTA 2.15.531.3 ROM but left my radio at the 26.03.02.26_M as the phone came (with the original Froyo ROM). It works, but ever since the upgrade, my conversation partners experience the annoying echo on their end (they hear their own voice delayed).
Similar issues were reported by others but so far, nothing I tried fixed the issue.
I now think this is due to the older radio not matching some settings in the new ROM. I never had this with the Froyo ROM.
Also, when I'm using WiFi calling, the echo is not there which further points to the radio as the culprit.
The interesting thing is that whenever I'm in a noisy environment (like when in a restaurant, mall etc.), the problem is not present but in quiet environments it's always there.
So I'm also thinking about flashing the radio and hope that the problem gets fixed... I'm just nervous to do it and eventually mess up the phone. After all, other than this, everything works perfectly...
I'm not even sure which radio should I pick from that other post. Should I just go with the latest T_MOBILE OTA 2.16.531.5 radio even though my ROM version is lower? I don't necessarily want to upgrade the ROM and deal with customizing the phone again (yes, I know Titanium Backup helps, but there is still work left after that).

If upgrading from stock rooted to the new ota rooted rom its ok and best to undate the radio to since they Booth were part of the update and work well together and so u can take more advantage of the better power management .. and yes battery did improve with new ota and radio
Sent from my T-Mobile G2 using XDA App

digikid said:
The way I see it with flashing radios is if it's from T-Mo (and if you're on t-mo) then the update would include the radio anyway if the new radio came with the new update.
Click to expand...
Click to collapse
That is exactly the way I look at it as well. I've only updated my radio once, and it was to the latest T-Mo radio. I took it one step further, and also RIL matched as detailed in another thread here on the XDA forums.

Thanks all for your help and advise. I finally found some time to do the updates last night. ROM is now at 2.16.531.5 and radio at Vision_Radio_12.62.60.27_26.13.04.19. All is working well and hopefully the annoying echo will also have disappeared.

I honestly think that flashing a new radio is not necessary unless you really have nothing else to do. maybe change do dz hboot u will require a dif radio (that diff story) but yeh. no really obvious point for u to flash. unless ur signal is really, really, bad?

FullScreen57 said:
...hopefully the annoying echo will also have disappeared.
Click to expand...
Click to collapse
Ah, so then you also had the echo issue before the update, similar to me? Echo reported by your conversation partners?
If so, then please post whether the update fixed the problem.
Thanks.
Sent from my T-Mobile G2 using xda premium

xyz_969 said:
Ah, so then you also had the echo issue before the update, similar to me? Echo reported by your conversation partners?
If so, then please post whether the update fixed the problem.
Thanks.
Click to expand...
Click to collapse
Sorry for the delay in replying back. I was busy with work and updating my son's G2.
I also matched the lib-ril files, and wiped the cache, dalvick cache and the efs partitions. The echo problem seems to have been fixed for now.
I compared the Android version, Baseband version, Kernel version and Build number on both my son's and my G2's against my wife's G2 (which is stock, unrooted and receives direct OTA updates from T-Mobile). All the version numbers match up perfectly.
Thanks to all for their help.

nelsdzyre said:
I honestly think that flashing a new radio is not necessary unless you really have nothing else to do. maybe change do dz hboot u will require a dif radio (that diff story) but yeh. no really obvious point for u to flash. unless ur signal is really, really, bad?
Click to expand...
Click to collapse
Actually after finally rooting and getting CM7 running, I was running into a problem when I would go in or out of an area that had no signal. I would essentially not be able to connect back to the network.
After upgrading to 12.62.60.27U_26.13.04.19_M (tmobile) my problem went away. Of course, ymmv, but it was a good upgrade (for me)

mrpoundsign said:
Actually after finally rooting and getting CM7 running, I was running into a problem when I would go in or out of an area that had no signal. I would essentially not be able to connect back to the network.
After upgrading to 12.62.60.27U_26.13.04.19_M (tmobile) my problem went away. Of course, ymmv, but it was a good upgrade (for me)
Click to expand...
Click to collapse
What he said!!! Also, it made more sense to me to have the radio at the same version as the one T-Mobile pushed OTA to all the stock G2s (having my wife's phone as a reference helped)