Related
I have installed the 1.12.10 GSM on it after making backups with aWizard. I am happy to report that it does work and that it does speed up the initial connection. Before (with 1.09.11 I beleive) I could log into (enter my PIN) and would still have some time before I would connect and get signal bars. It also seemed to increase refresh rates of the bars. Now the signal is usually found before I even finish entering my PIN muchless the today screen loading.
These tests were made in my basement at my house where I typically have been getting 1-3 bars. now to test 1.13.10 and 2.8 OS to see if it works.
I will say I thought it broke at first because I couldn't get my PC to talk to it after it reloaded, then I did another soft reset and the boot screen the second time didn't list the GSM version, even though the OS did see and use GSM. I re-ran the CID unlock procedure again since I could talk to the phone again. Reset again and GSM ver was on the boot screen again.
I also swapped out the boot screen for a bmp and that worked wonderfully. my only question is if there is a way to swap out the booting screen of the OS and not just the IPL Rom.
cheers,
ET
I have just done the RUU install of 2.16.9.101 which also upgrades IPL/SPL to 2.16. It changed my radio version to 2.7.10 and my protocol version is 413.1.0.3. This ROM date is 2/6/06.
Immediate differences are the battery notification is now at the top where on Cingular's ROM it was at the bottom next to the comm switch program. That and everything is I-Mate branded. No Get Good, but instead now I have I-Mate backgammon and Skype. And instead of the Cingular Mail link now there is an I-Mate mail link.
I will update later with more.
More... OS ver 5.1.195 build 14847.2.0.0 IDK if this is different or not.
Update 11AM: I have tested more. ZPhone themes I can't seem to install... IDK why but with the original Cingular ROM I couldn't either. The original ROM had a bug that used the proxy of the modem setting on the wifi setting making wifi not work unless you went and disabled it since it is enabled by default. This new rom after installing "Cingulcustomize_No_Emails.cab" to get MediaNet back, wifi just works. Even with the Proxy set on the modem connection. My Bluetooh headset (Jabra HT800) works great. Comm Manager is real nice. Even showing you the status of SMS and GPRS/EDGE connection. I want to play with it a little more to see if I can control those two or not. Gone from teh Cingular ROM is the ability to click on the Edge status icon in the notification area and tell it to turn on Wifi. But the Turn on Flight Mode still exists under the Cell Strength bar. Signal strength is comperable to the 1.12.10 radio rom I had before the upgrade. And IDK if it is taking longer to load from a reset or not, but before the Phone radio would be up and running just as I was finishing putting in my PIN unlock. But now it is running and connected before I can even start to input it. Just observation, that extra second doesn't mean anything.
I also have the 8125, so I am curious if the Imate ROM will cause any problems after the upgrade. I am not sure I want to wait a few more months until Cingular gets around to providing their upgrade.
Some other posters with the test/beta Qtek AKU 2.0 rom reported that they had trouble with the device resetting itself and problems with Wi-Fi. Let us know if you experience any issues with this ROM.
How has EDGE speed been, any improvements over the shipped ROM? Have you tried push email?
ok, i updated my 8125 to the new rom and am having two issues atm. first, the phone signal icon and the battery icon on the today screen is cut off so i only see the edge icon. secondly, i cannot start wifi at all, no matter what i do :\ (it looks like it's thinking but doesn't actually turn on ) now i did apply the cingular extended rom to this so i dont know if that caused both issues or not. as for edge performance, i'm in an area with bad signal so i couldnt exactly test it. i'm going to be clearing storage tonight and see if that fixes both issues or not. i haven't tested push e-mail as clubimates servers AREN'T supporting direct push (ie they don't have SP2 installed or have it enabled on exchange).
Locked up
Well I am noticing that it is locking up if I let it sit for a while to where I can't bring it back up. I have disabled the lock code to see if that fixes it.
I would have a feeling that the problems you are having are because of the enhanced rom difference. it won't hurt to try it as is like I did since you are having problems with it.
were can I fine install
I look for the rom in the ftp but there is no RUU install of 2.16.9.101 can you please tell me where can I fin this rom
thank you
Here:
http://forum.xda-developers.com/viewtopic.php?t=42638
Scroll down to HTTP server link.
Cheers
thanks
thank you for giving the info on where to get the link. I have been away from a pc today.
as an update: the phone seems to be stable with the new rom (I am actually using the phone now using edge and it seems faster than my old phone was which was a nokia.)
I haven't had it lock up on me since I uninstalled battery pack pro, disabled lock code, and uninstalled skype & backgammon so take your pick as to what fixed it. I will do some more expereriments to try and figure iit out.
later,
ET
Are you having the same issues as darkjedi who said he's having problems with WiFi and signal strength icon?
after the upgrade i cant find the GPS ICON
even i try to delete the redirect string in the registry like i used to do before
still i cant see the icon on my setting page
please anyone noticed this problem ?
tx
exchguy said:
Are you having the same issues as darkjedi who said he's having problems with WiFi and signal strength icon?
Click to expand...
Click to collapse
i finally fixed the signal strength icon (but don't ask me how), but wifi is still borked
no more problems, lock ups or otherwise
My guess with my problems were related to Battery Pack Pro demo. Even on the original rom I couldn't get it to work right with the assignable hard keys.
Anyway, I did not modify the original EXE one bit like darkjedi said he did. He seems to be much more advanced as I don't know how to do what he did and not that familier with its registry settings yet. But I naver had any problems with Wifi nor with icon placement.
My home wifi does use WPS-PSK TKIP using a Netgear WG302. Battery life seems good, but I do get a little crackle every now and then on my end of the bluetooth handsfree. People I talk to haven't said they hear anything other than perfect clarity. I would have been told if they heard anything since part of my reason to spend the money now rather than later was my voice and signal quality on my old Nokia was getting to be bad and they wouldn't waste a second ragging me if voice and signal problems were re-appearing. But mostly the crackle is few and far between and usually when my headset is on the other side of my body or I am a few feet away from my phone.
i didn't modify the original EXE, i installed it as normal, then after the fact, copied the cingular extended ROM then installed each cab manually. i didn't get a chance to try wifi before i applied the extended rom, but i just might hard reset and try that.
i dnt see the rush to upgrade if u have a cingular 8125 since there goa offer rom upgrades for the unit. with all the bugs i rather just get a ad2 bt plugin (wish they made it) and just do that
what roms do they offer? On my past phones I have had to have major problems before they would flash a new version of the Rom (my last 2 symbian phones).
darkjedi said:
i didn't modify the original EXE, i installed it as normal, then after the fact, copied the cingular extended ROM then installed each cab manually. i didn't get a chance to try wifi before i applied the extended rom, but i just might hard reset and try that.
Click to expand...
Click to collapse
ok... the only cab I installed for Cingular was the one I mentioned earlier. I have since installed spb power plus and their weather app and I am still stable. Not one failuer and my bluetooth is actually acting better from some reason. I was working on my car today with teh phone in the car and I was about 10 feet away without any noise or other problems.
Re: thanks
ethorn said:
thank you for giving the info on where to get the link. I have been away from a pc today.
as an update: the phone seems to be stable with the new rom (I am actually using the phone now using edge and it seems faster than my old phone was which was a nokia.)
I haven't had it lock up on me since I uninstalled battery pack pro, disabled lock code, and uninstalled skype & backgammon so take your pick as to what fixed it. I will do some more expereriments to try and figure iit out.
later,
ET
Click to expand...
Click to collapse
Is there any settings to configure edge? I only see GPRS in the connections section.
This version appears quite stable but's only my second day since upgrading my 8125 from the QTECH 2.8.7.102. I really like the Comm manager and the Push Email icon works great.
Thanks!
name of account
the only thing that I have notice so far is that the name of my celular company (I could see before upgrade) now i only see numbers.
exchguy said:
I also have the 8125, so I am curious if the Imate ROM will cause any problems after the upgrade. I am not sure I want to wait a few more months until Cingular gets around to providing their upgrade.
Some other posters with the test/beta Qtek AKU 2.0 rom reported that they had trouble with the device resetting itself and problems with Wi-Fi. Let us know if you experience any issues with this ROM.
How has EDGE speed been, any improvements over the shipped ROM? Have you tried push email?
Click to expand...
Click to collapse
On the new imate ROM I'm getting between 65 and 110 kbps on edge. Latency is still crap at about 1.5 seconds on average, but that's what it's always been for me.
Direct push is great. Assuming you have Exch SP2 installed, push works without any other changes. I'm averaging between 7 and 10 seconds for an entry to push out after it gets to Exchange. I haven't installed the device management tools yet, but I'll do that soon and let you know how well they work.
I just noticed wifi isn't working. If I enable it in comm manager, the button is ringed in green as if it's on, but the left green led does not blink and it does not detect my open, unsecured access point. I did install the cabs from my original cingular extended rom, and one of those appears realted to wifi, but not sure what it does. I'll mess around some more and see what I can do. I'm not totally heartbroken that wifi is messed up, but it does bug me that I don't know why it aint working.
Need Cingulcustomize_No_Emails.cab file
ethorn said:
I have just done the RUU install of 2.16.9.101 which also upgrades IPL/SPL to 2.16. It changed my radio version to 2.7.10 and my protocol version is 413.1.0.3. This ROM date is 2/6/06.
Immediate differences are the battery notification is now at the top where on Cingular's ROM it was at the bottom next to the comm switch program. That and everything is I-Mate branded. No Get Good, but instead now I have I-Mate backgammon and Skype. And instead of the Cingular Mail link now there is an I-Mate mail link.
I will update later with more.
More... OS ver 5.1.195 build 14847.2.0.0 IDK if this is different or not.
Update 11AM: I have tested more. ZPhone themes I can't seem to install... IDK why but with the original Cingular ROM I couldn't either. The original ROM had a bug that used the proxy of the modem setting on the wifi setting making wifi not work unless you went and disabled it since it is enabled by default. This new rom after installing "Cingulcustomize_No_Emails.cab" to get MediaNet back, wifi just works. Even with the Proxy set on the modem connection. My Bluetooh headset (Jabra HT800) works great. Comm Manager is real nice. Even showing you the status of SMS and GPRS/EDGE connection. I want to play with it a little more to see if I can control those two or not. Gone from teh Cingular ROM is the ability to click on the Edge status icon in the notification area and tell it to turn on Wifi. But the Turn on Flight Mode still exists under the Cell Strength bar. Signal strength is comperable to the 1.12.10 radio rom I had before the upgrade. And IDK if it is taking longer to load from a reset or not, but before the Phone radio would be up and running just as I was finishing putting in my PIN unlock. But now it is running and connected before I can even start to input it. Just observation, that extra second doesn't mean anything.
Click to expand...
Click to collapse
Where did you get the "Cingulcustomize_No_Emails.cab" file? I have searched everywhere and cannot find it! Help?
Hey All-
Rather then adding to the large Helmi thread, I figured it would be best to start my own...
In short today I upgraded from TuMa v1.3 to Helmi's new ROM: Helmi_BA_WM2k5_AKU_2.3_32mb_v1.rar
Everything went fine during the upgrade, I set the Operator Code to T%CID? which was retrieved by using GetDeviceData.exe and the upgrade went smoothly... but now the phone functionality doesn't work at all. I've tried with two different SIM's, one being a T-Mobile and the other a Cingular. Both just show no service when inserted, although if I place those SIM's into other phones everything works properly without issue and I get 'full bars' (I have another Cingular 8125 and a T-Mobile SDA).
Here is what I have done so far:
- Reupgraded the Radio to the latest rev 1.15
- Recreated the nk.nbf again with retyping the operator code
- Reupgraded to the ROM to Helmi's
- Reunlocked SIM with xdadev_all_unlock-v1.5.exe
... and still no phone service.
Any suggestions on how to get the phone functionality to work properly? Its pretty much useless right now...
Thanks!
tempie23
I'm not sure that T%CID is right for an operator code... I know for O2 UK it's O2___001 and I'm sure a T-Mobile code isT-MOB101, both of these are 8 digits... check you're devicedata output again and use the setoperator.bat to set it properly, then try again
It's all good clean fun
spkr4thdd
I have the same operator code T%CID? but only on WM5. When i use 2003SE it is DANGA001.
tempie23
I had such error on TuMa 1.4 but reinstalling the ROM helped for a while. Then I tried helmi's ROM and the problem gone. But a couple of days ago it appeared once and reflashing did not help. What I done is downgraded to 2003SE, did a hardreset and reinserted SIM. The phone came back to work. Then installed helmi's ROM again. Now it is working for a day without any trouble, HOPE it's gone forever.
Tried a few things...
I tried downgrading and then reupgrading, but it still is stuck. No phone service. Interestingly enough the LED for the phone doesn't even come on anymore.
Interestingly enough when I select the phone settings from the upper menu I'm getting a Popup message stating "The phone is not ready. Wait 15 Seconds and try again." Obviously waiting 15 seconds does nothing...
Any other ideas?
Thanks!
tempie23
sometimes (happened to me) the operator info corrupts when upgrading to WM5
copy the files attached to the update directory and run 'MaUpgradeUt_noID.exe'
spkr4thdd said:
I'm not sure that T%CID is right for an operator code... I know for O2 UK it's O2___001 and I'm sure a T-Mobile code isT-MOB101, both of these are 8 digits... check you're devicedata output again and use the setoperator.bat to set it properly, then try again
It's all good clean fun
Click to expand...
Click to collapse
No it is not, it sounds like he has the same SX 66 that I have.
The ID is = AT%CID?
I posted this in this thead Here
read my above post, it can happen to anyone when upgrading to any wm5, mine happened the very first time i upgraded (TuMa 1.3), i dont know how it happens, but it seems to be permanent even with further reflashes (haven't tried 2k3)
NO Service
Midget_1990 said:
read my above post, it can happen to anyone when upgrading to any wm5, mine happened the very first time i upgraded (TuMa 1.3), i dont know how it happens, but it seems to be permanent even with further reflashes (haven't tried 2k3)
Click to expand...
Click to collapse
HI.
Sorry for my post, but I did not "get" how to fix the "NO Service" error:
This is what I've done today with Helmi_BA_WM2k5_AKU3.5_v1.4.CF2 by baniaczek:
Hi all.
Today finally spent some time, trying to upgrade my Qtek 9090.
Everything went fine:
1st) Did a SD backup of my current settings;
2nd) Updated ROM with SetOperator to my Operator (got from getdevice.txt);
2nd) Updated without problems;
Then used the Qtek by 5 minutes (inclusively i did a phone call), after that could no longer get the "phone" working - exactly when I received a call, the phone "gone out" and never more. After several soft resets and hard resets the phone was always with "no service" message (but strangely, I could go to settings phone, and look for "the broadcasting" networks).
I swaped the SIM to another phone and it was working, never the less I got another working sim, but the problem continues (btw, I always have the PinCode disabled, and I remember now that I forgot to test enabling PinCode request!!!).
Then, just in case I downgraded the phone to W2003SE, again, and everything was working fine.
My radio was 1.12. So upgraded radio to 1.15, and started over again but with no sucess.
When I downgraded once again, the Qtek works fine with either RADIO versions or sims.
Has anyone got this "nice feature"?????
Is there any overcame solution? (My only missing test is to enable Pincode, and test if it works?)
tks for any help
I'm having the same issue here as well, tried the comm manger on and off and disable and enable it. Still makes no difference, someone please help me out, I can't get anyone to help me
So, I've unlocked my T-Mobile MDA G3 phone both CID and otherwise using loki. I've tried the T-Mobile update off their own site, and here is what happens. I suspect I need a different data cable, but I might be wrong there, so I figured I'd bring the issue to you all because you are the gurus of all gurus...type peoples.
So, here's what goes on. I download the software. I sync my MDA and my notebook. I ensure both machines are on and set to stay on. I check the connection and all is good. Heck, I've even backed up my MDA system using one of those backup utilities for Smartphones available online for trial download(which worked great, btw). So I run the software and click next and check everything it says the check and then it begins. This is where my problem begins and the goodness ends...
The MDA shuts off and just sits there. I don't touch it for fear of what might happen by being impatient, but every time, no matter which ROM I've tried to use for update purposes, the notebook pops up saying that it encountered a "communications error". It doesn't brick the phone, thank God. It simply just requires removal of the battery for 5-10 seconds after disconnecting the USB, then turning it on. It boots fine and all is good, except, no new ROM, same old 1.0.8.something version and bah!
I want to update my ROM and am stuck. I've tried at least 5 DIFFERENT ROMs and loaders and still the same thing.
I'm running the original T-Mobile ROM 1.0.8.something, IPL 1.X, and SPL 1.X. The phone says it's unlocked using the CheckLock program you can download from the forums, or elsewhere, I forget which. I've run the cidunlock with the loki tool multiple times and it finishes no issues.
If anyone has ANY ideas or thoughts, or even if they've run into this I'd like to know.
I'm pretty sure my phone right now won't do the whole A2DP via bluetooth bit, and that's what I'm REALLY wanting. I just got those Motorola HT820's and am anxious to play around with them more.
Anywho. You all rock and I've only been here like a day, but your information, walkthroughs, and just general geekiness(oh yeah, I work for the Geek Squad and we ALL use either the Verizon or Sprint version of the MDA, heh heh) have been most appreciated!
-----------
Originally posted under xda-developers > Wizard (Oops? )
Can someone please help me? I am a total noob right now, I just got a Treo 750 which was supposed to be unlocked (i got that taken care of) but I want to update to WM6. my version is
treo750-1.13-cng
but I dont use cingular, I am currently on T-mobile. I dont want the lame xpress mail and crap from cingular or att, so which update should I use? I was wondering about the generic one, will that have everything i need to use it on a different carrier but just not have the cigular stuff? (instead of getting the att update). I see ROW, RWE, ect and I dont know what any of these versions mean or the differences. Can people help, thanks much appreciated.
come on, people are reading this so give me some thoughts. i was thinking of using the official ATT release, but would the ROW 2.23 release be better for me? or am i missing out on stuff by not using the ATT one. I just want unbranded crap basically.
I just got a 750 about two weeks ago. When I received it, it had the same firmware you've got now (1.13-CNG) and I am also on T-Mobile. I updated to the unbranded 2.23, see this link for instructions on 'tricking' the updater to work with your CNG phone:
http://discussion.treocentral.com/showthread.php?t=156093&highlight=wm6+unbranded
You can also update from a MiniSD card; it is a bit less hassle but it won't show the new version number on your phone. (Plus I didn't have a MiniSD card )
Unbranded is definitely the way to go. No AT&T logos anywhere and no AT&T internet proxy. Also, the unbranded firmware includes the Windows Live app while AT&T has chosen to remove it. So far I really have no complaints with WM6 and this firmware version. I've been using the phone full time for a couple weeks and the only glitch I've hit was today I was in a building with no signal and the phone wouldn't re-acquire a signal when I left. I quick soft reset fixed it though.
There are a couple newer releases out, someone just posted the unbranded 2.27 release, but it has some bugs that were fixed in 2.23 and supposedly the radio version was older.
Also, I've seen some mention of a 2.30 release, but I haven't found it unbranded yet.
If you have any problems getting your T-Mobile internet or MMS settings done, shoot me a PM -- I spent a bit of time finding the proper settings already!
nope, didnt work, I dunno why. I still get the same error. Im not sure if its something wrong Im doing or just some registration error or whatever. I dont get why it fails everytime and tells me "I should be an administrator to run the update" pissing me off I WANT WM6 ALREADY.
You didn't mention any error in your original post(s)... I answered the questions you asked.
Are you running WinXP or Vista?
sorry yea i made 2 threads and did in the other. it wouldnt let me install, kept saying you should be the admin to update, even though i am the only user! but then i installed on vista and it works great =)
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.