Howto downgrade radio-firmware 1.54.30.10 ??

[vollemaan]

Dear developers..
Is there a possibility that I can downgrade my radio firmware from 1.54.30.10 to let's say 1.54.01.00 or whatsoever?

I tried dozens of methods but non worked, spend 10+ hours on this forum.. none worked.

My specs:
Treo 750 unlocked
Windows Mobile 6 (previously 6.1 normal version)
Radio: 1.54.30.10 (Hermes one)
IPL 0.20
SPL 1.40
Netherlands / T-Mobile

And is it possible to rollback to the official Palm Bootloader? In case I have to send it in for repair.

Many many thanks in advance

[shortyboy]

Bump Im Stuck With This Shitty Radio!!help!!!tried Everything!!

[franta23]

I guess nobody knows (so far) how to downgrade from Hermes radio. I guess the only way is to directly flash via JTAG :( - if you can find the right pins in your Treo. I.e. something like the one discussed for Hermes in http://forum.xda-developers.com/showthread.php?t=391047

[tmknight]

There are a couple of threads going on about this now and some people have reported success, but I am a little skeptical (sorry mates) they were actually at this firmware level as I have yet to successfully downgrade my radio...spent hours flashing, reflashing various OS ROMs, radio ROMs, even made my own radio ROM extracted from ATT 2.25 update, via various bootloaders, SPL, and on and on. So I have given up and hope the official WM 6.1 update rumors come true and it contains a refresh radio and can actually over-write.

Having said this, I am pretty stable using 1.54.30.10 alongside the normal/generic WM 6.1 ROM

[NYITGUY]

i was able to downgrade my unlocked and hardspl'ed 750 from 1.54.30.10 to 1.54.07.00. i had to use the palm recovery tool that was extracted from Treo750_2_27_ROW_EN_DesktopUpdater.

there's a thread on it, but basically, ran the recovery tool, then flashed the 2.27 ROW EN update, then updated it with a radio-less 6.1 ROM. after the ROW update, the radio version was 1.54.07.00, which worked much better with ATT

[Merlyn_3D]

There are a couple of threads going on about this now and some people have reported success, but I am a little skeptical (sorry mates) they were actually at this firmware level as I have yet to successfully downgrade my radio...spent hours flashing, reflashing various OS ROMs, radio ROMs, even made my own radio ROM extracted from ATT 2.25 update, via various bootloaders, SPL, and on and on. So I have given up and hope the official WM 6.1 update rumors come true and it contains a refresh radio and can actually over-write.

Having said this, I am pretty stable using 1.54.30.10 alongside the normal/generic WM 6.1 ROM

What exactly is wrong with this radio? I like it better than the ATT WM6 one simply b/c I've had less issues and the earpiece is MUCH louder.

[NYITGUY]

What exactly is wrong with this radio? I like it better than the ATT WM6 one simply b/c I've had less issues and the earpiece is MUCH louder.

with ATT here in NYC, i had issues with 1.54.30.10-- it would drop the signal and a reboot would be needed to get it back. or if you went underground, and came back up, it would not grab a signal for a few minutes, i would have to turn the radio off then back on to get reception.
the problem went away with 1.54.07.00

[ericizzy1]

i was able to downgrade my unlocked and hardspl'ed 750 from 1.54.30.10 to 1.54.07.00. i had to use the palm recovery tool that was extracted from Treo750_2_27_ROW_EN_DesktopUpdater.

there's a thread on it, but basically, ran the recovery tool, then flashed the 2.27 ROW EN update, then updated it with a radio-less 6.1 ROM. after the ROW update, the radio version was 1.54.07.00, which worked much better with ATT

couple of questions:
bi differance from your old radio to the new one? where are you located on the at&t network?
if much better, can you give me a detailed step by step, with the right links?
thank you

[elohssanarerauoy]

i was able to downgrade my unlocked and hardspl'ed 750 from 1.54.30.10 to 1.54.07.00. i had to use the palm recovery tool that was extracted from Treo750_2_27_ROW_EN_DesktopUpdater.

there's a thread on it, but basically, ran the recovery tool, then flashed the 2.27 ROW EN update, then updated it with a radio-less 6.1 ROM. after the ROW update, the radio version was 1.54.07.00, which worked much better with ATT

That's crap! 2.27 ROW Radio version is 1.54.01.00:mad:

[tmknight]

i was able to downgrade my unlocked and hardspl'ed 750 from 1.54.30.10 to 1.54.07.00...

Not wanting or trying to get into a fray, but rather really trying to understand how you have succeeded where we have failed. I have tried your method to no avail. As I stated here and elsewhere I've tried throwing everything at this firmware/radio short of the kitchen sink. The reason this radio cannot be downgraded, as I understand it, is due to a "password" type issue. The available down-level firmware and the methods for accessing the firmware do not allow for the 1.54.30.10 firmware to be overwritten. I truly question the validity of the claim, not that I think you a liar, but rather that you actually had 1.54.30.10 firmware installed or that you have successfully overwritten. How are you determining that you had 1.54.30.10 installed? How are you determining that you have overwritten with a down-level firmware?

I doubt you will do this, and you certainly owe us nothing, but as a service to your XDA compatriots, how about you re-install 1.54.30.10 show us that you have it installed, then overwrite it. Screen shots would be lovely.

Again, this may come off as having attitude, but that is not intended. This is purely an academic challenge to help the rest of us understand how you have succeeded where the rest of us continue to fail.

Thanks in advance, cheers!

[NYITGUY]

Not wanting or trying to get into a fray, but rather really trying to understand how you have succeeded where we have failed. I have tried your method to no avail. As I stated here and elsewhere I've tried throwing everything at this firmware/radio short of the kitchen sink. The reason this radio cannot be downgraded, as I understand it, is due to a "password" type issue. The available down-level firmware and the methods for accessing the firmware do not allow for the 1.54.30.10 firmware to be overwritten. I truly question the validity of the claim, not that I think you a liar, but rather that you actually had 1.54.30.10 firmware installed or that you have successfully overwritten. How are you determining that you had 1.54.30.10 installed? How are you determining that you have overwritten with a down-level firmware?

I doubt you will do this, and you certainly owe us nothing, but as a service to your XDA compatriots, how about you re-install 1.54.30.10 show us that you have it installed, then overwrite it. Screen shots would be lovely.

Again, this may come off as having attitude, but that is not intended. This is purely an academic challenge to help the rest of us understand how you have succeeded where the rest of us continue to fail.

Thanks in advance, cheers!

....

i had flashed the different radio version via sd card. i actually bought a new treo when i realized i couldnt get it to revert down to an older version, and 1.54.30.10 was horrible with ATT in NYC. i would get on an elevator and lose service and have to cycle the radio to get service again

i wanted to sell the one of the treo 750s, but didnt want to stick the buyer with the crappy radio version. i tried the method someone else posted up and it worked, i was actually very surprised.

its sold and gone, working happily on att with the rom version i posted above.

the only thing i had done before the ill fated flash was to hard spl the device and sim unlock it.

i have no reason to make it up, i can assure you i was stuck on 1.54.30.10, as i went out and bought a new treo 750 to replace it when i couldnt get the radio flashed down. it was stuck as i had tried to reflash the radio SEVERAL times, both using the hermes flasher and the sd card method. it sat on my desk for a few months gathering dust.

i dont have a stake in this, as i actually dont even use the treo i have left anymore-- the second one that i never flashed to 1.54.30.10. i'm now using a kaiser.

all i can say is, i didnt think to take screenshots because why the heck would i make this up? the radio was stuck at 1.54.30.10. i simply followed another members instructions for the hell of it (i was about to rip it apart for spare parts) and lo and behold, the radio dropped to 1.54.07.00. sold it. done.

i wouldn't have bothered to waste the time to post my success if i had known i would have people calling me a liar. seriously? for what? bragging rights that i fixed my own screwup?

was your device hard-spl'ed before you flashed the 1.54.30.10 rom?

[PsyberEMT]

Also a no-go here with the URT. Tried MTTY. Even tried BRICKING the darned thing with MTTY, corrupting the OS and radio, and no luck, reflashes but the damned evil radio remains intact. Gone as far as flashing a kaiser radio then reflashing a cheetah radio...no luck. Anyone? Imma shoot this thing lol.

[ericizzy1]

Also a no-go here with the URT. Tried MTTY. Even tried BRICKING the darned thing with MTTY, corrupting the OS and radio, and no luck, reflashes but the damned evil radio remains intact. Gone as far as flashing a kaiser radio then reflashing a cheetah radio...no luck. Anyone? Imma shoot this thing lol.

same situation.
maybe we should upgrade to a newer radio rom? something that works better with at&t?
anyone?

[PsyberEMT]

Not even sure if there is a newer hermes radio out?

[tmknight]

....
i wouldn't have bothered to waste the time to post my success if i had known i would have people calling me a liar. seriously? for what? bragging rights that i fixed my own screwup?

It's amazing that you still cop to this when I SPECIFICALLY stated that was not what I was getting at...why do people WANT to feel as though they're being kicked?

Anyway...

From the relevant bits of your response, I have to believe your "success" in downgrade to lower version firmware was rooted in the fact that the firmware upgrade to 1.54.30.10 actually did not succeed. Sorry mate, this one's a dead end.

Still waiting for someone familiar with the firmware coding to step-up and help us out of this jam...Bueller?

[tmknight]

same situation.
maybe we should upgrade to a newer radio rom? something that works better with at&t?

That's my hope too, maybe the new WM6.1 ROM that we're promised :rolleyes: will have a newer radio that can overwrite this one.

[summiter]

My understanding of this problem is that the persistently present problem radio version in question has a bootloader that requires a main bootloader (SPL) which can do a sort of authentication handshake.

Essentially the radio bootloader says "hey, SPL, here's some numbers...what's your reply? And if I like your answer I'll allow new radio code to be flashed. If I don't like your answer or I don't get one, take a hike jackass". The Treo SPL can't respond to the radio as needed.

To my knowledge an SPL with this capability has never been released for the cheetah. Ages ago when this was a topic of interest, I was told that someone may be able to port a hermes bootloader over to the cheetah that runs and can at least allow for reverting the radio. The hermes and cheetah are very very similar, with most of the differences being in address locations and so forth and whatnot and what have you.

There's only a handful of folks 'round here who could port a hermes SPL, but unfortunately they don't have Treos and are thus likely not all that motivated. Donations may perk their ears, but the developer not having a device for live testing can be painful for all involved. I used my device as the test subject for Oli while he dev'd the unlocker and it took a lot of IMing code back and forth and describing test results to him. I'm surprised he had the patience really. I've been stuck with that locked hermes radio ever since and it's been bearable, but HSDPA throughput is not good.

The Palm support tool would not be able to overcome this particular issue.

Is there a large number of folks with stuck radios?

[Clarkie]

My understanding of this problem is that the persistently present problem radio version in question has a bootloader that requires a main bootloader (SPL) which can do a sort of authentication handshake.

Essentially the radio bootloader says "hey, SPL, here's some numbers...what's your reply? And if I like your answer I'll allow new radio code to be flashed. If I don't like your answer or I don't get one, take a hike jackass". The Treo SPL can't respond to the radio as needed.

To my knowledge an SPL with this capability has never been released for the cheetah. Ages ago when this was a topic of interest, I was told that someone may be able to port a hermes bootloader over to the cheetah that runs and can at least allow for reverting the radio. The hermes and cheetah are very very similar, with most of the differences being in address locations and so forth and whatnot and what have you.

There's only a handful of folks 'round here who could port a hermes SPL, but unfortunately they don't have Treos and are thus likely not all that motivated. Donations may perk their ears, but the developer not having a device for live testing can be painful for all involved. I used my device as the test subject for Oli while he dev'd the unlocker and it took a lot of IMing code back and forth and describing test results to him. I'm surprised he had the patience really. I've been stuck with that locked hermes radio ever since and it's been bearable, but HSDPA throughput is not good.

The Palm support tool would not be able to overcome this particular issue.

Is there a large number of folks with stuck radios?

Hi Summiter

Yes, I think there are a relatively large number of people stuck with it, judging by the threads I've been following in the hope that someone finds a solution. Whether it's enough people to motivate Oli or one of the other gurus is not certain though.

My device has better BT connectivity and louder speaker volume, but dumps most of my calls whenever the signal goes below 2 bars. Very upsetting for me and frustrating those at the other end.

It'd be great to get out of this jam - serves me right for playing with 'cooked' ROMs and such - but I love what these people do on XDA-Dev, and can't help but wanting to join the party.

Anyway, for this problem I'm almost resigned to junking the 750, and getting another device - maybe an HP 914c or a Treo 850 when they come out. I love my 750, but it's getting to be a real issue for me.

[tmknight]

From posts here and other sites there appears to be a large number of 1.54.30.10 radios on Treo's. Though there appears to be a divide in those that feel it works fine vs those who know it does have issues. With that however, I feel the new devices on the horizon will soon make this discussion moot.

[awojtas]

I've had a really bad time with 1.54.30.10. Lots of dropped calls, crashed radio etc.
So many times I had to turn radio off then on to make a call.
GPRS would sometimes show connected but not transfer any data and it would need to be disconnected then reconnected.
Also, battery life was worse than before (I didn't think that was possible, Treo is so bad already).

I don't have time to try all the options listed above for returning to an older Radio so instead I'm trying the new Hermes Radio ROM: 1.56.70.11

I'll give it a couple of days then report back. Other Hermes users are reporting pretty bad battery life with it - but if the radio is more stable I'll stick with it.

If you want to try it yourself, the file name is
HERM_Radio_Only_1.56.70.11_CustomRUU

It was rock solid (for Windows Mobile, that is) on the 1.54.07 and older Radios.

I'm on Vodafone New Zealand by the way which is a 900/1800Mhz GSM, 2100Mhz 3G HSDPA network. We should be listing network frequencies here -- some Radio ROMs might be better or worse on particular frequencies.

[paypalbid]

I've had a really bad time with 1.54.30.10. Lots of dropped calls, crashed radio etc.
So many times I had to turn radio off then on to make a call.
GPRS would sometimes show connected but not transfer any data and it would need to be disconnected then reconnected.
Also, battery life was worse than before (I didn't think that was possible, Treo is so bad already).

I don't have time to try all the options listed above for returning to an older Radio so instead I'm trying the new Hermes Radio ROM: 1.56.70.11

I'll give it a couple of days then report back. Other Hermes users are reporting pretty bad battery life with it - but if the radio is more stable I'll stick with it.

If you want to try it yourself, the file name is
HERM_Radio_Only_1.56.70.11_CustomRUU

It was rock solid (for Windows Mobile, that is) on the 1.54.07 and older Radios.

I'm on Vodafone New Zealand by the way which is a 900/1800Mhz GSM, 2100Mhz 3G HSDPA network. We should be listing network frequencies here -- some Radio ROMs might be better or worse on particular frequencies.

i installed the new radio and it said successful but did not show the newer radio version under the display

[paypalbid]

Not that I have any problems with the 1.54.30.10 radio, however I did try to change it to verify some statements in this thread.

Anyway I had no success changing radio version vid SD card method. I attempted to change to radio version 1.54.07.00 and 1.56.70.11 and both time the process said update success. When I look under setting to see what my radio version is and it is still 1.54.30.10

Now I have tried other stuff as well such as unlocking spl again with Olipro programs.

The only thing I havent tried is downgrade the SPL lower than 1.40 to and reattempt to change the radio version.

Anyway I have been using 1.54.30.10 radio for a while now probably 8 months and it works fine. Nice quality call and loud no drop calls.

Now here is where I believe the flaws come in. If you live in an area with old crappy cell sites with radio may drop calls and that is about it. I travel quite a bit up and down California and notice all the old crappy inland cities is where this readio vesion struggles. Anyway its still not that bad as some are reporting. It a good working radio. if you guys have used the HTC devices like the MDA or 8125 man you dont even know what bad radio versions are. Try not having signal for 5 minutes after coming out of a dead zone and your device never get great signal compare to the crappy free phones.

[awojtas]

I've been using the Hermes 1.56 radio for several days now. It is fantastic!

Problems solved:
- Much faster finding network, only a couple of seconds between flight mode on or off now
- Data connections don't time out (and have to be disconnected then reconnected)
- No dropped phone calls
- Switching between simultaneous phone calls reliable
- Placing someone on hold works every time now
- Great coverage, and holds onto calls even at barely 1 bar of signal.

Problems NOT solved:
- This radio eats batteries like weetbix. My phone used to last a whole day, now by 4pm it's flat.

My radio version in the "Phone" tab from "About" screen has NOT updated to show this new version.
But I have noticed the difference so dramatically, that it must have updated.

[paypalbid]

I've been using the Hermes 1.56 radio for several days now. It is fantastic!

Problems solved:
- Much faster finding network, only a couple of seconds between flight mode on or off now
- Data connections don't time out (and have to be disconnected then reconnected)
- No dropped phone calls
- Switching between simultaneous phone calls reliable
- Placing someone on hold works every time now
- Great coverage, and holds onto calls even at barely 1 bar of signal.

Problems NOT solved:
- This radio eats batteries like weetbix. My phone used to last a whole day, now by 4pm it's flat.

My radio version in the "Phone" tab from "About" screen has NOT updated to show this new version.
But I have noticed the difference so dramatically, that it must have updated.

If it doesn't show then it hasnt been updated. Is that a fair assumption ?

[awojtas]

Yeah I'd normally completely agree, but the difference in radio has been like night/day.

If it hasn't updated completely, then something has changed. I didn't hard reset after upgrading the radio rom, and nothing else has changed.

Is there some way to test exactly what version radio ROM it's running otherwise?

[paypalbid]

Yeah I'd normally completely agree, but the difference in radio has been like night/day.

If it hasn't updated completely, then something has changed. I didn't hard reset after upgrading the radio rom, and nothing else has changed.

Is there some way to test exactly what version radio ROM it's running otherwise?

no there isnt a way that im aware that you can check the radio version other than checking under Settings>System>About>Phone

Well please do report back of your findings and experience. please do write about certain locations you experience problems and now improved. That way people wont think its a placebo effect you have.

i have upgraded this new radio also and as mentioned the new radio version did not show.

i will report back my findings too as they developes.

if you are experiencing better result then that is all that matters. i did the sd card upgrade method and it showed GSM upgrade completed and update sucessful.

[awojtas]

I'm hoping it's not the placebo effect also. I have now had a couple of incoming dropped calls but I loaded Worldmate on recently which has made my phone run very slowly, so I think that could have contributed to that.

I am concerned the radio rom version hasn't updated in software, it'd be great to be able to check it.

[treo927]

Not possible to install the new version via Hard SPL? Btw, can some point me the link to this new Radio? Thanks!

[paypalbid]

i believe i tried the hard spl method and gave me some error so I just went with the SD Method.

here it the link to the radio: http://www.mediafire.com/?2ms0vu4mb1d

[treo927]

i believe i tried the hard spl method and gave me some error so I just went with the SD Method.

here it the link to the radio: http://www.mediafire.com/?2ms0vu4mb1d

Thanks and yup youre right. In the end I installed using the SD Card method too.

My initial observations is that it seems to be more unstable that 1.54.30.10 with dropped calls and 3G issues. Will monitor for the whole week to see if its worth keeping.

[DAFTEK]

I have tried every possible way recommended on XDA with no luck of changing the radio to any version for that matter, this radio is junk, constant lost calls and phone freezes to the point of wanting to throw it out the window. Unless someone comes up with a way of changing the radio on these phones im back to my old Herms or might just take the plunge and get a new iphone or something that can do exchange...

Come on guys lets figure this out :(

[vollemaan]

Well... I believe my GSM radio died because of radio version 1.54.30.10...
When I get a 3G connection (UMTS / HSDPA) I have reception and I can make calls etc.. but when selecting "GSM only" it won't find any network.

[awojtas]

It was placebo effect. (or perhaps, flashing the radio ROM again flushes out old info and makes it run better) -- my calls dropped more and more and now it's back to the nasty 1.54.30.10 symptoms.

I miss so many calls, emails and txts every day. If I do receive the txt, typically it's delayed massively. Unless this is solved it'll be time to dust off the blackberry pearl...

[awojtas]

We should post what we *have* tried, so as to save other people wasting their time.

Note "OK" means the upgrade completed, not that it changed the radio rom version.
I am also hard resetting after every upgrade.

Via USB
---
1.56 hermes radio rom OK

Via SD
---
Radio ROM from Treo750v_Recovery_Tool (found in %temp% folder) OK
Radio ROM as above, minus SPL (removed using Dutty's NBH tool) OK
2.30 Vodafone NZ ROW WM6 Upgrade OK

[jcrompton]

We should post what we *have* tried, so as to save other people wasting their time.

Note "OK" means the upgrade completed, not that it changed the radio rom version.
I am also hard resetting after every upgrade.

Via USB
---
1.56 hermes radio rom OK

Via SD
---
Radio ROM from Treo750v_Recovery_Tool (found in %temp% folder) OK
Radio ROM as above, minus SPL (removed using Dutty's NBH tool) OK
2.30 Vodafone NZ ROW WM6 Upgrade OK

Guys I have a similar but slightly reverse situation. I upgraded to Radio Version 1.56.70.11 right after flashing 6.1 ROM. I have had some issues with the radio - it stayed connected but the other party would intermittently not be able to hear me. So Downgraded to a 1.47 Radio - I got an "Update Success" indication with the SD method. If I look in to Settings / About / Phone - my radio is still listed as 1.56.70.11 BUT I am absilutely sure that the radio is diffferent!

Just something to add to the equation


PS CAN SOMEONE CONFIRM to me what Radio version is on the Treo 750 if you use the Palm Updater for AT&T to Windows Mobile 6.0 ???

Thanks

[awojtas]

Hi mate, your radio is not changed, you are stuck on 1.56. Sorry.

I also made the same mistake -- it is just after flashing the radio rom, performance improves slightly. It will be back to dropping calls and all the nasties soon enough.

Join us in trying to find a way to downgrade... Kaiser users had the same issue which is now solved: http://forum.xda-developers.com/showthread.php?t=393337&page=7

Users having the issue:
- Cheetah (Treo 750)
- Hermes
- Breeze smartphone (e.g. i-mate SPJAS)
(all these devices use same radio rom)
Solved:
- Kaiser
- Tilt

[jcrompton]

Hi mate, your radio is not changed, you are stuck on 1.56. Sorry.

I also made the same mistake -- it is just after flashing the radio rom, performance improves slightly. It will be back to dropping calls and all the nasties soon enough.

Join us in trying to find a way to downgrade... Kaiser users had the same issue which is now solved: http://forum.xda-developers.com/showthread.php?t=393337&page=7

Users having the issue:
- Cheetah (Treo 750)
- Hermes
- Breeze smartphone (e.g. i-mate SPJAS)
(all these devices use same radio rom)
Solved:
- Kaiser
- Tilt


I am very much aware of the Kaiser issue - I carried the Kaiser for almost the last year and probably flashed a hundred ROMs. The main difference being that the problem was with only one radio.
Here we seem to be talking about two or more that can't be changed.

I still am greatly suspicous that the OS is not reporting the Radio version correctly. I am not aware of anyway to see the Radio version during boot - which I would trust alot more.

Any idea who might be working on this issue -- it took a lot of really smart and experienced people to solve the Kaiser issue !!!

[paypalbid]

I am very much aware of the Kaiser issue - I carried the Kaiser for almost the last year and probably flashed a hundred ROMs. The main difference being that the problem was with only one radio.
Here we seem to be talking about two or more that can't be changed.

I still am greatly suspicous that the OS is not reporting the Radio version correctly. I am not aware of anyway to see the Radio version during boot - which I would trust alot more.

Any idea who might be working on this issue -- it took a lot of really smart and experienced people to solve the Kaiser issue !!!

I believe u are correct.

[awojtas]

I also thought it was not reporting Radio version correctly. But I flashed Radio from WM5, which did not support HSDPA, yet I still could connect via HSDPA.

I agree it would be great to find a way to report Radio ROM version outside of the built-in "About" screen, as verification.

The 2 (or more) radio ROMs not allowing downgrade are both from Hermes. There must be something different in that 1.54.30.10.

[startngate]

Guys I have a similar but slightly reverse situation. I upgraded to Radio Version 1.56.70.11 right after flashing 6.1 ROM. I have had some issues with the radio - it stayed connected but the other party would intermittently not be able to hear me. So Downgraded to a 1.47 Radio - I got an "Update Success" indication with the SD method. If I look in to Settings / About / Phone - my radio is still listed as 1.56.70.11 BUT I am absilutely sure that the radio is diffferent!

Just something to add to the equation


PS CAN SOMEONE CONFIRM to me what Radio version is on the Treo 750 if you use the Palm Updater for AT&T to Windows Mobile 6.0 ???

Thanks

The radio is 1.54.27.00 if you used 2_25_ATT

[jcrompton]

I still think we have to know for sure what radio version is present before we can even begin to solve this problem.
My phone reports Firmware Version 1.56.70.11 after I installed the 6.1 ROM and then upgraded the Radio to 1.56.70.11

I then had realtively poor performance so I successfully ( ??? ) did a Radio downgrade to 1.47.30.20

There is ABSOLUTELY no doubt after using the phone all day today that there was great and very noticable improvement in call quality, performance (got 900 kbps 3G speed this AM, no dropped calls and slightly better battery performance (I still over 50% battery at 10:30 PM !!)

I just can't believe the Radio wasn't changed.

On my Kaiser there is a place that more clearly reports the ROM version as compared to the Radio version -- in the Treo it lists "Firmware Version"

Just more discussion


PS Has anyone asked (i.e, via PM or something) the guys that solved the non changable "Radio of Death" for the Kaiser ??

[paypalbid]

If you are experiencing better result then that is all that matters.

[awojtas]

I have tried to find out using AT Commands to report radio version but no joy.
Seems like every radio command is blocked.

If someone else wants to have a go, here's what I did (pretty basic):
- Pair with Bluetooth on PC
- Allow access to Serial Port on phone in the pairing options (where you select "headset", etc)
- Find out Bluetooth Modem's COM Port (mine was COM45, found from device manager under "Bluetooth Modem")
- Open HyperTerminal and select COM45 directly (not "Bluetooth Modem"), don't enter any numbers to dial
- Press Enter, you should see a prompt and "Connected" in the bottom status bar
- Type "ATZ", you should receive "OK".

AT Commands: http://wiki.xda-developers.com/index.php?pagename=HTC_GSM

The commands for general info worked. But nothing in the top section or for radio info. I could get the IMEI number of phone but no radio version.