SMS Backup - MDA, XDA, 1010 General

This message contains all postings in this thread
dated before January 19th 2003
Subject: SMS Backup
From: Anthony Newman
Date: 26 Dec, 2002 20:08:08
Hi Folks,
Thanks again for all your great work on the site. I was just
wondering if I could pick your brains on an issue that's been
bugging me.
I've searched google with every possible permutation of this
query, and it astonishes me that no-one's covered it - have I
been missing something really obvious?
I'd like to back up my text messages. Inbox doesn't sync them
with Outlook, nor does it offer any kind of backup tool. Short
of copying and pasting the text, date and recipient of each
message into a text file or email, is there a database I can
backup and use?
The reason I ask is because I'm trying to cover every
eventuality for when I flash my generic Spaceneedle with the
T-Mobile ROM that was released recently. I've carefully
catalogued every preference, program and file on my device ready
for fresh reinstallation with the exception of my text messages.
I could, of course, do a backup with Sprite's excellent
software, but I'd rather not do even a partial restore of a
backup from an old ROM version.
Any ideas, folks? Many thanks in advance!
Subject: Oh, never mind.
From: Anthony Newman
Date: 26 Dec, 2002 20:37:18
Having studiously backed everything up, made note of all my
settings and got everything set up just perfect...
... the T-Mobile utility won't let me upgrade my device. I
receive a check error showing device differences, and the only
difference appears to be the following:
My model: PW10B1:100
The upgrade's model: PW10B1:002
Can anyone let me know what the differences between the numbers
after the colons are?
This is really frustrating, as in terms of actual hardware my
device is the same as the T-Mobile, and I'd love the increased
speed and stability of the new ROM. Any help?
Subject: Oh, and just another thing...
From: Ant
Date: 26 Dec, 2002 20:41:57
I'm aware that I can try flashing with the bootloader method,
but I wanted to check that there weren't any known issues first
Subject: To continue my monologue...
From: Ant
Date: 27 Dec, 2002 00:21:39
My update went perfectly well, and I now have the new T-Mobile
ROM working nicely on my generic Spaceneedle with my O2 UK SIM.
Even GPRS works as well as it used to (which is intermittent at
best). Thanks for XDArit!
Subject: ROM Hack
From: mike
Date: 27 Dec, 2002 07:15:31
I was able to hack a ROM file with a hex editor to change its
version number. The version number is found within the first 32
bytes of the ROM file.
You also have to alter the checksum which is a number also found
in those first 32 bytes... three or four hex digits. IT should
be fairly obvious, since
If you increment an ASCII digit, you must also increment the
checksum. Decrement ASCII digit, decrement the checksum. Since
you'll change a 1 to a 0 (-1) and change a 0 to a 2 (+2), your
net change is +1 and you must add 1 to the checksum.
That said, whatever this ROM does to your phone is your risk. I
already screwed up my T-mobile phone, granted that was due to me
flashing the US radio with a European update, this shouldn't be
so bad, but do cross your fingers.
mike
Subject: .nbf files in RUU upgrade
From: XDA developers
Date: 29 Dec, 2002 14:21:29
You'll find that the XDArit already supports reading these files
and parsing out the bootloader and WinCE image. (We ignore the
checksum, but write the correct one for the bootloader on the SD
card...)

Related

Storing Programms to Flash

This message contains all postings in this thread
dated before January 19th 2003
Subject: Storing Programms to Flash
From: ako
Date: 18 Jan, 2003 15:27:02
Hi everybody, hi XDA-Developers,
just found today this really cool site and must say: great
rewards for you!
Am really happy to find a way, to backup my MDA.
Had a Palm before my MDA and that was so cool, to control most
of the things you can do with a PalmOS, with the Flash and so
on.
But now to my question: has anyone found a way to store
programms in the 32MB Flash of the MDA/XDA???
Would be greatful NOT to loose the installed programms, when
changing my SD-Card (i have stored most of the programms on the
card, to leave as much RAM as possible for working).
Would be cool, if anyone can help with this and post his/ her
experiences.
Have a nice day,
ako
hi everybody another time ...
just asked some weeks ago, but no answers.
think it's interesting for all of us. perhaps now there is someone who solved the puzzle???
cheers ako
24MB of that space is used for the OS, so you can't use that. The remaining 8MB could be used with the right software. HP includes that with the Jornada, called "Safe Store." I found it very nice to have when I had a Jornada. Unfortunately, the PPC ROM files seem to be protected so they can't be copied. Anybody know a way around that? If so, I can copy this from a friend's Jornada.

