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)
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
Well several months ago I rooted my own ROGERS dream using the cyan guide here:
http://wiki.cyanogenmod.com/index.p...-_Rogers_Dream_EBI1_to_CyanogenMod&oldid=1539
Now I went to root my brother's rogers dream but the instructions have changed:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
It's now asking me to flash a newer radio during the procedure. As I never did this when I rooted I am hesitant to root. Could someone possibly tell me why the guide's change and why I now have to flash this radio
search the site for "Rogers 911", you will find lots of info on this. I am not familiar with it, but have seen MANY posts about it.
But this phone doesn't have the 911 updates. What will updating the radio do?
The new radio is the one included in the mandatory update. There is no harm in flashing it. You can always go back if you want. You can even leave that step out if you want to keep your old radio. I have no idea what has been changed in the new version but I haven't noticed any difference. Some people say they have better reception and some say they have worse reception with the new radio.
Will it work ?
Read the thread. Your answer is in there.
No one will hold your hand for you. You're a big boy.
You know you could just be nice about it, since you took the time to actually reply.
The answer is yes, afaik.
http://android.modaco.com/content-page/309286/frf50-froyo-pre-rooted-update-zip/page/60/
Post 76
There's also a post later on in that thread containing an AT&T rom without the radio update (which apparently is what AT&T users are fretting about).
... and I saw Paul answer the question on Twitter too. I'm sure you can guess what the answer was...
I flashed the one with the radio update and everything seems to be fine.
Make sure you check the MD5 checksum, especially if you do the one with the radio update since a radio update could brick your device.
Yes, it does your BUT YOUR PHONE MUST BE ROOTED. I have an AT&T N1, which is rooted, and I downloaded the AT&T version at modaco and I'm currently running froyo. Loving it too.
Flash Paul's Pre-Rooted FroYo ROM & AT&T
Since it was said that flashing with the wrong radio could brick the phone I do not think it is fretting but a genuine safety check for a 500$ Device!
I did flash the full update with radio from Paul and I have no issue with the connection so far (wow so hard to say yes or no...)
So yes this rom work fine for me upgraded from cyanogen, now working into getting app2sd working (for some reason I get a PM not found)
Works fine WITH the radio included. Fret no more. Have AT&T version and did it earlier with no issues with the radio or any signal degradation.
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)
Hey guys,
I have a few questions about unrooting my HTC Legend, just in case. So I went to the thread "Easiest way to unroot HTC Legend" and it was a straight forward guide. I just have a few questions. The guide gives you a link to 1.03 software version, and 2.03 software version to unroot to, and all you have to do is reboot your phone while holding down the DOWN volume button. If I were to unroot (Just in case for emergencies) I would choose to roll back to 2.03 software. I'm on software 3.15 and was just wondering if this will roll back successfully to the stock ROM for 2.03? Will my stock ROM after unrooting be Android 2.1? Will my phone's radio version change? That I don't want at all. Just wondering because if for emergencies I need to unroot my phone then I need a stock ROM and software number that are out here in Canada, currently my phone has Froyo which isn't out for us yet. I wish I could put up a link but I can't, I was told before I'm not allowed to. But what I explained about the guide is everything you need to know just in case you don't. Thanks for the help guys.
I'm not sure about the firmware given in the guide, but those RUU files usualy contain radio too..It can be extracted from it, but I think that radio from froyo might not work with eclair rom you'd roll to...But as this is just in case, I think you have plenty of time to find out
Sent from my HTC Legend using XDA App
Actually the Froyo Rom I got didn't have another radio file in there, it kept the one I had with Eclair, so I'm sure it'll work. But what is a radio file do? I actually forgot to ask that, I always knew that it's needed but I actually don't like it when it gets changed, just because I was told if I flash the wrong radio, my phone will have problems. What happens when you change a radio file?
Anyway, there are versions of radios that do not work with certain ROMs and vice versa...
Radio image is an intermediate between android system and a GSM/CDMA/3G (phone) hardware...it is referred to as a RIL (Radio Interface Layer) it sort of acts like BIOS on PC, just between certain hardware and in your phone's software...
And yes, if you flash a wrong radio, you legend can act up like not being able to make a call or establish data connecttion, no wifi etc...
As Canada doesn't run GSM as far as I know, I'd be very carefull about radio firmware.(most radios here are WWE or Vodafone UK based and I'm not usre if it'll work out there )
You can check the zip files you update if they have radio update in them - easiest way is to remove the radio.img and re-sign them...
I actually used an RUU to root my phone that was WWE, with "Theunlockr.com" and it was used to downgrade. So I think WWE would work. If I use a Nandroid backup and something goes wrong such as wrong radio version, and restore the Nandroid backup, will everything go back to normal? If that's the case then there's not much problem in taking a risk. How do you know if the radio version if right for the mobile carrier though? I'm guessing that's the hard part of updating software? :/