Well, I just got the dev rom loaded and this is really great... Although my problem is still this...
I am fairly certain my GSM radio is still CF'd... The unit runs slow (probably due to phone related issues) and when I goto bootloader mode, I am still told that the GSM Error is still existing...
Has anybody managed to use XDA Rite to either put the TMobile RSU on their unit or the ATT RSU on their unit...
I understand you can't go backwards, but I am not sure the ATT RSU ever really went through...
I certainly seem to be seeing the end of the tunnel somewhere...
As always, any help would be appreciated...
Todd
Why don't u try to load att image again? Problem is there is no way to backup GSM rom, so u must use RSU upgrade from the provider. run the att rsu upgrade again and it will load the Radio stack.
alex
I want just the radio ROM, I get dropped calls a lot- but not just dropping, the antenna cuts out, and resets. I am running OS 2.24 and ROM 2.25 (I am using the custom version). Problem has been happening since 2.17 version, and having read though a few items, I thought i would try to run Radio ROM 1.08 or 1.09, seemed to solve a friends issue, but they don't have the ROM anymore. Anyone able to send it my way?
bump... anyone got anything for me?
First, this is a known issue (there is a thread 10 pages long about it) see here: http://forum.xda-developers.com/viewtopic.php?t=53432
Second, you can not use a 1.x Radio Rom with 2.x Bootloader and vice-versa.
Third, per the thread I referred you to the problem is not the Radio Rom but rather the connection method some programs (i.e. Agile Messenger & PocketWeater 1.3.x) use.
Please use the search function before starting a new thread about an existing issue.
Sorry thanks for the input! I normally browse over at Howard's Forums and this problem creeps up often with no fix- assumed those over there check over here since there are so many blank threads overthere with this issue.
Thanks again, I will make sure to refrence anyone from there to the thread you provided.
Thanks!
Hi Guys
If I receive or make a call then the speaker and mic goes dead, I have to do a soft reset to get it going again.
I've got this strange problem, I've flashed different custom roms and nearly all the radio roms but the problem is still there.
I have tried changing settings and nearly everything I could find to remedy this but no luck, please help.
hmm, thats a nasty thing, have you tried an official rom from htc? or the murrata radio or the newest radio?
ive had the same problem before with some roms, but then it was fixed when i updated the radio version..
im running on phamquam rom v44 now with radio 1.59.44.02 and combination thats working fine!
your cam and gps working correcly btw?
Hi Thanks for your reply
Everything else is fine, just this problem.
I've tried Radio Murata and the latest rom but still problem exists.
I'm running the phamquam v44 rom as well with radio 1.58.21.23, but i've been through all the radios I could find including the one you're running but the problem is still there.
I can only make or take only one call and then the speakers and mic go dead until I soft reset, i can run the music player but no sound.
This is really doing my head in.
By the way radio Murata totally wipes out the battery on my device within hours i have to recharge plus when I receive a call or make one it starts making a buzzing sound out of the speakers, so i had to soft reset and flash another radio.
FIXED:
I've managed to fix it by flashing it with a really old rom but when I upgrade it back to the newest rom versions I have the same problem again, so I guess i'll have to stick to the old roms for now.
hmm, thats weird, i dont have that much knowledge but maybe it is different hardware in polaris versions?
Just to let you know I have upgraded to the latest official rom and that works fine and the funny thing is my neighbour brought me his friend's Kaiser with exactly the same problem, so I tried a custom rom on it and that didn't work, then flashed the Official rom and that worked fine.
Any suggestions!
I love Spotify on my PC so was excited to see it being released for WinMo as I have a HTC HD2. I even upgraded to the Premium service to just to check it out.
BUT.......After trying the market place and also downloading the CAB file, both these method result in "installation was not successful".
Anyone else have problems or can help?
Hi, I downloaded the cab and it installed fine for me, infact this is an amazing app, even picks up on my music networked folders and integrates them too. Not sure why you have an issue though. I have stock o2 rom btw. 1.72 I think.
Just had a thought, make sure your Netframework is upto date 3.5 I thnk is the one I`m on.
I'm using Vodafone's most recent ROM 1.72.
How do check / update the Framework 3.5?
Try this method and also try searching these forums; lots of other people have been trying to get this too.
http://pocketnow.com/how-to/tutorial-how-to-upgrade-to-microsoft-net-compact-framework-35
I did a hard reset (always hate doing that) and its seems to have sorted out the problem.
Will try and add .net 3.5 as well though.
Thanks
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)