Related
Any of you 8125 owners who installed the imate 2.16.9.101 release have any new feedback on how it's going? Are there still issues with the connection icons or wifi connectivity?
I'm eager to get push mail working and have not been able to get a straight answer from a dozen different folks at Cingular on when their release will come out...so I might give the imate release a shot.
What about going back to the shipping Cingular version after installing the imate update - is it easy/possible? Any problems with extended ROM?
thx
I never even used the phone with the original cingular firmware, I went directly to the Q-tek Test rom. From that rom to this rom, the radios seem a little better (getting better signal, edge seems slightly faster, wifi picks up network much faster) and for some reason the whole feel is "snappier" seems like the menus and such load faster. I haven't had any stability issues, and push is working perfect.
I dont' know about the much faster part, but mine is very stable since i removed battery pack pro. I have SPB's power plus as well as their weather software.
if there are any software you want tested just let me know. Well if I can atleast run it without having to buy it, (i.e. Demos, etc.)
Bluetooth, Wifi, Edge, and signal are all real good. (signal on par with 1.12 radio as well as faster to get a signal than it was)
Battery icon is NOT on the bottom and does NOT show more than 2 bars ( so you have full, somewhere in between, and low).
Battery life seems pretty good, but I can't compare it to any other version as I had the phone 36 hours before I upgraded it to this version.
Great thanks for the feedback yall. So once I do the upgrade, how hard will it be to go back to the shipped version if I ever need to? I have everything backed up using awizard, but I understand there could be problems trying to go to a previous version. I think downgrading via the bootloader mode requires executable rom images, but there isn't one available for the shipping version.
You can still downgrade to an old imate ROM and then use aWizard to restore your cingular ROM.
I have installed it on my Qtek 9100.
I hanged 5 times in 2 days.
What is more annoying is when it hangs and
someone tries to call me at the same time, the
other party hears my phone ringing, but my
Qtek is dead silent.
ethorn said:
I dont' know about the much faster part, but mine is very stable since i removed battery pack pro. I have SPB's power plus as well as their weather software.
if there are any software you want tested just let me know. Well if I can atleast run it without having to buy it, (i.e. Demos, etc.)
Bluetooth, Wifi, Edge, and signal are all real good. (signal on par with 1.12 radio as well as faster to get a signal than it was)
Battery icon is NOT on the bottom and does NOT show more than 2 bars ( so you have full, somewhere in between, and low).
Battery life seems pretty good, but I can't compare it to any other version as I had the phone 36 hours before I upgraded it to this version.
Click to expand...
Click to collapse
Is your wifi working OK? If so, did you install any of the cingular exrom customizations?
Just curious, because I installed the released imate rom and everything is working like a champ except wifi. I installed some of the original customizations from the cingular exrom and I wonder if one of those cabs did something to the wifi config...
What kind of porblems are you having with the wifi?
nickcerda said:
What kind of porblems are you having with the wifi?
Click to expand...
Click to collapse
It won't turn on.. =)
I thought perhaps it was one of the cingular customization cabs I installed from the original exrom, but now I'm not so sure. I looked at all the cabs and the only one that relates to wifi is the cab that sets the key to enable talking to 802.11g APs.
In comm manager, if I click the wifi icon, it appears to attempt to start wifi, but then goes back to an "x" over the wifi button. The wifi radio doesn't start and the left LED that blinks when wifi is on does not come on.
I wish there were some logs to look at on this thing to see why it's failing to start wifi..
Solved the wifi problem. It appears to be related to something in one of the original 8125 exrom cabs. I reinstalled the new imate rom, skipped the imate exrom install, and only installed a couple cabs from the 8125 exrom. The cabs I installed that did not affect wifi were the mms config, the gprs account config, and the edge icon.
All is now well. If I had the time and patience I'd tear apart the original 8125 cabs to see which one might cause wifi probs, but at this point it's not necessary.
I'll stick with it as-is now until cingular releases their own update...assuming that happens before the hermes is out.. =)
I have a Dopod 838 (identical to 8125, I suppose). The new ROM has worked awesome for me. Better in every way. Even the infamous Activesyn problem went away
I am getting ready to take the plunge...just in case...
does anyone have the original 8125 ROM?
I use SPB backup can restore a backup after I upgrade?
I installed this rom on my 9100, and it is much better than it was with any of the other roms including the original shipped rom!
The radio is much clearer and the wifi hooks up faster and runs better, and I have had absolutely NO lock ups at all.
Later
I am thinking of installing it on an 8125...
Without a backup 'known good' ROM to revert back to I am cautious
summiter said:
Solved the wifi problem. It appears to be related to something in one of the original 8125 exrom cabs. I reinstalled the new imate rom, skipped the imate exrom install, and only installed a couple cabs from the 8125 exrom. The cabs I installed that did not affect wifi were the mms config, the gprs account config, and the edge icon.
All is now well. If I had the time and patience I'd tear apart the original 8125 cabs to see which one might cause wifi probs, but at this point it's not necessary.
I'll stick with it as-is now until cingular releases their own update...assuming that happens before the hermes is out.. =)
Click to expand...
Click to collapse
I added the extROM files one by one to see which one caused the wifi issue and it was Signed-gprsstall_128.sa.cab...so far. It was only the third one in a series of 17. I'll see what happens when I add the rest. This cab file moves a radio.dll file around.
I've installed this ROM on 2 8125's. Much better and faster than Cingular's ROM. The only thing I did was to install the Cingulcustomize_No_Emails.cab, Microsoft Voice and TRE Pocket PC registry editor and remove all traces of the Voice Command. WiFi connects to my secured access point flawlessly (though I never use WiFi) and the AKU2 push email typically has my emails coming in in about 8-10 seconds from my Exchange 2003 server. Very infrequent lockups, much less than any other ROM I've installed.
Just my two cents worth ...
Steven
ROM version: 2.16.9.1 WWE
ROM date: 2/6/06
Radio version: 02.07.10
Protocol version: 413.1.03
ExtROM version: 2.16.9.101
Cingulcustomize_No_Emails.cab
What does that cab do?
nickcerda said:
Cingulcustomize_No_Emails.cab
What does that cab do?
Click to expand...
Click to collapse
the one thing I see is it sets up the GPRS settings for data connection ... you do not need it to make phone calls or use Wifi
Step by step to 2.16
I have a cingular 8125. I'm no stranger to flashing roms, I had a SX66 that was running WM5 and I reloladed it all the time. I'd like to see a step by step guide for unlocking the ext rom, flashing the radio and system roms for the 8125. Anyone know a post with that info in it?
Thanks!
Re: Step by step to 2.16
dmelton75 said:
I have a cingular 8125. I'm no stranger to flashing roms, I had a SX66 that was running WM5 and I reloladed it all the time. I'd like to see a step by step guide for unlocking the ext rom, flashing the radio and system roms for the 8125. Anyone know a post with that info in it?
Thanks!
Click to expand...
Click to collapse
Interesting you say you're no stranger to flashing ROMs but then ask for a step by step.
It's laid out quite well in several topics, but basically:
-Use awizard and enable rapi
-Use awizard and CID unlock
-Use awizard to back up Extrom, radio, splash, os
-Run the executable RUU installer for the imate
-On first boot, as soon as you get prompted to choose a carrier, do a soft reset to prevent the imate ext rom stuff from loading
-Install desired customization items from your backed up cingular ext rom. Any of them can be installed EXCPET the gprsstall cab - it will kill your wifi.
There is currently no way to unlock the ext rom in the lates imate upgrade, so you're stuck with what's in there, but you don't have to let it install.
Finally a new rom for us vario owners!
http://t-mobile.iris-global.com/download_manager_mda_vario.html
Does anyone have a changelog?
i am uploading it to the ftp site
has anyone installed it yet?
Guys let us all know your findings with this rom please
I looked at it. Here's the stats:
OS 5.1.195 (Build 14847.2.0.0) (AKU 2.0)
Radio 02.19.11
IPL/SPL 2.21
Ext ROM 2.21.2.109
Protocol 4.1.13.09
ROM build date 3/9/06
yawn.
=)
t-mobile rom
it look like dopod and tmobille are using same rom and radio .
summiter said:
I looked at it. Here's the stats:
OS 5.1.195 (Build 14847.2.0.0) (AKU 2.0)
Radio 02.19.11
IPL/SPL 2.21
Ext ROM 2.21.2.109
Protocol 4.1.13.09
ROM build date 3/9/06
yawn.
=)
Click to expand...
Click to collapse
Oh well it shouldn't come as much of a surprise really, but it would of be nice to get something different.
deadmetal said:
Finally a new rom for us vario owners!
http://t-mobile.iris-global.com/download_manager_mda_vario.html
Does anyone have a changelog?
Click to expand...
Click to collapse
Looks like the same ROM that was leaked a few days ago. This contains the same Ext ROM that I used to create the Mr. Clean AKU 2.3 T-Mobile UK ROM.
I've not yet tried upgrading the ROM on my UK Vario, but I guess now is the time to think about it. I want to keep my stored SMS and MMS messages, but everything else on the machine I'll probably clean-install and re-tweak as necessary once I get the new ROM flashed. I've got a good idea of what I do and don't want in my Vario after 5 months use, and I guess now would be a great time to get rid of all the junk that's probably clogging up the registry by now.
A couple of questions:
I know I can make a backup copy of the current ROM onto a clean SD card, but can I back it up onto a partially used card (i.e. using the file system, rather than raw data blocks).
I backup my Vario regularly using SPB Backup. Can the SPB Restore utility restore just my SMS/MMS messages (including user-created folders) without reinstalling anything else, so I can keep a nice clean machine?
The UK T-Mobile release is 2.0, whereas "Mr Clean ROM" is 2.3. I'm guessing 2.3 is better, but what am I likely to lose (if anything) that's on the T-Mobile ROM? Is the stereo bluetooth headset facility on both? I've already removed most of the obvious T-Mobile pink stuff, and put in a better dialler skin, etc. In fact, I don't really want T-Mobile's dialler skin at all, as I've been trying to get rid of their modified history & speeddial icons for ages!
Finally, what about reinstalling things like TomTom - will doing so remove my user-defined favourite place settings, etc? (my maps are stored on SD card)
Thanks for any advice, I'm a little nervous here...
Andre
^^^ Same questions and concerns for me.
Also, I flashed my T-Mobile UK MDA from original ROM to Qtek 2.17 ROM a month ago. I SIM & CID unlocked it in the process using Lokiwiz 0.2b - do I need to prep the phone with Lokiwiz 0.3 before flashing the MDA to keep it unlocked?
Cheers in advance.
deadmetal said:
Finally a new rom for us vario owners!
http://t-mobile.iris-global.com/download_manager_mda_vario.html
Does anyone have a changelog?
Click to expand...
Click to collapse
Things I've noticed so far:
1)
The Comms screen has been radically changed, adding a "push" button (deactivated on my uk t-mobile vario for some reason) and another button that looks like a ppc to ppc connection.
2)
The battery icon has moved from the bottom right corner to the top right corner, on the top panel, (where the time used to be) and has turned an ugly shade of green. I presume it goes yellow -> red when on low power.
3)
In the programs, something called "SAP Settings" has been added.
It's used for remote sim access apparently.
4)
"Running Programs" is now a program and can be seen on the start menu
6)
"Comm manager is now a program that appears on the "running programs" list.
5)
When starting up, it displays the t-mobile screen followed by the WINDOWS MOBILE screen instead of just the t-mobile screen.
Finally, this could because of a cleaner registry and stuff, but it does feel somewhat more efficient.
So would the early adopters say it is better or worse than the mighty summiter/Mr Clean (Uk) versions
Bhayani
Right now I like the Mr Clean version better, but I only had that on for a weekend and the new one has only been on for an hour or so.
Personally after a day with it I'm tempted to go back to the qtek 2.17 rom
Hi can someone post up the MMS settings as I didn't note them down when I updated the rom - doh! UK of course.
arf said:
Personally after a day with it I'm tempted to go back to the qtek 2.17 rom
Click to expand...
Click to collapse
Thats interesting.... Im using a Qtek 2.17 ROM at the moment and am considering upgrading, but Im holding back at the moment. What dont you like?
Bad news here. I've been running the Mr Clean Comes to London ROM for a few days with no problems at all and before that one of the Qtek ones and the unit never reset itself which it had ben doing with the T-Mobile ROM from the start of the year. I am happy with the performance of the new T-Mobile ROM after installing it yesterday but overnight it went back to soft resetting itself as all of my open programs were shut down this morning. Also when I turned it on the screen wasn't responding so I ended up doing another reset.
I'll leave it over the weekend but it looks like the spontaneous reset problem hasn't been resolved. Strange that T-Mobile can't fix that but all the other ROMs seem to have it licked!
leigho said:
Strange that T-Mobile can't fix that but all the other ROMs seem to have it licked!
Click to expand...
Click to collapse
Of course it could be something T-Mobile has put in that's causing it. I'm thinking Mr Clean is the way to go...
Andre
Over at Howard Forums / T-Mobile MDA/SDA page, chesney09 posted the soon to be release MDA ROM update....
http://www.howardforums.com/showthread.php?t=965690&page=1&pp=15
--------------------------------------------------------------------------------
Hey All..
Many of you played with the 2.24 BETA ROM I had shared a couple months ago...
Well.. in keeping my consistency... Here is the SHIP ROM 2.26. This has the MSFP, Improved radio and bugs fixed.
Hope it helps the hopeless MDA users..
________________________________________________________
i have been waiting.... can't wait much longer
Would be nice if someone could upload it to xda.
I tried getting it up on the ftp but it didn't work.....so i just put it up on my site...
http://www.lvlolvlo.net/?p=32
enjoy...
lvlolvlo said:
I tried getting it up on the ftp but it didn't work.....so i just put it up on my site...
http://www.lvlolvlo.net/?p=32
enjoy...
Click to expand...
Click to collapse
Your page must be getting hits like crazy about now! :lol: Won't even load the page let alone download the file.
oh crap....
i hope'd people who could access rapidshare would use rapidshare....and those who couldn't access rapidshare woul use my link....but i guess that's not the case.....
but so far not too bad...just under 1gb served....file size ~55MB so....
I think a lot of people hate rapidshare. I know I do. I'll put up with it if I need to, but if there's an alternative, screw 'em.
But thanks for the file...I'm gonna check it out later.
dkb218 said:
Over at Howard Forums / T-Mobile MDA/SDA page, chesney09 posted the soon to be release MDA ROM update....
http://www.howardforums.com/showthread.php?t=965690&page=1&pp=15
--------------------------------------------------------------------------------
Hey All..
Many of you played with the 2.24 BETA ROM I had shared a couple months ago...
Well.. in keeping my consistency... Here is the SHIP ROM 2.26. This has the MSFP, Improved radio and bugs fixed.
Hope it helps the hopeless MDA users..
________________________________________________________
Click to expand...
Click to collapse
Unluckily they removed the Intent MIDlet manager but i was able to extract it from the 2.24 and i'll post it as a cab tomorrow morning.
Ok, so like I did the SIM/CID unlock when I loaded up 2.17.
I recall something about the unlocking utility used wouldn't hold once you got past the 2.17 ROM [going from 2.17 to 2.24, etc.]
Is there another unlocking utility I need in order to upgrade to 2.26?
UPDATE:
Did the update...Now restoring back-up...
I uploaded it to the xda-dev ftp:
ftp://xda:[email protected]/Up...Mobile_US_226102_22610105_022511_WWE_Ship.exe
Can anyone confim the version numbers for the IPL/SPL & Radio Rom?
Also can you confirm that it is AKU 2.3?
Thanks
kyphur said:
I uploaded it to the xda-dev ftp:
ftp://xda:[email protected]/Up...Mobile_US_226102_22610105_022511_WWE_Ship.exe
Can anyone confim the version numbers for the IPL/SPL & Radio Rom?
Also can you confirm that it is AKU 2.3?
Thanks
Click to expand...
Click to collapse
I have installed it this evening and it works great so far!
IPL: 2.26
SPL: 2.26
ROM version: 2.26.10.2
ROM date: 6/7/06
Radio Version: 2.25.11
Protocol Version: 4.1.13.12
OS Build version: 14955.2.3.0
kyphur said:
Can anyone confim the version numbers for the IPL/SPL & Radio Rom?
Also can you confirm that it is AKU 2.3?
Thanks
Click to expand...
Click to collapse
IPL 2.26
SPL 2.26
GSM 2.25.11
OS 2.26.10.2
Phone Dial Pad...
This ROM is working great for me. It fixed my one big problem with the 2.24 ROM, which was the phone time never being correct. I have one issue, though...
When I first start the device and it prompts me for the password on my SIM, I get the nice blue phone dialing screen I'm used to (from the 2.24 ROM). But whenever I access the phone after that, I get a far less pretty T-Mobile dial screen (it's in pink and grey...ick). Anyone else have this issue? Any ideas how to fix?
Thanks,
Manzil
I just installed this and I must say that the screens just pop out at me right off the bat without applying any spped registry tweeks, overclocking, etc.
I'm installing my essential Cingular mods tonight and will kick the tires tomorrow.
Sumitter, looking foward to your work on this! (If it passes muster ... )
Re: Phone Dial Pad...
Manzil said:
This ROM is working great for me. It fixed my one big problem with the 2.24 ROM, which was the phone time never being correct. I have one issue, though...
When I first start the device and it prompts me for the password on my SIM, I get the nice blue phone dialing screen I'm used to (from the 2.24 ROM). But whenever I access the phone after that, I get a far less pretty T-Mobile dial screen (it's in pink and grey...ick). Anyone else have this issue? Any ideas how to fix?
Thanks,
Manzil
Click to expand...
Click to collapse
Change to the windows default theme instead of the tmobile theme...I think it's under settings, today...
It does seem to be working quite well for me, also. It's not displaying any of the problems I had with roms after 2.17 and it was reasonably fast even before the usual improvements were added. The T-Zones Today item is kinda worthless, IMO, and the Comm Manager doesn't add a lot but it's at least easier to understand at a glance. All in all, a decent update.
Anybody use O2 miniS?Are there any prolem with symbol(when press blue dot) when you use this ROM.When i use 2.24,the symbol text isn't suit with keyboard!
Re: Phone Dial Pad...
That didn't work. In fact, I did a hard reset of the device, changed theme to Windows default, and everything is blue -- except the phone dial pad which stays with the "T-Mobile look". The funny thing is that when I first turn on the phone radio (not the device itself, but the phone) I am prompted to enter my PIN code for my SIM. This dial pad is the nice blue 3-d dial pad. But every other time I get to the phone dial pad, it's the ugly T-mobile "flat" looking one in pink and grey...
It can't just me be!
Manzil
famewolf said:
Manzil said:
This ROM is working great for me. It fixed my one big problem with the 2.24 ROM, which was the phone time never being correct. I have one issue, though...
When I first start the device and it prompts me for the password on my SIM, I get the nice blue phone dialing screen I'm used to (from the 2.24 ROM). But whenever I access the phone after that, I get a far less pretty T-Mobile dial screen (it's in pink and grey...ick). Anyone else have this issue? Any ideas how to fix?
Thanks,
Manzil
Click to expand...
Click to collapse
Change to the windows default theme instead of the tmobile theme...I think it's under settings, today...
Click to expand...
Click to collapse
To disable dialpad skin (T-Mobile) and use default change HKLM\Security\Phone\Skin\Enabled to 0
zoki said:
To disable dialpad skin (T-Mobile) and use default change HKLM\Security\Phone\Skin\Enabled to 0
Click to expand...
Click to collapse
Thank you! I hate to sound obtuse, but how do I edit the registry...I can't seem to locate any way to do so (no regedit?)
Manzil
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
Bump Im Stuck With This ****ty Radio!!help!!!tried Everything!!
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
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
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
tmknight said:
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
Click to expand...
Click to collapse
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.
Merlyn_3D said:
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.
Click to expand...
Click to collapse
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
hi
NYITGUY said:
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
Click to expand...
Click to collapse
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
NYITGUY said:
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
Click to expand...
Click to collapse
That's crap! 2.27 ROW Radio version is 1.54.01.00
NYITGUY said:
i was able to downgrade my unlocked and hardspl'ed 750 from 1.54.30.10 to 1.54.07.00...
Click to expand...
Click to collapse
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!
tmknight said:
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!
Click to expand...
Click to collapse
....
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?
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.
h
PsyberEMT said:
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.
Click to expand...
Click to collapse
same situation.
maybe we should upgrade to a newer radio rom? something that works better with at&t?
anyone?
Not even sure if there is a newer hermes radio out?
NYITGUY said:
....
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?
Click to expand...
Click to collapse
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?
ericizzy1 said:
same situation.
maybe we should upgrade to a newer radio rom? something that works better with at&t?
Click to expand...
Click to collapse
That's my hope too, maybe the new WM6.1 ROM that we're promised will have a newer radio that can overwrite this one.
A little input
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?
I'm stuck with it!
summiter said:
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?
Click to expand...
Click to collapse
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.
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.
-
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_Radinly_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.
Ive tried many different roms and many different radios and still havent found one that works great. most of the problems i have is with the keyboard for some reason on certain radios my keyboard will lag and different keys will not work all the time. and the weird thing is that if i change the radio it changes what keys work and dont work. i recently tried the newest rom and radio released on the htc website and that didnt help. another question can i download the rom for the htc tytn 2 from the website and flash it on a att tilt? thanks again for the help
crackzattic said:
Ive tried many different roms and many different radios and still havent found one that works great. most of the problems i have is with the keyboard for some reason on certain radios my keyboard will lag and different keys will not work all the time. and the weird thing is that if i change the radio it changes what keys work and dont work. i recently tried the newest rom and radio released on the htc website and that didnt help. another question can i download the rom for the htc tytn 2 from the website and flash it on a att tilt? thanks again for the help
Click to expand...
Click to collapse
Sometimes you need to change language when flashing certain roms diffrent from stock, if not match youre HK will be remaped to whatever the flashed ROM tells it todo . Example:
I am Norwegian so I have to change Curlang to 414 (414 Hex, 1044 Dec). I do this by searching up Curlang in my register (should be in: HKLM/Hardware/Devicemap/Keybd), then I Soft Reset. DONE! My Keyboard is now supporting ÆØÅ and all the oter keys and so on, just as I am used to on Norwegian Shipped/Stok Roms.
There are floating alot of curlang cabs for the diffrent phones in here, dig in or perhaps someone will post it for you.
its not just the mapping its just the keyboard wont type a letter unless i press it like 3 or 4 times. and im pretty sure its the radio and not the keyboard because if i change the radio different keys are effected. i no it sounds weird but im sure its not the keyboard or the mappings
crackzattic said:
its not just the mapping its just the keyboard wont type a letter unless i press it like 3 or 4 times. and im pretty sure its the radio and not the keyboard because if i change the radio different keys are effected. i no it sounds weird but im sure its not the keyboard or the mappings
Click to expand...
Click to collapse
I would deffently reflash to stock ROM asap! If its not rom/radio related I would suspect you got some fluid under HK? By the way you say diffrent (like in random?) keys ad affected makes me suspect its HW related if its really not as simple as radio. The remap should be the same on same country ROM`s for you, and the mapping is done in the register. If its radio related, you whole device should act strange and dodgy IMO.
ya i get what ur saying but when i use my gfs att sim card she doesnt have any problems only with my tmobile sim card
crackzattic said:
ya i get what ur saying but when i use my gfs att sim card she doesnt have any problems only with my tmobile sim card
Click to expand...
Click to collapse
Kinda relevant information, you shoulda sticked in there first place my friend Tmobile I have no experience on radio to share. Think you need to dig into radio treads as its probobly then as youreself concluded radio related. Just try combine diffrent roms -> radio until you find a good match then take notes of the given radio. I would also search more for other Tmobile comments on radio issues from the memebers.
Dont know how updated this is but belive you can take it for a spin: [4 December] The Ultimate Radio Thread
i have searched and it seems like noone has shared their tmobile radio experiences. ive been fooling with this phone all night and i may have a conclusion. i used jockeyw's unlock method and i believe my hardspl isnt upgraded to the 3.29 or 3.56 like the new roms require. i have tried to upgrade and still wont change my bootloader info. on my tricolored screen the 2nd line says "SPL-1.0.OliPof" which i am assuming is SPL1.0 not SPL 3.29. this is very frustrating because i cant change it no matter what hardspl i do. i even tried this post http://forum.xda-developers.com/showthread.php?t=354061 and it still didnt help. i think this is all the info i can come up with i hope someone can help
Some SPL Wiki reading called for
crackzattic said:
i used jockeyw's unlock method and i believe my hardspl isnt upgraded to the 3.29 or 3.56 like the new roms require.
Click to expand...
Click to collapse
So if you're using a Windows Mobile 6.0 compatible SPL (version 1.xx) with a WM 6.1 ROM that can give a host of problems, including freezing. I used this SPL Questions part of the wiki to change from the OliPof 1.0 SPL to a HTC 1.93 SPL the other day and using JumpSPL1.93-KAIS.exe it worked fine so there's something you're not doing right. If you describe what happened after you tapped Kermit, (including any RUU error messages) it may help us diagnose whats going on. I suggest you re-read that part of the wiki as well as this is getting a bit spoon-feeding-ish (which xda-dev is not about).
I have Hard SPL 3.56 and use KAIS_Radio_1.70.18.02 with PDA_Corner Ultimate X Beta II (ROM). My average download speed via tethering is now about 27 KB/s. It used to be only about 20 to 22 KB/s. Also make sure that you install the Tilt keyboard fix cab that is on the WIKI page if you are using a Kaiser ROM on an AT&T Tilt.