Related
Anyone know if there is potential brick-danger in changing a radio rom? I currently run the Cingular 2.25.0001 .. and was wondering if the T-mobile 2.19 was better and if it was safe to replace my G4 8125's radio rom with the T-mobile one..
Thanks
Madcap180 said:
Anyone know if there is potential brick-danger in changing a radio rom? I currently run the Cingular 2.25.0001 .. and was wondering if the T-mobile 2.19 was better and if it was safe to replace my G4 8125's radio rom with the T-mobile one..
Thanks
Click to expand...
Click to collapse
I had i scary moment in my first flashing days when i tried a radio only updater that didn't work and i lost the ability to connect to active sync. I then discovered phones could be flashed from boot loader and fixed it with a full official ROM.
But the answer is NO, a radio upgrade does not brick the phone and you can upgrade just the radio (gsm_data zone) by using an updater made for that purpose.
The question is: is the file well made? are the addresses correct?
Two choices:
Make your own radio updater. Easy these days with all the tools and info
Get an updater from a reliable source or from places with positive feedback by other members. I believe there is a thread for that in 'Wizard Upgrading' section
Hope it's clear, good luck.
cheers
Yea I flashed it to T-mobil radio 2.19 .. worked flawlessly.. i havent run into any problems flashing ANYTHING yet.. I think i am getting lucky.
Madcap180 said:
Yea I flashed it to T-mobil radio 2.19 .. worked flawlessly.. i havent run into any problems flashing ANYTHING yet.. I think i am getting lucky.
Click to expand...
Click to collapse
yeah, i should have see your signature duhh
anyway, it still can be useful for others with less knowledge
Hey all.
I picked up a 2nd hand T-Mobile (I think) MyTouch Unlocked a couple of months ago and have been busy about rooting and flashing since. I'm on Telus in Canada, and my 3G SIM works fine for data and voice, practically out of the box. However the last time I flash its rom, about 1 week later the 3G data stopped working suddenly. I tried everything I could reasonably think:
- Called Telus and had them reset my SIM
- Tried a different Telus SIM
- Rebooted/battery pull, whatever I could think of
- Reflashed a bunch of roms, including my 1st working Cyanogen
Its been a month or so since then (I've been overseas) and thought I would try to do something about it before I returned. If I can't get the data working again, I might as well start looking for a new phone. :-(
Fast Boot gives me the following information:
SAPPHIRE UNKNOWN 32B ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-11
RADIO-2.22.19.261
I'm running RA-sapphire-v1.5.2G for flashing. Right now I've got KiNgxKlair-DroidEris2G flashed, but it doesn't matter as I can't test anything right now. (in Japan)
Does anyone have any ideas? Maybe I screwed up and stuck a 32A rom on my 32B are some point?
What about my radio version? I have never been able to find any great information online about radio versions and never attempted to flash it. Could a reflash to even the same version help?
Any suggestions would be really appreciated. I'm not interested into getting into another 3 year contract and even 2 year old Androids are still selling for $400 used. Plus this MyTouch has been great so far. (until the data died...)
Thanks!
You should upgrade to 3.22.23.02 version radio
Radio & SPL
Both are zipped inside that file. You don't need to flash your SPL if it works for you. But try that radio and see if it's working better for you.
Fast reply!
Kemekill, thanks for the quick reply!
I'll give it a try tonight. Is there a good source for radio related info? I've had a hard time trying to piece together what the story is on radio updates because they typically get mixed in with provider specific stories or 32A vs 32B, etc... I wasn't able to locate a wiki or anything central.
If its all common knowledge then I'm clearly not digging deep enough.
Thanks!
Well here's what i think the issue is. Most myTouch roms only work with specific radios thus your out of date radio is probably the problem
The only real source you'll find on radios is in the main developers thread on XDA and maybe something from Cyanogen's Wiki
I'm so confused. Because I've got a 32B I'm having a hard time finding good information on how to flash just the radio. Every post starts with the radio and ends up only talking about SPL. I've got SPL 1.33.2005 so I should be good, but I need to try to do something about my malfunctioning radio. Is the Android SDK required to flash a radio.img? My RA-sapphire-v1.5.2G supports flashing from zips. Sorry to come off as a newb. My experience with Android rooting and roming has been its easy to get into, but maintaining if you blink for a couple of months is difficult. If I can just get my radio working again I'll leave it alone.
Thanks for any help anything can throw my way.
Forget it. SDK, flash radio, got it.
underto said:
Forget it. SDK, flash radio, got it.
Click to expand...
Click to collapse
How did you get 3G speeds on non- AWS network like Telus? Because Tmobile MyTouch only works on AWS- Frequency.
**EDIT**
After reading another post of yours I think you have the rogers version, because of your 32b board. But just for a heads up if its branded "T-Mobile" then that means 3G speeds will only work with Wind Wireless or Mobilicity.
VNPrince said:
How did you get 3G speeds on non- AWS network like Telus? Because Tmobile MyTouch only works on AWS- Frequency.
**EDIT**
After reading another post of yours I think you have the rogers version, because of your 32b board. But just for a heads up if its branded "T-Mobile" then that means 3G speeds will only work with Wind Wireless or Mobilicity.
Click to expand...
Click to collapse
The Rogers one is 32A. Just checked mine. All the T-mo MT3G's are supposed to be 32B iirc...
I bought this phone off Craigslist with a bunch of accessories for $180. The data worked for 24 hours, then since this phone didn't have the 911 fix, it shut off. Now, signing the Rogers waiver for me simply doesn't work. I've called Rogers countless times for this and there is nothing they can do.
I asked this question on androidforums and someone told me to upgrade to 5.0 Cyanogen and a new kernel thing. I did all that and I'm still without data over 72 hours later.
My current settings/about phone info is:
Firmware: 2.1-update1
Baseband Veersion: 62.52S.20.18H_3.22.20.17
Kernel Version: 2.6.33.4-cyanogenmod
Build Number: EPE54B
Now all I want to do is either downgrade to the 1.5 OS or keep the 2.1 or 1.6 OS with data. I know you can downgrade through HTC Sync, but all of my 6 family PCs do not recognize my phone through HTC Sync.
So what do I need to download/flash or whatever to get my data working? I'm not very technical savvy with Androids so if anyone can direct me to a good guide I'd be thankful.
Thanks
EDIT: I'm on a 32A device, if that matters.
Anyone?
I want this solved or I'm just going to sell this damn thing. Who wouldda thought Androids could be so difficult.
I think the problem you are facing is that because you cannot sign the waiver, you need to upgrade to the new radio. That is how rogers determines whether or not you have the 911 fix and are able to use data on their network. There are a few sources around here that can help you do that. (I'm not allowed to post links, so remove the space after the first h...)
h ttp://forum.xda-developers.com/showthread.php?t=677045 - Radio Switcher Tool
h ttp://forum.xda-developers.com/showthread.php?t=605239 - Manual Method
Once you upgrade the radio, you will need to pick a rom that uses the new 6.35.xx radio, if you want 2.1, I would highly recommend this one:
h ttp://forum.xda-developers.com/showthread.php?t=689652
There are several more roms that use the new radio and some are better than others, most are easily discernible with [6.35] in the thread title.
Hope this helps!
mrapp said:
I think the problem you are facing is that because you cannot sign the waiver, you need to upgrade to the new radio. That is how rogers determines whether or not you have the 911 fix and are able to use data on their network. There are a few sources around here that can help you do that. (I'm not allowed to post links, so remove the space after the first h...)
h ttp://forum.xda-developers.com/showthread.php?t=677045 - Radio Switcher Tool
h ttp://forum.xda-developers.com/showthread.php?t=605239 - Manual Method
Once you upgrade the radio, you will need to pick a rom that uses the new 6.35.xx radio, if you want 2.1, I would highly recommend this one:
h ttp://forum.xda-developers.com/showthread.php?t=689652
There are several more roms that use the new radio and some are better than others, most are easily discernible with [6.35] in the thread title.
Hope this helps!
Click to expand...
Click to collapse
I tried following the first one and got lost not only when I tried to create a fastboot, but also when I needed an SPL or whatever for a fastboot but I needed a fastboot for an SPL.
So confusing. Is there any easier way to do this?
hwy cannot you not get anything done by rogers? if you pay for data you are entitled to it regardless of what phone you use
tell them its a non-rogers phone called the htc magic from europe or something and it has long since been fixed before this 911 issue occurred on Rogers ;P
if they dont fix it then escalate to manager and if you have to office of the president
http://www.rogers.com/web/content/contactus
has the office of the president listed as well as other support numbers
Andy348 said:
I bought this phone off Craigslist with a bunch of accessories for $180. The data worked for 24 hours, then since this phone didn't have the 911 fix, it shut off. Now, signing the Rogers waiver for me simply doesn't work. I've called Rogers countless times for this and there is nothing they can do.
EDIT: I'm on a 32A device, if that matters.[/B]
Click to expand...
Click to collapse
The best (but certainly not easiest fix since it involves dealing with Rogers) is to call in and get escalated to 2nd level support (at least). They have a team that can add IMEIs to the blessed (do not scan/blacklist) list. Once you get your IMEI on the list you will have data again. If you politely keep insisting to get escalated technically (not to a manager) you can get to someone who has the ability to fix the problem. Keep pointing out that the issue is with Rogers and their implementation of the 911 fix (scanning and blocking on radio firmware level) and that your device is updated and does not have the issue. You need to keep insisting that the issue has nothing to do with your phone. The nice thing is once you get on the list, you will not have any more data issues. Based on my experience this will likely take you multiple calls and expect to loose data at least a couple of times during the process.
I went this route since my updated ROM already had the 911 fix and I was not downgrading to their ROM nor was I willing to sign their waiver and accept unspecified and unlimited liabilities.
Second option is to update the radio to 6.35 (since that is what Rogers is scanning for and making the blocking decision on) and get them to reset your data. That will also work except there are a lot more ROMs available for the old radio so this will certainly limit you.
I have no problem with data on my Magic, running a 1.6 ION based build, and using the old radio.
by escalating to tier 2 you are agreeing to the waiver verbally so they can add the fix...
no point in not doing the waiver if it works for u
You might try out the steps here to use the Dream radio with your Magic, that way you will still have 3G data: h ttp://greatbigdog01.wordpress.com/2010/05/10/rogers-post-e911-magic-to-cm-5-0-7-android-2-1-with-dream-e911-radio/
I'm using it here and it's great.
I tried calling Rogers again and claiming I was on the other operating system, they say they'll look at it.
Does anyone have a more noob-friendly guide to downgrading my Radio?
Andy348 said:
I tried calling Rogers again and claiming I was on the other operating system, they say they'll look at it.
Does anyone have a more noob-friendly guide to downgrading my Radio?
Click to expand...
Click to collapse
If you are on a 3.x radio currently, just flash the 3.22.26.17 E911 radio from the dream into your Magic. It's compatible and Rogers will then detect your phone as updated.
GreatBigDog said:
If you are on a 3.x radio currently, just flash the 3.22.26.17 E911 radio from the dream into your Magic. It's compatible and Rogers will then detect your phone as updated.
Click to expand...
Click to collapse
No it wont
If you have a 32A you need to sign that waiver to be on old radio. Request tier 2 support and just get them to give it to you. It's a pain in the behind not to do it. CM5 is well worth the hassle.
xaueious said:
No it wont
If you have a 32A you need to sign that waiver to be on old radio. Request tier 2 support and just get them to give it to you. It's a pain in the behind not to do it. CM5 is well worth the hassle.
Click to expand...
Click to collapse
Actually GBD has been using the Dream radio on the Magic for a while now without getting data cut off.
To Rogers the Dream radio isn't the old radio therefor passing the scan sweep.
Just flash over new radio?
Hey guys,
I also have the same problem with rogers. I have been sent to tier 2 support but was wondering if I could just flash 3.22.26.17 E911 radio over top of my current one (3.22.23.18)? Would it brick the phone without having to wipe and reload the rom?
Thanks.
Mod. edit: not dev related, moved to general
Not sure where the best place to ask this is...
I have:
HBOOT-1.33.2010 (SAPP50000)
3.22.23.18
RA 1.6.2H
Can I simply flash the 3.22.26.17 radio via ADB fastboot and be good to go on the sweep?
(edit: I have a Rogers Magic 32A on the Rogers network... trying to get the Dream radio on it per GBD's advice)
Today I bought a Wildfire that has a branded OS by Telstra, I don't like a lot of the extras and startup screens and junk that is there. So I rooted the phone and flashed it with that popular Puzzlerom but I didn't really like it so I recovered back to my original from a backup. Is there anyway for me to flash it with the latest official ROM from HTC or get rid of the branding on my current Telstra ROM?
So I've done some searching, I found some references to getting the official HTC ROM from Shipped-ROMS. I couldn't find anything on the website, but when looking at the website index directories I found the Buzz folder but I don't know which HTC ROM to download. I want the latest one and I'm not really sure what the difference in versions numbers are as there are so many and all of them are pre-dated before the 2.2 release and I don't know if there is a difference in Radios and I don't want to upgrade to the latest version and have my phone not picking up reception and not being able to possibly revert it as I don't know if 2.2 is rootable.
I'm also unsure If I can simply run the official WWE .exe if my phone is rooted without some kind of corruption.
If somebody could give me a quick guide or point me to a thread which could help.
In a nut shell my situation is:
Telstra Branded Firmware Version: 2.1-update1.
Software number: 1.21.841.3
Kernal: 2.6.28-543e5f81
Rooted
Need to unbrand and get latest official HTC rom.
I too am interested in a fix for this?
cheers
Turns out I'm actually really stupid.
In the Development subforum people post the official ROM and safe .zip versions of it too -_-.
Debrand Telstra Wildfire
Am curious about doing this the Telstra firmware is quite annoying not to mention god knows when Android 2.2 will become available. I have tried all the RUU update i can find none work, get either error 130 or 140... main problem seems to be the model id of my phone is incorrect. I currently have 2.1-update1, baseband 13.55.55.24H_3.35.20.10, software number 1.30.841.1. Anyone got any ideas how to get rid of the Telstra firmware in favour of the standard HTC?
chrisj9898 said:
Am curious about doing this the Telstra firmware is quite annoying not to mention god knows when Android 2.2 will become available. I have tried all the RUU update i can find none work, get either error 130 or 140... main problem seems to be the model id of my phone is incorrect. I currently have 2.1-update1, baseband 13.55.55.24H_3.35.20.10, software number 1.30.841.1. Anyone got any ideas how to get rid of the Telstra firmware in favour of the standard HTC?
Click to expand...
Click to collapse
http://www.shipped-roms.com/downloa...5.55.24H_3.35.20.10_release_160191_signed.exe
have you tried this one?
Its Froyo by the way
Or browse in here:
http://www.shipped-roms.com/index.php?category=windows mobile&model=Buzz
I bought a Telstra Wildfire before Xmas and used the follwoing procedure to debrand it to a stock HTC ROM.
The Wildfire came with ROM ver 1.21. I upgraded it to 1.37. See http://shipped-roms.com/shipped/Buzz/ for a list of the HTC roms. I used http://shipped-roms.com/shipped/Buz...3.55.24H_3.35.19.25_release_151892_signed.exe as it is the most recent one that can still be rooted. The next one is Froyo (http://shipped-roms.com/shipped/Buz...5.55.24H_3.35.20.10_release_160191_signed.exe) however if you flash this one you will not be able to root it unless someone works out how to at some time in the future.
Firstly you will need to root the phone using Unrevoked (http://unrevoked.com/#wildfire).
Secondly create a goldcard (http://android.modaco.com/content/software/308798/pc-application-goldcardtool/)
The goldcard is necessary as, even though the phone has been rooted, the upgrade program will note that the CID in the phone is for Telstra and you are installing a non-Telstra ROM. You will get an error without the goldcard. The goldcard will override this detection and allow stock HTC and custom ROMS to be installed on your phone. Once you have installed the new stock HTC ROM using the goldcard, the goldcard will not be required for future stock ROM upgrades. It may not be required for upgrades to custom ROMS either but someone else may be able to verify this as I have not tried them.
Some people have had trouble getting the goldcard to work using thrid party SD cards. If you use the one that came with the phone you will not have trouble. The only problem with this is, as part of the unrevoked rooting, you will probably have done an nandroid backup which will dump backup files on the card so that you can restore your original ROM if you wish. I skipped this backup as shippedroms has the standard Tesltra 1.21 rom on their site (http://shipped-roms.com/shipped/Buz...45.55.24_3.35.15.31_release_138758_signed.exe) so that you can restore the phone to standard if required.
Thirdly, install the stock ROM (http://shipped-roms.com/shipped/Buz...3.55.24H_3.35.19.25_release_151892_signed.exe) with the goldcard in the phone.
This will unroot your phone but you can re-root it again as you did in the first step above.
You can upgrade to Froyo but read the posts under the Wildfire Android Development section of these forums so that you understand the disadvantages of doing so. Many have been to quick to upgarde and have been caught out!
I am going to wait until unrevoked can root Froyo before I install it.
Has anyone tested that the phone can still communicate at 850mhz after running this process?
The phone I ran this on still works at 2100mhz, but lost 850mhz, which more renders a Telstra wildfire useless (Unless you're a city dweller with ample 2100 coverage)
Is it possible that the radio firmware flashed in with the european image (which is of course designed for the 900/2100 radio) does not work properly with the hardwre in this phone? I've done a lot of searching on this subject and have come up completely empty!
Hey guys,
I bought Eclair Wildfire Telstra-branded only weeks ago, straight away rooted it and installed Sunaabh ROM (a stable, stock-like Froyo ROM). Apart from Telstra splash screen (unable to remove because we have S-On) it is debranded of course. I dunno what you mean about the radio stuff, but I live in faaaaarrrr west Sydney (Wallacia) which is pretty much country and I get 3G. Is that full NextG speed...? I really don't know!
Do NOT install official 2.2 update! It will remove root and install the new, currently unrootable HBOOT!
EDIT: What is this goldcard nonsense? Do your research! Unrevoked3 installs the Clockworkmod recovery and you can then flash ANYTHING.
Sent from my HTC Wildfire using Tapatalk
I think by now I can say there's 2 ways of debranding a Wildfire A3335:
What I did (don't do this anyone else!):
* Run a stock RUU. Fully fully debrands it (No telstra logos anywhere). Also replaces the radio firmware with an eurpoean version and destroys your phone's rural (850mhz) coverage
What you did (and what I should have done):
* Just replace the ROM. Leave the Radio firmware in place: End result: You still have a phone that works on 850mhz but you've also got an annoying telstra boot screen, and there's not a damn thing that can be done about it until S-OFF is figured out for Wildfire.
jonusc said:
Hey guys,
EDIT: What is this goldcard nonsense? Do your research! Unrevoked3 installs the Clockworkmod recovery and you can then flash ANYTHING.
Click to expand...
Click to collapse
The Goldcard is for people who choose to run the HTC RUU upgrade process, as described by lemming999. As you just reflashed your ROM, it is expected that you would not require a Goldcard.
As per my post above. *** Do not run this unless you really don't care about your rural coverage ***
Ok - I've posted a solution for getting 850MHz 3G back again for anyone silly enough to do what I did. Read here: http://forum.xda-developers.com/showthread.php?p=11559059#post11559059
inaxeon said:
Ok - I've posted a solution for getting 850MHz 3G back again for anyone silly enough to do what I did. Read here: http://forum.xda-developers.com/showthread.php?p=11559059#post11559059
Click to expand...
Click to collapse
Is it possible that you have S-OFF as a result of flashing an RUU? I assume no, because there are no RUU packages which have an "Engineering" SPL included... right?
What about SIMLOCK? True debranding should remove the CID if you can share whether you can use non Telstra SIM cards now, I may pursue the Goldcard/RUU process myself!
I don't have S-OFF at the end of this. But the HTC RUU does have the ability by some means of magic to COMPLETELY debrand the phone (including the first boot screen) and ruin your radio in the process.
So now that I've managed to restore the Telstra radio, I have have a 100% unbranded, fully working A3335 while most people tend to be stuck with the telstra logo at the SPL.
If S-OFF was obtainable on wildfire I think this process would be a lot easier but I got the desired result in the end. Reflashing the radio is pretty dodgy. I've avoid it as if it goes wrong. Your phone is a doorstop.
jonusc said:
What about SIMLOCK? True debranding should remove the CID if you can share whether you can use non Telstra SIM cards now, I may pursue the Goldcard/RUU process myself!
Click to expand...
Click to collapse
Yes non telstra SIM cards work. Although, I bought the phone unlocked so I don't know how this came about. as for the CID, it may remain, it may not. I don't know how to tell. There's a fairly good chance it was nuked when I flashed with the Euro RUU.
Fair enough, thanks for the detail. I'm not fussed on SIMLOCK (no vodafone coverage out here anyway), was just curious.
In regards to s-off, it is determined by SPL which AFAIK every RUU has. But again, every PUBLIC RUU would have nandlock. But there are some Wildfire users here who do have s-off, and say they don't remember how they did it (they never noticed until down the track). Odd.
Sent from my HTC Wildfire using Tapatalk
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)