Database Users

Downgrade the radio

Hey guys,
I've been searching all over the net and can't find anyone who's posted this problem yet, so here I go...
I have a rogers Dream and followed cyanogen's radio update guide (wiki.cyanogenmod.com/index.php/Upgrade_Rogers_Dream_Radio) to get Rogers off my back about the 911 update issue...
However, ever since I've updated my radio, I've been facing all sorts of problems on my phone, including instances where my data connection just stops working (although the 3g symbol is still on - and the only way to fix it is to either put my phone into airplane mode or restart it), or my fully charged battery might die overnight - which only started happening after I updated the radio.
My question is: does anybody have the old radio version (3.22.20.17) available for upload? I can't find it anywhere on the net.
I'm currently running the latest radio for rogers dream/magic devices (3.22.26.17)
Does anybody know of a way to fix this without having to downgrade my radio version?
thanks in advance!
-phatoush

[Q] Bluetooth asking permission for every file transfer from same PC

I paired my PC to Wildfire
everytime i transfer files from pc to mobile, my mobile asks permission for transfer, quite annoying. Bluetooth Incoming File Accept/Deny
can some1 pl help me with disabling bluetooth file transfer permission with a trusted PC
thanks in advance
kindly post reply if u knew the solution

isnt there any solution to this .. kindly help me solve this

Hi realxception,
I am also facing some problems related to Bluetooth in wildfire.
My wildfire configuration after rooting through unrevoked3 :
Firmware version
2.1 update 1
baseband version
13.45.55.24H_3.35.15.31
Kernel version
2.6.29-c9472fc1
[email protected]#1
Tue Aug 10 18:57:37 CST2010
Build Number
1.25.720.1 CL227575 release-keys
Software Number
1.25.720.1
Browser version
Webkit 3.1
-----------------------------------
First thing, after rooting, my a2dp is not working, means i cant hear music on my normal bluetooth headset, which I used to before rooting, though normal calling features are working through the bluetooth headset.
can you confirm if you had checked this thing on your piece before rooting.
Now I need to unroot back it stock image, so that I can take it to HTC for getting this problem checked.
And for bluetooth pairing, I suppose this is a shortcoming in android as a whole that even after pairing you have to click accept again and again.
I am from Delhi, can we get in touch on Mobile. : 09971777426

my firmware details are exactly same as urs.
i dont hv blue headset , so cant comment on its working. will try to test it n post results soon
currently am using bluetooth file transfer app or wifil explorer to upload or browse files...

hashimjamal said:
Hi realxception,
I am also facing some problems related to Bluetooth in wildfire.
My wildfire configuration after rooting through unrevoked3 :
Firmware version
2.1 update 1
baseband version
13.45.55.24H_3.35.15.31
Kernel version
2.6.29-c9472fc1
[email protected]#1
Tue Aug 10 18:57:37 CST2010
Build Number
1.25.720.1 CL227575 release-keys
Software Number
1.25.720.1
Browser version
Webkit 3.1
-----------------------------------
First thing, after rooting, my a2dp is not working, means i cant hear music on my normal bluetooth headset, which I used to before rooting, though normal calling features are working through the bluetooth headset.
can you confirm if you had checked this thing on your piece before rooting.
Now I need to unroot back it stock image, so that I can take it to HTC for getting this problem checked.
And for bluetooth pairing, I suppose this is a shortcoming in android as a whole that even after pairing you have to click accept again and again.
I am from Delhi, can we get in touch on Mobile. : 09971777426
Click to expand...
Click to collapse
I'm running the 1.37 rru and a2dp works

[Q] Baseband versions ?

Greetz all,
I've noticed there're different baseband versions, so far I've seen only two versions :
1.ending with 06
2.ending with 15
I haven't seen any reports of problems with particular version, on my device I have the v1, and it seems to work for all the roms.
If someone has info about this subj. please post in comments.
Also, if your baseband is neither 1 or 2 listed, please post complete baseband version and list of updates done to the phone.
I am not sure if this is the cause, but I still have a problem with voice quality over Bluetooth connection in a car.
The device in question is Becker Cascade Pro.
The sound is "bubbly" and very distorted, hardly usable.
I had this same problem with HTC Hero firmware 1.5, and it disappeared after upgrading to 2.1-r1, but in X8 the problem remains even on Gingerbread and any other roms.
Anybody has a similar problem?
Solutions ?

I think everyone's baseband begins with: "M76XX-TSNCJOLYM-53404xyz" <- yes, XX exactly, they don't represent something else, and last xyz are three numbers...
I have 015.
Updates: first flashed 1.6 FW when updating to 2.1 via deleting /system method.
Later, flashed 2.1 via FlashTool.
Then again some 1.6 and again 2.1, then updated via SEUS to latest 2.1.1.A.0.6
I think baseband is in amss files, because I've read somewhere that unlock solution could be patching amss - and simlock should be related to radio, right?

blagus said:
I think everyone's baseband begins with: "M76XX-TSNCJOLYM-53404xyz" <- yes, XX exactly, they don't represent something else, and last xyz are three numbers...
I have 015.
Updates: first flashed 1.6 FW when updating to 2.1 via deleting /system method.
Later, flashed 2.1 via FlashTool.
Then again some 1.6 and again 2.1, then updated via SEUS to latest 2.1.1.A.0.6
I think baseband is in amss files, because I've read somewhere that unlock solution could be patching amss - and simlock should be related to radio, right?
Click to expand...
Click to collapse
Thats little stupid idea.

as-mario said:
Thats little stupid idea.
Click to expand...
Click to collapse
Why? Right now I've checked, every baseband version DO begin as I said, and it's in related to AMSS, AMSS_FS, FOTA0, FOTA1 and KERNEL files.
And I'm uploading them for download, check in baseband collection thread

[Q] Bluetooth version : help needed

Hai guys,
I need some help. I searched and red allot, but I can't find the answer.
I'm on a HTC HD2 with Android version 2.3.4
I have a Parrot car kit (CK3000) that is not working with my current BT version with is V2.3.4 (No I can't update the firmware of the car kit. For that I need a cable and is expensive.)
When I install an old version of Android, like 2.1, my car kit is working just fine with my HD2 but as you all now earlier versions of Android have robot voices and other (minor) bugs.
So basically this is what I ask:
I need an APK or another way to downgrade the current BT version to for e.g. V2.1 or 2.2
Can somebody help?
Thanks.
Kind Regards, Diq

I have a Typhoon v3.3.9 (GB2.3.4 build) ROM and it works fine with my CK3100. You surely must update the parrot firmware. You don´t nee any cable. I update it with a bluetooth connection on a notebook.

Mponte,
As I said, I have a CK3000 and not the CK3100 like you.
The CK3000 is not upgradeable by Bluetooth like your CK3100.
I know for sure, not only because it's been written on the original Parrot website, but I also have tried it! And I'm not going to order a cable cause it's worth more than my old CK3000...
Again,
My question was about downgrading the BT version of my phone, not about the upgrade for my CK3000......

[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)