Sorry guys to bug you but i need your help.How can i revert back to
Qtek_9100 old rom 1.6.7.1 after upgrading to 2.8.7.102?I downloaded a new 1.6.7.1 ROM, tried that several times and it kept on telling me that I'm using a newer ROM therefore an upgrade is not possible.Could you outline to me or point me to a detailed info for downgrading cause the new ROM is not stable on my device(Qtek 9100).It keeps on rebooting even during a call and when i'm running other applications.
I'd appreciate your kind help.Thanks a mil.
I have a similar problem. Except I need to go back to my original tmobile MDA ROM. A2DP works fine, but nothing else is working for me. How can I go back?
davidbessler said:
I have a similar problem. Except I need to go back to my original tmobile MDA ROM. A2DP works fine, but nothing else is working for me. How can I go back?
Click to expand...
Click to collapse
Did you backup your original rom? Also is aWizard not letting you go back to your previous rom? I have posted the production T-Mobile USA ROM in a different post on the board if you don't have your old ROM.
I am also curious what the issues are you are having as I have been wondering about trying the test ROM on a USA unit for T-Mobile going from 1.x to 2.x as you did.
I could use a link to the TMO USA MDA ROM just in case I need to exchange the machine. That said, I am having absolutely NO problems with the QTEK TEST ROM. However, I did lvlolvlo's trick and after I had flashed the new ROM, when it said that in 3 seconds it would install the extended ROM, I quickly soft-reset, and then installed the extended ROM stuff from TMobile. This automatically set up my internet, and made the email triggers a snap. I can now use my Motorola STEREO bluetooth headset (even has a mic for the phone). As an added bonus, with the TMO ROM, I was unable to have both MortButtons and MS VoiceCommand installed simultaneously (something about the startup folder), but with the QTEK ROM they both work.
You know, I came from the 6315, and this machine is FLAWLESS ... really a top-notch device, with the QTEK ROM, it is even better.
If you would like me to test out any functionality with this configuration, let me know, I'd be happy to test it out.
Can you get me that link to the original TMO ROM just in case?
I posted this not too long ago. It has the main rom and a link to the extended rom.
http://forum.xda-developers.com/viewtopic.php?t=42130&start=0&postdays=0&postorder=asc&highlight=
The reason I ask about your functionality is that you said your bluetooth stereo profile was working now but nothing else was? I am tempted to switch to the newer rom but not without some assurance it works semi decently. I am mainly interested in the Radio rom upgrade as mine seems to take a while to re-obtain a signal once it is lost and it ocassionally appears to not accept calls (going to voicemail) even though it has signal strength.
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.
I've searched through the forum but can't seem to find any topics based on this question. Of recent months, I'm having terrible problems with;
- People finding it hard to hear me from time to time (as a result of me going 'very quiet'),
- Calls not ringing through (despite volume being turned up),
- Calls cutting off despite mid-signal levels which suddenly drop.
I'm guessing all these are faults with the Radio ROM. I'm currently using 02.07.10, any recommendations on what I should be upgrading too?
try each of these: 2.09.11, 2.40.11, 2.47.11, 2.61.11, 2.69.11, 2.71.11 to find best radio for your rom!
I am on O2 UK PAYG with my Wizard and I use radio rom 02.19.11. It works really well, and is the best I have found without other issues.
if you dont search....
First of all... search but now...
radio 2.19
http://rapidshare.com/files/84722422/T-Mobile-UK_2.19.11_Radio_Only.zip.html
radio 2.71
http://rapidshare.com/files/91064086/radio_2.71.rar.html
Because nobody said his own informatin...I will said it again this is just Radio upgrade but remember... you need to be CID/SIM unlocked before do anything stupid ok?
See you soon tell us what does it works for you ok?
See you soon!
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.