Yikes! Sounds like the German 4.00.33 production release has the Windows Modem firmware on it. There's been a number of discussions in the past about how the radio hooks in WM2003 meant that the previous way of patching the modem firmware into a ROM wouldn't work.
Does this development open the door for some enterprising young geniuses to patch the Windows Modem into the existing widely available 4.00.xx ROM versions?
Also, the hooks that were required for the modem to work were similar to the hooks required to make SIM unlocking work. See where I'm heading here? Perhaps a 4.00 based ROM that unlocks?
Related
Hi
I downloaded the rom update from o2 website in ireland and tried to install it, it the told me that i needed to find a compatible version any ideas any 1. I am running the Q-Tek XDA same thing just branded differently. Also my unit has ver 3.14 on but i cannot find function to keep gprs online. Please assist
Thanks
Waiman
I have exactly the saeme problem. MDA is PWA10A2, the update is for PWA10A1 and thus doesn't flash. (except for radio which I updated already).
You can use the ROM Image tool from here, it needs a 32MB SD card and a PC SD card reader but it is supposed to be risky.
Anybody tried updating to this ROM on PWA10A2 before we burn our machines? >
Get your self a FAQ with a description for a language change. Then patch that file according to that FAQ, do not change the language but the phone type. that's all.
** Remember, you might loos guaranty, it might fail or your device might get broken ! **
Can I revert to the older ROM (the working ROM) then? The bootloader should work anyway?
I can't see the FAQ though, is it PPC general or MDA/XDA specific?
I patched the ROM (rewrote the desired ID of XDA to match with my MDA ), flashed and... guess what... it works
Let me apologize if someone has asked this before (however I did search and found nothing). I also want to apologize if I sound stupid - I'm incredibly new to all this technology.
The Device: I have a "Siemens SX56" which I now know has many other names (thanks to this website). My ROM version is R.20.11 ENG dated 06/05/03, my Radio version is A.20.10 and my Protocol version (don't have a clue what it does) is 324e4. My wireless GSM carrier is Rogers in Canada.
The Problem: I wish to upgrade the device from Pocket PC 2002 (currently installed) to Pocket PC 2003. Microsoft only allows the manufacturer to provide this upgrade. Siemens does not have an upgrade for this device for people using the Rogers product in Canada. They do however have the upgrade available to AT&T subscribers in the U.S.
The Questions: Does anyone know if I can use the Siemens AT&T upgrade without any problems? What differences are there between these products? I noticed that my ROM and Radio versions were not included in the profile list (they must be fairly unique) does anyone have any familiarity with them and if so, how are they different from the newer versions? Can I update my ROM version to something less unique and still retain my wireless GSM carrier? Siemens and Rogers have been thoroughly unhelpful.
Thank - you for all your help.
It is so easy to upgrade to 2003.
Over hundreds posts are in the forum about upgrading to 2003
If you still cannot get it, contact me to help you. I'm in Toronto, Canada
thanks cgigate,
I too read MANY messages in this forum about upgrading to 2003 but haven't found anything that dispels my concerns about upgrading a phone with Rogers AT&T as the carrier.
Can you provide a link? What file(s) should I be looking for?
Also, a couple of other things...
1. Is there a way to backup my SMS messages before the upgrade and then restore them after the upgrade?
2. Has anyone found a solution the the "increasing ring" or volume clipping that was included in the new ROM's?
Thanks again! PS. I'm in Mississauga.
Rogers is my concern
Thanks Cgigate,
My concern is the same as Guiness.... how will the update effect a Rogers phone? The Siemens website clearly states that the upgrade is NOT for a rogers phone so I'm a little concerned. I did search the forums for any information on this and found nothing to this specific issue. Any help would be greatly appreciated.
Thanks again,
Sean
P.S. I'm in Markham/Toronto.
Update
Well, Siemens finally posted on their website an upgrade for WM2003 for the Rogers phones. You can find it here: http://www.my-siemens.com/MySiemens...C%2FMC%2FSX56POCKETPCPHONE%2Fdanda%2F,00.html
I downloaded it and followed the instructions. The Radio Stack was upgraded successfully, however, the thing pooched during the ROM update. Phone is dead - won't turn on at all. I contacted the Rogers guy I bought the phone from and he has sent it in to get reflashed.... crappy!
Hey senmc,
I just followed your link to the Siemens upgrade for Rogers users in Canada.
I did the download, full upgrade (Radio Stack and OS) and it worked flawlessly!
I'm up and running without any problems... except, of course, I am having the same volume issues that everyone else has written about.
I just went to the Siemens site.
It says..." the upgrade is no longer avaliable"!!!
Does anyone know where else can I find the upgrade?
Try this link:
http://downloads.rogers.com/wireless/products/phones/siemens/Siemens_SX56_Software_Upgrade.exe
Here is the update to WM2003 directly from Rogers.
(I've got some problems with this ROM used in the ROMkitchen. But in the original format it should work fine....)
For further Informations you can take a look at :
Stefanhttp://forum.xda-developers.com/viewtopic.php?t=9563&highlight=rogers
HTH
I tool the big leap! It was met with success. Was able to upgrade my Vogue to Rev A/GPS using the Sprint rom. Everything went fine. No issues. The advice I received was most helpful as well as the read me notes that was included within the file. YOU GUYS ROCK!
Now, the real fun begins. Finding a mapping program to use with the GPS. I ran across a rom that requires the user to install a program that will install the 3.37.15 radio version. With the new upgrade to my unit the current radio version is 3.42.30. Isn't this considered a downgrade? Wont it create hardware issues? Feedback is appreciated.
Might want to put this in the correct fourm. This is for the Juno aka TMobile Shadow. The Vogue is a different unit.
Now from a general Radio standpoint, yes technically it would be a downgrade of sorts to go from 3.42.30 to 3.37.15. While it may be considered a downgrade it may be better to use one version over the other for performance issues. I know that on my Wizard, Radio 2.40.11 worked better than any of the newer versions fr use with TMobile in the states. Some people had better luck with other Radio versions using Cingular\ATT in the states and others with different versions in different countries with different providers and so on. It is all a matter of which Radio works best with your ROM\Carrier\Location.
Hello guys,
First of all Happy new year.
I just got a Samsung Tab and I am learning on it (how to ROM...etc...)
But since it is my first device (android) I would like some help from you
anywhere I can find some tutorials...help ?
what is ROm and what's the difference between ROM and Firmware
what is CSC ? is JPJK2 the latest version ? how ? where ?
thanks a lot.
Pierre
@Pierre. What country are you in, what mobile carrier do you use and what's the sales code on your phone? No one will be able to give you ROM version advice without these basic details.
ROM and firmware are the same thing, people use the names interchangably. The ROM/firmware is the usually seen as the PDA version thats on the device as this is the Android operating system. The devices also have modem software and the CSC (customer specific customisations). The modem code contains drivers for the modem (ie data and voice), WiFi and (afaik) bluetooth. The CSC contains vendor specific applications and mobile network connection details (eg. APN settings).
Have a look around in this forum and in the Samsung Galaxy S forums for tutorials / advice etc and enjoy your Tab!!
If I've given any bad information above, could someone who knows more please feel free to correct me!
I had a chance to flash to 7704 today and had to update the phone to restore my backup so I ran fiddler to sniff out the cabs. Here they are:
Code:
http://download.windowsupdate.com/v9/windowsupdate/redir/muv4wuredir.cab?1112010406
http://download.windowsupdate.com/v9/microsoftupdate/redir/muauth.cab?1112010406
http://download.windowsupdate.com/v9/microsoftupdate/redir/muv4muredir.cab?1112010406
http://download.windowsupdate.com/v9/microsoftupdate/redir/muv4muredir.cab?1112010406
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/02/diff-7.0.7004.0-7.0.7008.0-armv7-retail-microsoft.pks_fe49cc6a5f39389728a769f9013dcd491bd65168.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/03/diff-7.0.7008.0-7.0.7355.0-armv7-retail-microsoft.pks_7fea4585c1275be10e4c06adffb3c4e42372f7d2.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/03/diff-7.0.7008.0-7.0.7355.0-armv7-retail-microsoft.lang_0409.pks_65fe09539f02edc8e1d44609fb537b87613063ea.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/01/diff-7.0.7355.0-7.0.7389.0-armv7-retail-microsoft.pks_35616816bdd0b9c08e39cdbab9fc9f7bfafec5ac.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/01/diff-7.0.7355.0-7.0.7389.0-armv7-retail-microsoft.lang_0409.pks_0cdfd833159cd10036e6025ec1db784dd712b2f4.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/03/diff-7.0.7389.0-7.0.7390.0-armv7-retail-microsoft.pks_669700d5014b3a9c73fe81390281620ca29d0675.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/03/diff-7.0.7389.0-7.0.7390.0-armv7-retail-microsoft.lang_0409.pks_b4e3f25a79cfd5514895169ba167d9bd0cdb135d.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/04/diff-7.0.7390.0-7.0.7392.0-armv7-retail-microsoft.pks_3a3a18fff5252d787974a169b115f8b428c0566c.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/03/diff-7.0.7008.0-7.0.7355.0-armv7-retail-microsoft.pks_7fea4585c1275be10e4c06adffb3c4e42372f7d2.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/03/diff-7.0.7008.0-7.0.7355.0-armv7-retail-microsoft.lang_0409.pks_65fe09539f02edc8e1d44609fb537b87613063ea.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/01/diff-7.0.7355.0-7.0.7389.0-armv7-retail-microsoft.pks_35616816bdd0b9c08e39cdbab9fc9f7bfafec5ac.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/01/diff-7.0.7355.0-7.0.7389.0-armv7-retail-microsoft.lang_0409.pks_0cdfd833159cd10036e6025ec1db784dd712b2f4.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/03/diff-7.0.7389.0-7.0.7390.0-armv7-retail-microsoft.pks_669700d5014b3a9c73fe81390281620ca29d0675.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/03/diff-7.0.7389.0-7.0.7390.0-armv7-retail-microsoft.lang_0409.pks_b4e3f25a79cfd5514895169ba167d9bd0cdb135d.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/04/diff-7.0.7390.0-7.0.7392.0-armv7-retail-microsoft.pks_3a3a18fff5252d787974a169b115f8b428c0566c.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/custom_diff-7.0.7392.0-7.0.7403.0-armv7-retail-microsoft.pks_5787b956938cb2b6d09892934b38dd9fd88f25ab.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/canonical-7.0.7004.0-7.0.7403.0-armv7-retail-microsoft.lang_0409.pks_04973d3358abc8524cca292e5ff43f71ac0a0b01.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/custom_diff-7.0.7392.0-7.0.7403.0-armv7-retail-microsoft.pks_5787b956938cb2b6d09892934b38dd9fd88f25ab.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/canonical-7.0.7004.0-7.0.7403.0-armv7-retail-microsoft.lang_0409.pks_04973d3358abc8524cca292e5ff43f71ac0a0b01.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/08/407216_venuepro_qisdaupdatepks_gleos2a_us_tmo_signed_swv0219_lp0030_rv001_retail.pks_c13ae38ec4ab63aeb46ee1f7bbee3ab878390112.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/diff-7.0.7403.0-7.10.7720.68-armv7-retail-microsoft.pks_af342c3af8880359d4ecffac3bf17c8e2e586599.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/diff-7.0.7403.0-7.10.7720.68-armv7-retail-microsoft.lang_0409.pks_ef46131182d8294904ede76983dc9c58e63e245d.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/diff-7.0.7403.0-7.10.7720.68-armv7-retail-microsoft.dpi_262.pks_268000b46b0dad9d5d51ce762ee73e5e4ae1f341.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/08/407216_venuepro_qisdaupdatepks_gleos2a_us_tmo_signed_swv0219_lp0030_rv001_retail.pks_c13ae38ec4ab63aeb46ee1f7bbee3ab878390112.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/diff-7.0.7403.0-7.10.7720.68-armv7-retail-microsoft.pks_af342c3af8880359d4ecffac3bf17c8e2e586599.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/08/407216_venuepro_qisdaupdatepks_gleos2a_us_tmo_signed_swv0219_lp0030_rv001_retail.pks_c13ae38ec4ab63aeb46ee1f7bbee3ab878390112.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/diff-7.0.7403.0-7.10.7720.68-armv7-retail-microsoft.lang_0409.pks_ef46131182d8294904ede76983dc9c58e63e245d.cab
http://download.windowsupdate.com/msdownload/update/software/dflt/2011/07/diff-7.0.7403.0-7.10.7720.68-armv7-retail-microsoft.dpi_262.pks_268000b46b0dad9d5d51ce762ee73e5e4ae1f341.cab
This was for my T-Mobile Dell Venue pro. You will notice I did not include the 7740 update as the update was not official.
Thanks, that's the 219-33 driver cab. (33 is tmo)
One down; many, many more to go.
Wonder if anyone has the link for the 219 US and EU cabs.
Hopefully this helps. I was one of the people who waited a long time to receive my DVP after ordering it from Dell. So it came with '7392' installed. The phone is locked to AT&T, and due to their combined "support" , the first update rolled out to us was 7720. This is the cabs sent in that session. Captured with Fiddler.
Peace.
That's exactly what I was looking for in my other thread (which links to this).
Hypothetically, someone on the same level rom (7720-8107) should be able to install this over their 00-US/00-EU/33-Tmo rom and turn it into a 31-Att device.
there's no point obviously, if we got a 00-US/00-EU bundle you could hypothetically turn it into that.
What we need is someone that has previously flashed the 7704/33-Tmo FFU to try pushing this with cabsender. I say after having used the FFU as there's no way of knowing if it'll work or simply brick your device. If you've already done the FFU install you could (hopefully) do it again if it bricks it.
Strangely enough the 31/att one includes a "TMobilePageOnce.xap". the att version's the rarest, so they likely didnt bother putting much effort into recustomizing it.
Edit: wait a second, the 33/att one is different from the normal ones.
The Att one is a "1A4" submodel and the others are "2A4", flasher beware.
It's also built later, the other 219's date to aug 22nd, and the att one is oct 4th.
Could you post your firmware version? is it: 2250.1800.7720.219? I dont know offhand how to manually find it in the cab
Here ya go. This is all the info (excluding what you already know from my previous post) referencing your thread: http://forum.xda-developers.com/showthread.php?t=1479233 (Can't reply to that one yet).
Firmware revision: 2250.1800.7720.219
Hardware revision: 112.576.2.0
Radio S/W: 2.2.50.18
Radio H/W: 8250
Bootloader ver. 7.27.1.0
8GB version
Always has been locked, and locked...
I was referring to this one specifically: Seeking anyone that hasnt updated their non tmo VP, but hey results are results.
I'm really curious what the 00-US and 00-EU ones are now, as there's a 1A4 and 2A4.
I believe both 00's are 2A4's though.
Wonder what the differences are, as your bootloader ver is the same as the other models,
I'm not aware of any firmware updates (baseband/dsp/modem) being pushed over an update.
The update bundles dont seem to contain them (or if they do they're not obvious).
It's unfortunate that the cab names include their sha-1(?) hashes, otherwise there's the (very small) possibility of simply guessing at the filename until you find it.
How did you purchase your VP exactly? Did you buy it yourself or is it a 2ndhand purchase?
I was able to get mine unlocked and I bought mine off ebay.
I just had ownership transferred to me, told them that tmo explicitly was unable to help me (as mine was tmo locked) and requested the code.
A couple phonecalls and emails later I got my code.