Home-cooked 1.72.902 upgrade package (1.72.00/1.17.00) T-Mob

I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
8-11-2004 20:57 GMT: New version V2 uploaded.
I added a small archive containing the changed ExtROM files to solve the earlier reported errors (not updating ExtROM version and not making IIWPO un-installable).
Comment on IIWPO and making it un-installable: After having customized & installed IIWPO, you will have to do one of the following to make it un-installable if youre using the 1.72.902 ExtROM:
a. Another hard-reset
b. Running Version_172_902.cab from the ExtROM
NOTE: This thread is being replaced by
http://forum.xda-developers.com/viewtopic.php?p=68652#68652
Thank You!!!!!!!!!!!!
I am d/l'ing right now and will be installing shortly...
One request... You might want to include the cab for setting up IIWPO in case someone is installing it into the phone.
edsub Thanks.
Question tho. Can I use this for T-Mobile USA and does it fix the MMS problem ?
asking because the version says NL, isnt that the Netherlands country code ?
Thanks again
Well from first look everything seemed ok.
THese are a few of the things I have noticed since loading.
1. The ext rom version # doesn't show up in the info
2. If you use the IIWPO then it still shows in the remove list
3. The new apps from the 187 version will not install no matter what you do. (I have tried adding the ver # in the Reg, both 902, and 187 (not at same time)) Niether worked.
These are the few things that I have found since loading. If I find any more I will loet you know. Other than these I think you havea winner here!
I was wondering about the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 packages, and why you didn't include or update to them? Was there some incompatibality issue?
Thanks and great job!
Re: Home-cooked 1.72.902 upgrade package (1.72.00/1.17.00) T
edsub said:
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
Click to expand...
Click to collapse
Is SRS included?
SRS is not included due to the fact that I don't see any use for it personally. Since it is an ExtROM installer, you could add it yourself.
The NL is only there because some sdetting are more or less specific to the Netherlands. I had feedback on my earlier 1.72.901 package that it worked for other countries (incl USA) as well. Be prepared that the date format will be dutch by default (easy to change via settings though).
Also MMS is suposed to be working (but I have not tried it due to lack of interest in MMS)
The ExtRom# is not showing because some bug in the Version_172_902.cab. Working on that now.
IIWPO not showing in the remove programs list is a bit more difficult than it seems if you install for the first time. Normally you would boot up the device with new rom. IIWPO is NOT installed at this point. Once you have customised & installed IIWPO, you will have to do ANOTHER hard-reset (ie run the ExtRom contents again) to disable the uninstall. You could force this by hand first time to re-run Version_172_902.cab after installing the customised IIWPO. BUT as this cab is not OK, it wont work anyway. Working on that now.
I did not find the time to look into the new O2 apps. If someone finds a solutiuon here, I am more than happy to includew it in a new version.
For the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 the basic reason is lack of time. I dont know what 'extra' new there is on bluetooth in the O2 builds? OS Rom 1.72 allready has an updated BT stack that fixes most open issues. I have no experience (& interest) in MMS / streaming MMS . . .
I suppose the issue with TomTom locking up without GPS enabled is not solved with this rom ?
I know: wishful thinking..........
@Pleun: Nope. I WISH I would have solved that one!!! FYI: I tested he new TomTom GPS 3.07. It doesnt solve any locking issue and next to that makes my Headset react very slow. Also the 'Bluetooth GPS' option that is supposed to solve the locking has gone, at least with my installation. Not advisable. I reverted back to TomTom GPS 3.03.
@all: I solved the issue of not setting the Ext Rom version and making IIWPO non-uninstallable. New version V2 will be up in 10mins (incl. incremental fix for all that downloaded the version from yesterday).
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
edsub said:
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
Click to expand...
Click to collapse
I feel like my MDA2 is a little bit slower to respond not sure why! I added PocketMVP, Belkin Bluetooth GPS, Resco Explorer 2003 V5.0 and .NET Compact Framework 1.0 SP2 for Pocket PC 2003.
I am having problem with Belkin BT GPS; I got it to bond, detect the COM port (COM5) and baud rate(4800) to use but my MDA2 hangs up and had to soft reset. Any idea why?
I will try to install one by one and see what's causing it and report here.
edsub thanx for me it works great its a great improvement!
machine seems faster and no more lock-ups.
Keep up the good work (ill be following you)
p.s only one thing my battery seems to give me no more than 4 hours of on-time
4 hours is very different from my (and others!) experience. The 1.72 rom should even improve battery life.
My battery lasts for about 1,5 days (not measured but recalled from my memory) with approx 1-1.5 hours on the phone and bluetooth permanently switched on . . .
were can I download this rom from?
from the first msg in this thread : RUU172902WWE_eDsuBsofT V2.exe
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Anonymous said:
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Click to expand...
Click to collapse
You cannot download it as a guest! If you are a member of this forum you have to log-in before you can see the file you want to download. That's what I encountered before so just try logging in first.
Good luck!
THank you very much superperry. Should have registered before but was always too lazy.
I have put together rom upgrade 1.72.903
This thread can be closed. See http://forum.xda-developers.com/viewtopic.php?p=68652#68652 for the new one
Edit: The new upgrade files are now available (see refered post)
An error need help please
I downloaded the files then followed the instruction below but now I get error
the flashing process
first the devicedata is obtained from the device, with HimaGetDeviceData.exe, this gets the operatorname, and language/country code from the extended rom, sector 2 of the BDK.
Then a tool 'HimaClearJumpCode' is executed, which erases the jump at the start of the kernel. causing the bootloader to start at next reboot.
the upgrade tool then connects to the bootloader of the xda, via serial over usb. ( port \\.\WCEUSBSH001 )
warning do not just run the 'HimaClearJumpCode' program, it will erase part of your OS rom, after which you will have to repair your device by running an entire upgrade again.

SMS displaying received phone numbers instead of names

I have problems with sms displaying received phone numbers instead of names. I have tried soft & hard re-set but it still shows phone numbers insted of names from my contacts.
can someone guide me how to fix this problem. also if i need to upgrade ROM please guide me with the link where to upgrade ROM
following are the current specs.
WALABY
MODEL SIEMENS SX56
ROM VERSION 3.17.03 ENG
RADIO VERSION A.20.10
PROTOCOL VERSION 324e4
Help is desperately needed
Thanks in Advance
Aamer Sheikh
E-mail: [email protected]
This is an old fashioned Problem with the PocketPC 2002 ROMs. There is an fix from Paragon Software. You can get it there for free....
OR it´s fixed in the WM2003 ROMs.
You can cook your own at http://lumpistefan.dyndns.org/
HTH
Stefan
Hang on though - you have rom 3.17 which should have that fix built in.
My guess is that your mobile numbers aren't stored in the mobile number field within Contacts. Cut and paste them over and all should be well.
JD
You'll find the fix here:
http://www.yorch.net/apps.htm
Its called Paragon Software SMS Name Fix
Or download the file directly from here:
http://www.yorch.net/downloads/SMS fix.zip
8)
Problem may be that mobile numbers in contacts have to start +44 (in the UK) and drop the leading zero.
May also need to load them into SIM using SIM manager (not sure on this point!).

