OK... So I sit here trying to read all all of the posts out there... With one simple purpose.
What is the best version for my 8125 (I know this has ben asked before)... I am very intrestd in the Mr. Clean version, bit would like the Cingular custom cofiguration (much like the one done for T-Mobile). I can configure the setting myself, but I am still intrested an all the Cingular customizations.... So a version for Cingular has a great deal of appeal.
Presently I have the latest build from the HTC web site, but I seem to be fighting a ActiveSynce issue... I am not 100% sure it's related to the build.. but I know I did not see it with the previous build.
So here it is simply put: What is the latest build us less fortunate peolpe can get and get the customizations we need for our carrier (in an installable format)?
Thanks very much....
Additionlly, thank you for all the work that has been done to date... You guys rock! :mrgreen: [/b]
Sorry, but I have no answer to the ROM question, but I think I might have a possible answer to the activesync problem. Did you upgrade from the 1.8 stock rom to the 2.25 official Cingular rom? That's what it seems like to me....
If that's the case, did you download and install the newest version of activesync from the MS website after flashing the 2.25 rom?
If not, that's what should fix the AS issue.
ActiveSync
I have upgraded to several version for that have been posted here.. It only seems that the issue is on the new Cingular released ROM image....
And I am running the latest build of ActiveSync....
At 1st I thought it was Norton antivirus blocking the ports.. But I set that up and still can not make the connect... removed Norton and went to Zone Alarm, open up all the programs and ports still same issue... I know it’s with the device (or I should say this OS version), since I don't have an issue with my two 2003se devices. And as I aid to the best of my knowledge it did not occur prior to this upgrade.
I think am going back to 2.17 until I see a different build for Cingular... I would love the Mr. Clean as I said, but I want the Cingular customizations…
I know PICKY PICKY PICKY
Hello all, 1st post here. I will be aquirring a XDAIIi in a week or two as a relative is replacing his firms pda`s and im getting one of the old units.
I know they were on O2 and I have a T-mobile sim so Id like to unlock it.
I have found the unlock info on this forum and will give that a go.
My question is, what should I check for to make sure it will be running as best it can be and how can I find out what s/ware should be loaded onto it and is there a way of getting a master copy of the original build or will this all be on the software disks that came with it ?
also is there any particular sat nav s/ware that works better than most on the XDAIIi?
I understand the xdaIIi is called something else in places, what is that name ?
sorry there such open questions nut couldnt think how to phrase them in order to do a search.
many thanks in advance, Lee.
Moving to alpine.
podhead said:
Hello all, 1st post here. I will be aquirring a XDAIIi in a week or two as a relative is replacing his firms pda`s and im getting one of the old units.
I know they were on O2 and I have a T-mobile sim so Id like to unlock it.
I have found the unlock info on this forum and will give that a go.
Click to expand...
Click to collapse
I have sucessfully unlocked three of my firm's old Alpine's, aka XDA IIi, using the file in this post, All in one SIM unlock tool, personally i found the earlier version more successful, but you may be OK with the newer version. The biggest thing i would say is to have patience, when you run it, it will seem to finish and nothing has happened. Wait until you receive a message saying it has been unlocked, and then soft reset.
Only other advice i can give is to do a hard reset to get it back to factory settings and then when you get a popup saying "Applying customisations in 3 seconds", or something similar, soft reset. This will prevent the O2 stuff being installed, leaving you with more RAM to play with.
Thanks Ive sucsefully unlocked it for t-mobile, fantastic. just need to find out what else I can do to improve this pda.
Don't try to improve it
as is it is one of the best ever made OK yes it restricted because of only running 2003SE but it runs it dam fast. I have a friend that has a Orbit (the latest one by O2 thats the equivilent of the XDA IIi and mine is as fast as his and he ditched the crappy sat nav software that came with it to go back to TT6, ref sat nav software it runs TT 6 fine I have it on mine and have no problems whatso ever.
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.
Hi guys, I really did search first, I promise. I have been having connectivity issues (not making calls, lost data connections, etc...) since I updated to the ATT Official Windows Mobile 6.1 ROM (3.57.502.2 WWE) with radio version 1.65.21.18. I am trying to determine if I need to upgrade my radio version. I found the thread with all the radio versions for my phone but don't know anything about them. I did get that I should try different ones until I find one that works for me. So do I need to install the HardSPL on my phone (or did the Official ATT rom upgrade do that already)? From there do I run that RUU.exe file on the desktop (or what)? It would be great if someone could put this in super simple terms for me.
Thanks in advance,
-Max
one word for your info, "WIKI"
I did look over the wiki for some time, here is my hang up. Jockyw2001 posted in an SPL thread that "SPL3.56 is part of the latest AT&T Rom which is dated June 6. 2008" So since I did the official ATT upgrade and my ROM date is 07/17/08, does that mean that I already have SPL 3.56 on my device? I can not find a post about how to determine what SPL version (if any) is installed on my device. If SPL is already installed, is there any danger in installing an older version of SPL or reinstalling one?
Thanks again
-Max
maxjenius211 said:
Hi guys, I really did search first, I promise. I have been having connectivity issues (not making calls, lost data connections, etc...) since I updated to the ATT Official Windows Mobile 6.1 ROM (3.57.502.2 WWE) with radio version 1.65.21.18. I am trying to determine if I need to upgrade my radio version. I found the thread with all the radio versions for my phone but don't know anything about them. I did get that I should try different ones until I find one that works for me. So do I need to install the HardSPL on my phone (or did the Official ATT rom upgrade do that already)? From there do I run that RUU.exe file on the desktop (or what)? It would be great if someone could put this in super simple terms for me.
Thanks in advance,
-Max
Click to expand...
Click to collapse
So you are saying that the stock rom and stock radio are not working correctly, no cooked roms or other carrier radios?
Did the problems start right after you updated?
Oh and your problem seems similar to the one in this thread here, well least is sounds similar to me anyways...
SavageWolf said:
So you are saying that the stock rom and stock radio are not working correctly, no cooked roms or other carrier radios?
Did the problems start right after you updated?
Oh and your problem seems similar to the one in this thread here, well least is sounds similar to me anyways...
Click to expand...
Click to collapse
Yup, stock radio and rom as suggested by ATT, whom their customer service now claims they do not support WM6.1. I've never used a cooked rom and really only come here for device information and applications. I did have problems before I upgraded the rom but they have much worse since. The thread you posted is similar but they mostly talk about an "H" connection. I am in the DC metro area (USA) and get 3G all the time now, I wonder if that is part of the problem, I never get an EDGE network signal anymore.
Well... I just found THIS buried over on the ATT support forums
Clp1970 01-21-2009 10:33:16 AM
I guess we just got 3G network here. I haven't been able to make/receive calls for 5 days now. Tech support supposedly looking into issue. My phone switches bewteen 3G and EDGE constantly. Anyone else having this issue? What was the resolution? I don't want a refurbished Tilt if they can't come to a resolution (why would I want the same darn phone if it doesn't work well with 3G as advertised?) I have already drove 20 minutes to the nearest store for a new SIM card..which did no good. There isn't anyway of turning off 3G network unless I install software I have seen mentioned on this forum and well, I don't know about that...I paid for this phone to do what it said, and it isn't.
Click to expand...
Click to collapse
And this is the reply to it over there....
tilteduser 01-21-2009 08:42:13 PM
Common problem that can be either due to problems with the rollout or that the local towers cannot handle 3G as effectively or at a greater distance as the same tower could for Edge. These are some related threads and posts but there are a lot more. As noted in these posts if there is a local AT&T store run by AT&T then you might pop in and confirm some of the problems with them.
http://forums.wireless.att.com/cng/...lar&message.id=103583&query.id=659420#M103583
http://forums.wireless.att.com/cng/...lar&message.id=103054&query.id=659420#M103054
http://forums.wireless.att.com/cng/...gular&message.id=92693&query.id=660536#M92693
The tendency is to blame the phone but the reality is often different and that includes from customer support who offered to swap my phone several times but this obviously would not work because it affected many other users as well differing phone manufacturers and models.
Click to expand...
Click to collapse
Timing of it is close enough to make me wonder, but I had been using HSDPA.. But I have been getting the same problems you are talking about when the phone is set to 3g as well. The other thing that is starting to make me think its something ATT did to their network is that the OP from the thread that I linked on here lives 20 mins west of my location, and I am 15-20 mins north of DC... I may go to one of the local att stores and see what they have to say (tho that means for me that I get to flash my phone back to the stock rom )
I have had a Treo 750 on AT&T for the last year and a half or so, and have never gone "outside the box" for upgrades til recently.
Device started as WM5.1 and I used the AT&T upgrade to get to 6.0
About a month or so ago, work ported my number from AT&T to T-Mobile and gave me a BB Curve 8320 as a new phone. While I used to use BB's, after getting into the WM side, I quickly realized I couldnt go back, and decided to unlock my Treo, and use the T-Mobile sim in it.
Everything has been working, but other projects have kept me from being able to look into why I wasnt getting 3G on the Treo. I would consistently have a G indicator, and dslreports never would report higher than 180K on a 100K d/l test.
I started to try to fix it by upgrading to the WM6.1 generic img that is here - since I already was set up for SD card upgrading, this was pretty easy, tho it didnt fix the speed issue.
I next looked at the radio - firmware was reported as 1.16, so I bumped it to 1.50.00.0, as this was the highest on the wiki that reported success with T-Mo. By doing this, I was able to get the G to change to an E, but I think this was largely just a lateral move, as the speeds havent changed at all.
I have tried numerous times to re-flash the radio, but the firmware never changes - always say 1.50.00.00
The weird thing to me is that i even fell back to WM6.0 by getting the nbh file out of the 2.27 ROW Palm updater, but even though it did fall back to that OS, the software version still reported TREO750-2.25-ATT and firmware was still 1.50.00.00
I reapplied the generic 6.1, still shows the same software and firmware.
Even though everything "works" - I'd still like to get 3G if at all possible, and would love any suggestions of other things to try, if anyone has any...
Thanks!