Related
All,
I have a US T-Mobile Pocket PC Phone edition. I am using it on AT&T's GSM netwotk in the US, and everything runs ok after removing the SIM lock.
However, AT&T has a set of "acceleration" utilities for the GPRS data connection. This might be nice to use to try and compress or proxy (or whatever it is they do) to save a little bit of data and thus money.
I recently downloaded the latest software package from my-siemens.com for the SX56 device.
Could this work? AT&T software in the T-Mobile device? What precations could - should I take prior to attempting running the AT&T installer in the hopes that it will upgrade / overwrite the T-Mobile software?
Any other thoughts / ideas? Has anybody tried this?
Feel free to email me at [email protected]
Thanks
Mikkel
Hi,
I downloaded the Siemens AT&T update with the intention of installing
it on my T-mobile. However when you run the update program it
says that it cannot install because it is not compatible with the existing
system. So it looks like this is not an option
Mikkel said:
All,
I have a US T-Mobile Pocket PC Phone edition. I am using it on AT&T's GSM netwotk in the US, and everything runs ok after removing the SIM lock.
However, AT&T has a set of "acceleration" utilities for the GPRS data connection. This might be nice to use to try and compress or proxy (or whatever it is they do) to save a little bit of data and thus money.
I recently downloaded the latest software package from my-siemens.com for the SX56 device.
Could this work? AT&T software in the T-Mobile device? What precations could - should I take prior to attempting running the AT&T installer in the hopes that it will upgrade / overwrite the T-Mobile software?
Any other thoughts / ideas? Has anybody tried this?
Feel free to email me at [email protected]
Thanks
Mikkel
Click to expand...
Click to collapse
Just copy our adaptROM program to the directory where the AT&T upgrade has installed, run it, and then run the upgrade ("Programme A"), and you're all set.
Hi
Thanks for the tips & advice.
I ran adaptrom. If I understand correctly, I should now be able to flash the AT&T rom into my T-Mobile device?
I am concerned with all the postings here about folks having fried their devices after flashing. It seems that upgrading the radio software is especially sensitive?
So... Has anybody out there tried flashing a T-Mobile device with the AT&T radio & Win CE rom images?
Any special hints? Anything to be aware of prior to attempting this?
Sorry for all the questions, I just would really really hate to damage my device (I love my XDA, does that make me a bad person?)
Anyways, thanks all for all the interesting posts, and THANK YOU to all the XDA developers, you guys truly rock!
/Mikkel
i did it successfully on mine. word of advice is to hard reset ur t-mobile before u run update. then it works without problems.
alex
kalex said:
i did it successfully on mine. word of advice is to hard reset ur t-mobile before u run update. then it works without problems.
alex
Click to expand...
Click to collapse
Hard reset... As in using the tiny button with the battery icon to completely reset the device, or just a "normal" hard resent from the other little hole on the other side of the SD card slot?
A 'normal' reset is usually called a 'soft reset' (big hole), a 'hard reset' refers to the small hole and wipes the contents of the RAM, and thus everything that is not in ROM.
Kinda off topic but.....:
the current setup I have with the T-Mobile ROM running on AT&T's US GSM/GPRS network gives me about 11 kilobits/second as the highest speed.
This is, as far as I can tell, equal to one "channel" or "Timeslot" in the GPRS world.
Is it likely that changing to the AT&T firmware would allow me to use more than one channel (The device would be a "type 4" or "type 8" or something)?
Or in other words: Would I get more speed over GPRS from doing this?
Alright, performed the upgrade as per the instructions in this and other treads.
IT WORKED!!!!
My T-Mobile device is now running AT&T software. How cool is THAT??!?
Do you still have internet access? I seemed to have lost mine. Everything else works great.
MrDollyMaker,
u don't loose interet access. after u flash the rom u can no longer use auto configuration of t-mobile gprs. u have to manually configure it. i noticed on mine when i did the update i had to wait couple of hours for it to kick in.
alex
Anyone have a ROM of WM2003 that works w/ T-mobile USA? I tried about 5 and no luck. XDA dev Rom works great and so does my old one, but can't find a 2003 rom that works. All either hang at the boot/welcome screen or don't boot.
--Mike
So far I have tried 3 different 2003 roms.
The first the "O2" rom loaded, but gave me some intermittent problems.
The second “For Testing Only” rom worked great. Only one small problem with Microsoft reader. I most likely wouldn’t have changed except that the new ROMkitchen got me more excited than it probably should have.
Now I am using the ROMkitchen version very happily….(same problem with the reader though)
Interesting because I tried the ROMkitchen version yesterday and got the same, hangs on welcome screen result. Did you do anything special other than put it on SD with XDArit? I have Wallaby 5.15 bootloader which I think is what the unit shipped with but from what I've read this is fine.
I'm just at a loss because I've tried most everything I can think of. Which file type did you select from the ROMkitchen? I grabbed the nb1. Should I try NBF? Does it matter what I put in the "header string" at the bottom of the ROMkitchen page? I noticed when I try to upgrade it says my device is PW10B1. Does that matter?
Maybe you can post or email me your ROM and I can try that today.
--Mike
I didn't use the SD card boot with the Kitchen rom version. I had the Kitchen create an .exe file and let it load through usb. I actually did it 2 times...and it worked both times. Just did it the second time after they fixed PocketMVP.
I will e-mail it to you if you want, but I think that you should try creating an .exe through the Kitchen first...since that is what I would e-mail anyway.
Scott
The Hang that you see may be caused by the simtoolkit loading on startup. Try removing the link in the windows startup folder. that may help
My fellow T-Mobile WM2003 users, I have been using all 3 versions successfuly with no freezups. There is a little trick that increases stability when on the US networks:
Go to your \Windows\StartUp\ directory and DELETE Ussd.lnk and STK.lnk.
These are autoconfiguration apps that work with European providers but do nothing for the T-Mobile network; so much so, that with the T-Mo original ROM these apps were not used at all.
When these apps run in T-Mo's (Cingular's) network here in Los Angeles area, I've even experienced random cold resets when switching cell sites.
Ok, sounds like that's the problem then, but how do I remove this from the startup if I can't get it to go past the welcome screen? Can I bould a ROM in the kitchen w/o these options? I only saw an option for where to "move" these apps and not an option to not have them installed at all.
--Mike
Sorry, the kitchen doesn't allow you to do that. If you know how, you can burn your own rom and exclude these items. Anyone know what ussd is for? As mentioned, i have deleted the toolkit link and have not had any problems, just curious as to what ussd is.
valheru said:
Sorry, the kitchen doesn't allow you to do that.
Click to expand...
Click to collapse
Now it does...
Check the new 'Remove 'stk.lnk' from Startup folder' option. If someone tells me what ussd is and why it's bad, I'll add it to the remove list for this option...
Tried the new ROM w/ stk.lnk
Ok, I tried the new ROM and still no luck. Tried it as both .exe and as a SD flash and get the same net result. System hangs after bringing up the radio stack version and OS version as well as the third number which is: G324e4.
This device flawlessly runs the 3.17 xda ROM as well as T-mobile 3.14 so I don't understand why it will not take any 2003 ROM successfully. Any more ideas?
USSD
Unstructured Supplementary Services Data
USSD is a means of transmitting information or instructions over a GSM network. USSD has some similarities with SMS since both use the GSM network's signaling path. Unlike SMS, USSD is not a store and forward service and is session-oriented such that when a user accesses a USSD service, a session is established and the radio connection stays open until the user, application, or time out releases it. This has more in common with Data than SMS. USSD text messages can be up to 182 characters in length.
STK is for SIM ToolKit - It should not cause any problems unless you have a really old SIM Card.
I think USSD is basicaly a thing for ie. GSM banking - it allows the network to send you binary SMSes deciphered by the SIM (when I login with my GSM key to a bank account, I receive a message with temporary password, it is not sent through ordinary SMS, but delivered to the SIM toolkit area which is protected by PIN)
XDA developer Peter Poelman said:
valheru said:
Sorry, the kitchen doesn't allow you to do that.
Click to expand...
Click to collapse
Now it does...
Check the new 'Remove 'stk.lnk' from Startup folder' option. If someone tells me what ussd is and why it's bad, I'll add it to the remove list for this option...
Click to expand...
Click to collapse
xda-developers,
might be a stupid question but, i checked the command to remove stk.lnk from startup in (one of the reigstry hacks) and the command is the same as to add object. how do u remove it from startup, is it based on the file name. this one has rmobj extension.
thanks
alex
I'm sick of waiting for an answer from T-Mobile on when WM2003 will be available for the PPCPhone Edition, if at all, so I decided to create an executable of 4.00.16 at Jeff's kitchen.
I'm a little freaky about installing it. So before I do I would like to know (1) problems encountered from those that have done the upgrade and (2) the exact instructions on how to return back to my original T-Mobile OS ROM.
I know there are many of you out there that feel the same anguish regarding T-Mobile's lack of information regarding WM2003 & the hopes of better software that improves the PPC's ability to connect via GPRS (it sucks now) and overall performance. After all, we spent a load of money on this sucker.
Thank you in advance to all the gurus out there who answer this for the rest of us
If you install the XDAtools, you can create a backup of your ROM through ActiveSync. If at any time you click on the backup file, you will be offered the option of burning it back into your device.
However: since your new ROM is 4.00.16, you need to know there is a problem: you cannot use the normal upgrade program called "Programme A" to move away from 4.00.16. But you can use the option in the XDAtools to write your old old OS to an SD card using the XDA (all files on the SD-card will be erased in the process). Then you can boot the device in bootloader mode and press the center of the rocker switch to load your old OS.
My guess is you'll be almost perfectly happy with 4.00.16 though (at least happier than with any 3.x ROM) . Just be aware of the one remaining problem: occasional SD-card erasures have been reported by some people (they do not seem to affect everyone), so do not store valuable data on SD without backup.
I upgraded to 4.00.16 yesterday and still can't get GPRS to work. Sometimes it says it connects but I can't get to anything and other times it gives me an error trying to connect. I've been trying everything I can think of for GPRS settings. I'm on T-Mobile in Atlanta with Radio version 6.18.00. I'm not sure if you will have the same problem or not.
I had trouble connecting through GPRS too at one point where I thought it was ROM 4.00.16. But I finally did connect.
One of the major reasons for upgrading was an expected improvement in GPRS performance. If anything, it got worse. Do I have to upgrade the radio rom too for improvement in GPRS?
rfeagin:
I had similar problems following the upgrade, and as an afterthought I went to my local TMo store and exchanged my SIM chip. Mine was three years old, and the new SIM fixed the problem. Also, if you upgrade the radio stack to 6.24 or the AT&T stack, you will gain persistent GPRS connectivity.
David
SO the TMo store will swap sim cards with me if I go in and tell them I want a new one? Also... where can I find the radio stack 6.24 stack or the AT&T?
Thanks for your help. I really would like to get this working again.
I've heard that its very difficult if at all possible to downgrade the Radio ROM back to its normal state. This is why I have not done it yet.
I posted instructions in the following thread for locating and installing the 6.24 radio stack: http://xda-developers.com/phpBB/viewtopic.php?t=2452&highlight=. If you would like the AT&T files (I prefer the TMo files), send me a PM and I will help you get them.
Downgrading radio stacks is difficult, and maybe impossible in some cases, but as long as you have the four files listed in the referenced thread, it seems to work well.
David
I backed up my original ROM on an SD Card so I could revert back to it from 4.00.16. I tired to revert back today but for some reason the image is not on the SD card. Now what?
How can I get my old T-Mobile ROM back? Any ideas?
If you have a Card Reader, you can use XDATools to burn a rom image onto it, then use that image to reload your XDA via the SDCard method...
I just bought a SDCard reader from WalMart, for 19 bucks, it is a Lexar JumpDrive Trio, and it can read SD cards, XD CArds, and Sony Memorystick, and it is USB 2.0..
It is nice, albeit a bit flimsy..
But it works.
B
camarao said:
How can I get my old T-Mobile ROM back? Any ideas?
Click to expand...
Click to collapse
Yes, you can download it from here:
Current T-Mobile 2002 ROM Update:
http://www.t-mobile.com/products/handhelds/pocketpc/downloads.asp
Will upgrade to this version:
ROM version: 3.14.40 ENG
ROM date: 11/26/02
Radio: 6.18
Protocol: 324e4
HTH
camarao said:
I'm sick of waiting for an answer from T-Mobile on when WM2003 will be available for the PPCPhone Edition, if at all, so I decided to create an executable of 4.00.16 at Jeff's kitchen.
Click to expand...
Click to collapse
Is there anywhere the more adventurous among the non-linux population can try this baby?
Cato
Qman:
Are you saying that I will be able to download and install the T-Mobile executable over my 4.00.16 version?
camarao said:
Qman:
Are you saying that I will be able to download and install the T-Mobile executable over my 4.00.16 version?
Click to expand...
Click to collapse
I'm not sure about if the executable will work or not but if does fail you can always use the bootloader method!
I have a TITA100(Quest) that I am unable to launch EPST.exe on. I need to enter in the SPC # that I generated, but when I tap it to launch it reads EPST at the top for a sec but never leaves the file browser. I have also tried ##778(#), but the phone dials to a quest message service that says I am unable to dial this number.
I want to configure it for cricket.
Here is what I have done so far.....
Started with: Radio v. 1.39.00, ROM V. 2.13.656.2, Bootloader 1.2
Went to bootloader 2.40(via Hard-SPL-MF.exe), Scrosler's Titan ROM 3.26 w/touchflow. and then Radio 3.42.30.
Thank you in advance for any suggestions or solutions.
I got it to work after doing the using reedit to dump the code into a text file. I am not sure if that activated something, but it worked.
upsett3r said:
I got it to work after doing the using reedit to dump the code into a text file. I am not sure if that activated something, but it worked.
Click to expand...
Click to collapse
can you plz explain in detail what you did? i'd like to get into EPST again, so i can deactivate the GPS... it's killing battery... thanks in advance
phattboy29 said:
can you plz explain in detail what you did? i'd like to get into EPST again, so i can deactivate the GPS... it's killing battery... thanks in advance
Click to expand...
Click to collapse
So go to settings then phone the location and turn it to 911 only, GPS is now off. I don't think there are any gps settings in EPST but I could be wrong. And I run GPS all the time and have no problems with my battery life. I think you have other issues.
i may be wrong, but my Quest XV6800 didn't have the EPST.exe executable in it's original ROM (it's also in the Windows directry). i believe i flashed it to Alltel's stock ROM to get to it, and reset the SPC to 000000's. i couldn't get it into debug mode with the Quest ROM either
i have flashed many Moguls and the Quest ones are always the most peculiar...
i can't get epst to launch. i tried repeatedly starting it, using ##778 AND EPST.EXE in \Windows. I then soft restarted two or three times, trying both methods after each boot.
Is there any way to fix this? Otherwise, is there another way to enter the A KEY? I'm gettin an auth error when making calls.
rom 4.1.2 radio 3.42.50 pri 1.35_002
Installed DCD Verizon Carrier Cab from http://dcd1182.n715dp.com/index.php?dir=carriers and that allowed me to launch EPST via both methods.
Did not eliminate the need for a new A KEY.
Still kinda learning this stuff, I flashed everything OK, and now the GPS works with Garmin XT. This is on a "practice" phone, one that was kind of beatup that I could practice on before I flash my actual phone. I couldn't get EPST to work till I loaded the Verizon cab described below. Question is, will I have to load this cab every time I flash a new ROM, or does it have more to do with flashing a different radio ROM?
This is a great forum, I've learned a lot, and still learning. Thanks everyone.
Dale.
Some roms are carrier specific and have the info included. Most roms state that installing the carrier cab is necessary. This allows the same rom for all titans and then the user just adds carrier info. Just read the rom instruction better next time. Most list if the cab is needed.
I can sync and copy files like several of the cabs from this site to the phone Storage card or My Documents in the phone and when I try and run any of them I always get an Unsuccessful .
is the ATT Pure Application locked? I did notice that all the applications I am running are not digitally signed or signed by a trusted provider and the phone complains and ask if if I still want to run. I pick yes and it still fails.
Any thoughts? I know some of you have ATT Pure devices!
FIXED
I did this and all is working...
1. Deleted my partnership with my laptop (Win 7 64bit)
2. boot my ATT Pure
3. Connect but dont establish partnership
4. copy over the cab files you want
5. use file explorer on the Topaz (Pure) to run them
6. all works fine!
7. loading EnergyROM now
the lesson to be learned if it does not work for you and it works for everyone else then go back to the basics!
Welcome to AT&T... yes all branded phones are app locked because they want to force you to use their apps.
You can app unlock it using a cab install... but some new phones are even rejecting that.
Official and Custom roms are the way to go. I recommend everyone with a Pure to at least flash to the newest Official WM6.5 build. It will work just the same but be clean of AT&T junk.
I have an AT&T Pure
I have no particular problems with installing Cabs
As another poster said copy the cab to a temp directory
and run it from File Explorer (delete the cab to save space after its been run)
Or you can use "CabviaActivesync" availabele on this site which makes it a little bit easier. (but I did have two cabs that had bad setups and needed manual install)
Bottom line the PURE does not block most cabs (I've tried)
(I only had a problem with the write protected weathercity database now ok)
Chances are something is wrong on your Pure or your method
To the senior poster that replied
Hey I've made tweeks and played with the stock ROM
I'd love to clean the bloated and unused ATT aps
incorporate weather into the clock ( TF3D 2.5+++)
and get a cleaner start menu (too many aps)
and certainly see an improvement in performance and snappiness
Id love to try a new ROM
but most new roms are written for Diamond2/Topaz
I'm not clear if the radios are the same on the the D2 and the Pure?
Can I burn WM and TF3D without affecting the radio part of the code?
Are the any other issues we need to be aware before we burn a new Topaz rom
onto an ATT variant of the Topaz ?
Is there a copy of the original Pure Rom available in case we need to return
it to ATT (what else would we need to insure we could return to ATT to fix any other later warrenty covered problems)
Of course I realize there is a risk invilved,
but whats the best safety prep?
I'm new to phones but an old micro hard/firm/soft ware and PPC guy
Thanks in advance
KJL
I haven't had a single problem installing anything on my stock Pure. Even software that normally requires an app-unlocked phone installs just fine.
I'm also curious about what Kenn asked. I'm getting a Pure tomorrow and I won't be able to get the crapware off there fast enough.
Specifically, can I flash the official HTC 6.5 rom to the Pure without having to hard spl? Is is just a straight flash?
I have the same problem with this ROM: http://forum.xda-developers.com/showthread.php?p=5743820#post5743820
Everything is OK but installing the cabs.
When I try to install any cab it wrote me "Instalation of ... was unsuccessful."
I tried a lot of cabs and all of them are the same
Any help please?
.
This particular problem gave me 4 day headache last week when i couldn't figure out why I couldn't HSPL my Pure. Had to Hard Reset entire phone, everything worked
Yes, I also hard-reseted my phone yesterday and everything works now!