[RESOLVED] ROM Version/Date Relocated

I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
I'm not really sure what could be wrong, but if you need the dump set up for Visual, I had no problems dumping it and uploaded the untouched "Kitchen" to my FTP. Its labeled correctly as the build number 5.11.xxxx. I wish Icould help more, as you have helped me out a bunch.
EDIT: I did dump a ROM recently and got the same Version ID with xipporter as you have mentioned, but thought nothing of it. And I dont remember which it was, so sorry still not very helpful.
The ROM Version "garbage" is odd and IMHO should not be like that - your confirmation that you saw the same thing is very helpful ... at least I'm not losing my mind completely.
I'm trying to keep a PkgToolsBuildOS (5.3) and a Visual Kitchen (9.8) going for folks to use.
I had gone through all of the effort to port 21051 (SYS) and 20771 (OEM) in the hopes of posting it up before the end of the weekend ... then I started running into these unexplained issues and ended up scrubbing the lot.
I'm in the midst of recreating a new Visual Kitchen (9.8) and am discovering additional files in the OEM folder that weren't there before in older versions of the Visual Kitchen - not sure what it means yet; sure hope it doesn't mean having to recreate a kitchen everytime there's an update to the tools.
Cheers,
hilaireg said:
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
Click to expand...
Click to collapse
Several of the new builds are this way. Its because the date info has been moved. Until someone figures out which part needs hex edited we are stuck with stock dat Version changes fine.
Are you saying that we should *no longer* be changing the ROM Version and ROM Date?
In my case the Date "looked" ok but the ROM Version was bogus.
Which leads to these questions:
Does this also mean that PagePool Unlock, NoCert Patching, PagePool sizing are also in jeopardy of moving? (I know you or others won't have an answer for this one as it's in the hands of the OEM).
Does this mean that PkgToolsBuildOS kitchens and supporting tools are now at end-of-life?
Hate that when I forget to read the memo
UPDATE
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
hilaireg said:
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
Click to expand...
Click to collapse
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
B4PJS said:
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
Click to expand...
Click to collapse
The PagePool seems ok on my 6.1 builds at the moment but Da_G could best confirm that as he's been on this "circuit" way longer than I.
An observation I made, while I've been working on this, is that the PP size on the AT&T 5.11.502.2 seems to be set 1MB ... at least that's what XIPPorterEX 1.2 rev32 reports when I issue a change to the PagePool to 16MB on a non-reduced ULDR os.nb.payload.
Hmmm, Wonder why when I change my PP to 0 I still only have 197mb Total instead of about 213mb total? Might have to do a test and set it higher to see if my free space decreases
UPDATE: Direct From Da_Grand Pubba ...
Just had a quick chat with Da_G and he confirms that there's been a change in the XIP modules.
At first glance, he noticed that the NK.EXE module has three (3) new resource strings. So in short, if the ROM Version happens to display [K] InitDr (which is [K] InitDriverGlobals) DO NOT attempt to change the Date/ROM Version.
He also had a quick look for Certificate Patching, PagePool Unlock, and PagePool resizing - these appear to be untouched at the moment.
HTH,

[Q] Blutooth Receving Issue

Hi,
I am new to this forum, I am having a problem in my mobile Bluetooth receiving mechanism for which I need your expert opinions.
The problem is that when someone (either through PC / mobile) send multiple files through Bluetooth to my mobile I have to accept each number of files separately by going again and again in the notification area and after clicking the file and click 'accept'. In short if someone send me 5 files I have to go to the notifications 5 times and have to click accept 5 times as well.
I want to know is this the standard feature or I have some problem in my set? I am not using any apps for this purpose just using the standard feature of the set.
Kindly help me in this regards.
Following are the details of my Android Set:
Set Name : Star A5000 Android 2.2 Dual Sim
Model Number: e1000_pxht2 2010/11/16 11:8:23
Android Version: 2.2.1
Baseband Version: MAUI.10A.W10.48. 2010/11/29 22.57
KERNEL VERSION: 2.6.32.9
[email protected]#1
thu Dec 16 14:03:12 CST 2010
Build Number: ALPS.10Y.W10.48 p27.MP.VO
thats just how Bluetooth file transfer works bro. You could zip up the files and just unzip it when you receive them.
I have checked the same feature on another Samsung android phone and the phone receive continuously all the files without separately accepting the files in notification area.
yeah well Samsung is crap anyway so don't be mad you don't have a Samsung its just the Bluetooth that ya got and the company that made your os hasn't enabled all the bells and whistles its probably a dated most general version available. Nothing you can do other than check out the different apps if there are any availble. Or archive the files and unzip them so you only have to do it once. I don't know much about the device you have but not everything is capable of doing 100 things at once. Patience my friend patience.
If anyone know please answer the question.....
Question: are those sending devices already paired with your phones ?
Try 1: Mark the sending device as "trusted" after you pair (might depend on your device how to do it in the bluetooth settings), this way no further notice will appear in accepting the files that you are getting from the other phone or pc.
Try 2: Use a 'folder browsing' (not 'object push') profile for transfering files.
Take a look at this neat program to handle bluetooth connection from your PC, I find it really useful (free & lightweight & works)
ObexCommander

Categories

Resources