The SD card erasure issue is really bugging a lot of us and I just read that
someone is experiencing SD card erasures in the XDA II!
Here is the post ( there are some unique characteristics):
http://xda-developers.com/forum/viewtopic.php?p=18204#18204
I would like to have a reality check on my "feeling" that these erasures happen because of code in the RIL and how the device recognizes the SD card.
Since the RIL function in PPC 2002 and 2003 function resides in the " RILGSM.DLL inside DEVICE.EXE, which is a process which is always active on Windows CE, PPC 2003 and 2004. For the application part another DLL called RIL.DLL is present which translates RIL API calls to device IOControl messages.This DLL in turn is used by higher level APIs such as CELLTCP.DLL (TAPI Service Provider), CCOREDRV.DLL (the SIM: and SMS: device driver) etc. The RIL.DLL itself sits on top of the serial port to the GSM Device (COM2.
It is possible that the RIL on our the new RSUs are creating a new ID for the SD aspects our XDAs. So has anyone compared the RSU, RLI from PPC 2002 and WM 2003?
I have been using tstril to monitor how the RIL can be of use, but I need some help 'cause I may be focusing on the wrong areas.
If we resolve this all our ROMs will be much more stable and we may even help the providers to release their ROMs officially! :roll:
Possible solution.
Ok, Sorry for the non techies here, but:
I hope someone at TMO or AT&T with RIL and RSU access can validate, test and correct this issue and save a lot of its customers the aggravation of lost data.
Since there are no SD card issues with non phone WM2003 editions. I figured the issue had to be related to the RIL and RSU. I used 6 devices with different ROMs and ran the same tests coming up with similar results with "erasures" happening when the RIL was updating itself.
Since I do not have access to the code and the API and do not want to reverse engineer the code and breach your IP. I am posting it here.
You can monitor RIL functions and calls by using a modified tstril found in this site.
The problem with SD erasure is caused when WM2003 RSU files are trying to share the same memory address, handles and I/O MRUs list calls the SD cards are using.
According to the patent on the RIL. The native RIL device will always superceed a PnP device(SD card, GPS and others), renaming it and causing the erasure of file allocation tables with certain cards. Albeit the files are still there the card seems erased and data is not accessible by current software.
This problem is compounded by of your native code that does the same thing within SMS and Bateery Monitor.
I tested this in PPC2002, WM2003 all versions to date. I have attached the the registry settings for PPC V3.0.12039 ( build 11178) with ROM v3.14.40 ENG, RSU 6.18, Protocol 324e4. In which no SD card erasures are occurring. Monitor how the RIL interfaces with the RSU on this and the issue should be resolved.
[HKEY_CURRENT_USER\Software\Microsoft\File Explorer]
"LastLocation"=dword:00000000
"LocalPath"="\\My Documents\\Templates"
"StorageCardPath"="\\Storage Card"
[HKEY_CURRENT_USER\Software\Microsoft\File Explorer\MenuMRU]
"MRUList"="bdac"
"b"="\\My Documents"
"c"="\\Windows\\Start Menu\\Programs"
"d"="\\Storage Card"
"a"="\\"
[HKEY_LOCAL_MACHINE\Drivers]
[HKEY_LOCAL_MACHINE\Drivers\Active]
[HKEY_LOCAL_MACHINE\Drivers\Active\29]
"Hnd"=dword:00097820
"Name"="DSK1:"
"ClientInfo"=dword:00000000
"Sckt"=dword:00000000
"PnpId"="UNKNOWN_MANUFACTURER-"
"Key"="Drivers\\PCMCIA\\SDCard"
[HKEY_LOCAL_MACHINE\Drivers\Active\08]
"Hnd"=dword:00078480
"Name"="RIL1:"
"ClientInfo"=dword:00000000
"Key"="Drivers\\BuiltIn\\RIL"
Related
Ok, i konw there's already been several threads here about downgrading from the wm2003 rom (4.01.16ENG from the rom kitchen to be precise) but i can't seem to get this thing anywhere... as i said i upgraded the rom to the one specified above and found it far slower and unstable than the ppc2002; I wanted to flash the xda with the old rom but there's this strange communicate saying that the connection has been suddenly closed and the "programme a" stops. i tried to flash the old rom directly to the device using the xdatools but also with no success... it keeps on saying that it couln't communicate with the remote application... well then i thought about this bootloader fix (still unsure what bootloadre i have because i can't get the info anywhere) and it said that the memory on the device is write protected.... :/ well, and as for now i am waiting for a sd card to try that, but.... tell me, will the xdatools prepare the card if i insert it into the device? (i have no card reader for my pc) i am woried because each action i take (except normal device usage - activesync, copying and moving files, installing appz) that messes with the roms, shuts down the connection and i have to unplug the device from my pc and plug it again... please help me, i'm in dire need!
I am having a similar problem with the same rom version. I wish i never used that version! I did an update to wm2003 earlier and i could go back and forth with no problems, but this one is a real nasty one!!
the message i get when using osimagetool:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
I am having the same problem ..
and when i power on/off the device it says (Unrecognized Card)
Enter the name of the device for this card. For information, see the card manufacturer's documentation.
and there is a place where i can write something (Unknown card in socket 1)
m112a said:
I am having the same problem ..
and when i power on/off the device it says (Unrecognized Card)
Enter the name of the device for this card. For information, see the card manufacturer's documentation.
and there is a place where i can write something (Unknown card in socket 1)
Click to expand...
Click to collapse
YES!!! Same here!!
How about the phone? I cannot seem to turn it on. When the pin screen comes up it says i should turn on the phone, but i cant dothat anywhere..
Hi All,
The best option for ROM upgrade is always the SD method ... it's much easier and safer. XDAtools doesn't work with some ROMs because of the boot loader version not the ROM itself.
So what do you say guys? will i be able to downgrade it from the sd card? - and first of all, prepare the card having it inserted into the xda itself and using xdatools? i also wish i had never used it, the newest ppc2002 rom from o2 is just soo cool comparing to the wm2003 one i'm stuck with right now...
OK. This will have to be short and by memory but the good news is the details are all here in the forums. Thanks to everyone for the bits, I just stitched them together after spending hours of experimenting with my useless SX56.
After using the PPC 2003 on my ATT SX56 for a number of months I decided to dump it and go back to the PPC2002 version. I had problems with battery life, ring volumn, reception, dropped calls and some of my application would not work.
I was successful in using the ATT SX56 upgrade on the Siemens site once. I did it a second time because I was unsure if some binaries got loaded (it appears that this image does not have the standard ActiveX controls which I got elsewhere).
During the second install everything went wrong. I was left with a dead PPC with no useful ROMS. Period. All I could get to load was the Wallaby 5.15 bootloader.
So this is what I did. Note only try this as a last resort before sending in your PPC PE to Siemens for a reflash as I was about to do. This may work for other carriers but you will need their versions of the files mentioned here.
ONLY DO THIS IF YOU ARE GOING TO THROW YOUR PPC AWAY
Brain Dead PPC with GSM Error and no ActiveSync
First you will need a SD reader/writer for your PC and and SD card. This first step will give you a somewhat usable ROM for the PPC side. We will deal with the GSM side in a bit.
First get hold of the Siemens PPC 2002 update and install it on your PC. (it will probably fail to your PPC since if you are reading this ActiveSync won't work, if it does you probaly don't need to read this thread)
It will probably hang on the warning screen. If it does just go to the task manager and end it. All you want at this point is the files anyway. They will be installed in Program Files\SX56 Upgrade utility
Get a clean SD card and copy the NK.nbf file from the english subdirectory to the card. Stick the card in your PPC SD slot and get the bootloader running. (soft reset + volumn button). It will load a new ROM into memory after you select the action (rocker switch at bottom of PPC).
After this you can softboot the PPC. It will probably ask to reformat the SD card. Let it do that as you don't need the NK file anymore and you will need a clean SD card.
PPC without Start Icon and no GSM
Now your PPC won't have a start icon and you will also not be able to use the pointer as the PPC will not have performed setup. Don't even try. All you can do is bring up the contacts and calendar to frustrate you.
Next we will get the repair.zip file (search for it in the forums). While it is made for the XDA we will use it only to give us back a functional PPC. Follow the instructions to copy the subdirectory and file to the SD card and reset the machine.
1% Problem
You will now find yourself at the famous 1% problem but you will have a Start icon again, which is a good thing.
Do not acknowledge the error by selecting OK. Let it be there but instead sneak behind and hit the start icon. Bring up the file manager and go to the windows/startup folder. Delete upgrade program. Do a softboot.
Working PDA but no Radio Stack
Now you will have PPC again but it will be slow and you will have no radio stack yet. Now to fix that. Go to your PC in the SX56 upgrade/english directory and copy these four files to the Windows directory on your PPC.
monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.exe, RSUpgrade.cp64.
Once copied leaving your PPC in the charging cradle run RSUpgrade.exe from the PPC windows directory. It should upgrade all your ROMS and you should be back in business.
The only file I could not update was the rilgsm.dll. It was locked and would not let me mess with it or copy another on top of it. Perhaps another attempt at the upgrade program would fix this but I am gun shy right now and I have a working system again.
Chris
Dear Chris,
THanks for your clearly poitining out steps to fix the phone. Can you please help me where to download the repair.zip. or drop my email: [email protected].
Thanks!
hoanghon
Hi,
I have a T-Mobile Pocket PC Phone 2003.
Rom version: 4.01.16 ENG
Rom date: 02/04/04
Radio version: 6.25.02
Protocol version: 324e4
Wallaby Bootloader: V5.22
I am in a GSM 1800Mhz region while the phone has only 900/1900Mhz. I have read various reports that with a Firmware upgrade I can make the phone Tri-Band capable meaning 900/1800/1900Mhz. There have also been reports that this is a hardware feature which will not be effected by software upgradation. But I wanna still try. Firstly the phone was Simlocked by T-Mobile which I managed to unlock with a code given by their SimUnlock dept. believe it or not.
The problems / issues I am facing with this phone are:
1. Downloaded the XDAROM.exe with adaptROM.exe Program A.exe etc in it but it always stops at the dreaded -
ERROR: GetDeviceData - An existing connection was forcibly closed by the remote host.
error getting devicedata
For the above I have tried all the suggestions on this forum like hard booting (battery off/on), Select GSM900 in Wallaby Mode then reset, Remove Sim Card then Reset, Switch off Radio (which I presume is GSM) in Wallaby then reset. All options lead to the same error.
2. Tried backing up the current ROM in Bootloader Mode which it does and asks me to press the Action key. But when I reboot the device or remove the SD Card and plug it into a PC it says Card not formatted. The SD card
works under normal conditions transferring data to and fro and storing data.
3. Read that I can copy the .NB1 (update file) onto a SD card and on rebooting it should ask if I want to Flash the device with this new data but it never asks and reboots completely.
4. Wallaby mode is also supposed to Flash the device via USB if I press the record key I tried but the computer and device never connect.
5. Device does not ActiveSync always on docking very often I may need to reboot the PC and or the Device for them to talk.
6. Tried XDAUnlock. exe which gave me 'error getting unlock code'.
Any ideas people? Any help would be greatly appreciated.
Andrew with no clever lines
In no particular order:
(1) 1800 MHz is a hardware feature. At best, playing with the firmware will make the phone think it can operate at 1800MHz, but it really can't without hardware changes. But hey, you already know that.
(2) When you dump the ROM to an SD card, it is dumped as an image, which overwrites any FAT formatting on the card. This is why you're getting the "Card not formatted" message on the PC. You need special PC software (XDATools -- available on this website, or XDArit) to access the ROM image on the card with the PC.
(3) In order to upgrade the XDA with an SD card, the firmware needs to be placed on the SD card as an image (the same format as #2 above). If you just did a PC file copy you used the wrong method. XDATools also does this function.
(4) Why are you trying to use XDAUnlock.exe when you've already unlocked your phone with the code from T-Mobile?
Hi,
Thanks I did finally realise what every one took for granted in this site that the ROM dumps on the SD were written in a proprietory image format not FAT format.
Am trying the entire exercise coz have read at enough places on the site that the phone can be cracked to be tri-band which is what I need for it to roam India. We have only 900Mhz at select locations and the rest is 1800Mhz. Can only but be hopeful.
The chronology for the unlock bit was off on my mail.
Basically I cant perform any updates to the phone via the adaptROM method because I feel Wallaby 5.22 has protection built into it and shuts down the connection. If I try to Downgrade the Wallaby to V5.15 using the bootloaderfix included XDATools I get the error listed below.
'C:\bootload\pput.exe' is not recognized as an internal or external command,
operable program or batch file.
ERROR: ITReadProcessMemory - Unspecified error
Unable to find flash info offset, cannot disable bootloader writeprotect
If I use XDArit V1.02 route to write via SD I get Failed to open Device \\.\PhysicalDrive7
Anyone got the older version of XDArit ??
Help people.
Thanks,
Andrew
I'm not as familiar with Bootloader version issues. My (old) unit was Version 5.15. I just got a replacement for it after I busted the screen, and the new one is Version 5.22. Maybe I'll learn more about bootloaders...
But LumpiStefan says he hasn't had problems using the SD card method with 5.22. I haven't played with the new phone yet, since it came with WM03.
Wouldn't it be easier for you to spend $100 (or so) on an unlocked 900/1800 phone?
AS I sit here staring at my cute little Wallaby in it's cradle with a nice desktop, I long for 20/20 foresite. I can sync with my PC and and do anything I want as long as I don't want to make a phone call or take it off its cradle. I have been all over this web site and the web in general looking for a solution to the 1% GSM Failure Upgrade problem. I have tried every written idea and approach with no success. I am sharing my conclusions here with no particular hope of an answer.
It seems a low battery may cause the error in the first place. The first upgrade attempt got me to 16% and hang. I reset and got to 6%. Third time it was 1%. Once the battery is low the GSM processor shuts down. The GSM processor controls the battery charge. You can not upgrade the Radio Stack if the GSM processor is shutdown Even a new battery does not seem to reset the GSM as there is a software switch that seems to have been set. I have read some vague reference to a serial cable and hyperterminal used by TMobile techs to "reset" but no real details.
I am moving on with my life as Wallaby is dead.... I miss you, baby.
Have you tried this method?
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
cruisin-thru said:
Have you tried this method?
Yes I saw this solution straight away and have tried it and several variations, but now that I review it I have a question. The wallaby's battery is completely dead so after the reset I must put it in the cradle for it to start up. It then produces the 1% again ala step 8. Now what am I supposed to do? Take it off the cradle and put it back on? That would cause AS to start. Are you suggesting the GSM upgrade will take place WITH the error message right on screen?. That would be super! I'll try it right now.
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
Click to expand...
Click to collapse
Blues Redeux
One other note. The developers ROM v1.1 will not active sync with my PC. Neither will v1.2. All the other STD roms I've tried will though. Any idea about that?
getting the image to run from the SD card
problem: radio stack upgrade failed (using the siemens upgrade) and now I get a GSM error and eventually a partial pocket pc desktop with no start menu or access to an explorer window.
OK, I used xda tools to copy the rom to the SD card (1GB card), inserted in the wallaby, held the power and soft reset the device, I get the boot loader v5.15 and then a GSM Error. From there, nothing. Any suggestions as to what I am doing wrong? Does the SD card need additional files or should it be formatted a certain way? Any help would be greatly appreciated.
Getting image to run from SD card
Charles,
If you search this site you will find many descriptions of how to load an image from the SD card. Sounds to me as if you did not get a valid rom image on the the card cause the boot loader should rcognize it and ask you if you want to copy it.
The bigger problem is the PDA rom does NOT fix the GSM rom, which is the one that is hosed.
I am now in week three after I killed my Wallaby and I am having severe withdrawal pains. I did not realaize how much I depended on it. Can anyone tell me where I can sent it to have the GSM/Radio stack fixed?
I have found how to flash radio via rs232 cable, but i need program monitor.exe (pc monitor ver 6.5.7) to do this. I can't find it. Does anyone have this program or know where i can download it?
Sorry for my english, I'm from Poland
can someone tell me what ipl or hspl is?
and for what is this?sorry i am beginner xD
thanks for help
Frequently Used Acronyms in PPC World
Frequently Used Acronyms in PPC World
.CAB Files : Cabinet - is the Microsoft Windows native compressed archive format. cab files are files used to install programs. cab files are similar to what you might know as .exe files from your PC. cab files can be downloaded directly to your Hermes with Wifi or GPRS, you can also transfer them to your Hermes using File Explorer on your PC. cab files are not supposed to be unpacked/unzipped on the PC. Copy the intact .cab file as you downloaded it directly to your Hermes
ActiveSync :This program by Microsoft is what we all use to connect to our computers at work or at home. It allows contacts, tasks, emails and Calendar events to be synchronised with Outlook aswell as such things as media and favorites. In Windows Vista this has been replaced by the Windows Mobile Device Center. In addition ActiveSync allows browsing of the device in Windows Explorer.
AKU: Adaptation Kit Update - they usually patch up existing bugs and enable several new features. Each newly released AKU pack retains fixes found in previous versions of AKU. Starting with Windows Mobile 5 Microsoft began a policy of updates similar to that of the desktop windows. Rather the replacing the whole OS some functionality may be added. For example AKU 2.0 introduced push mail. These updates are distributed through the OEMs and are given to the consumer in form of ROM updates. Note that OEM may choose not to create an update with the latest AKU for their devices. Getting an AKU for your phone is like getting the SP2 (Service Pack 2) for your Windows Xp.
Application Unlock: Most Windows Mobile devices only allow you to load applications that have an acceptable digital signature. If you try to edit the registry or load an application it will give you an error. Application Unlocking removes this barrier and allows you to install any application or edit the registry to your liking.
Baked ROM : that the original shipped complete ROM (CE, Extended and radio) has been modified. A Baked ROM could have a CE ROM from one operator, a Radio stack from a second operator, an Extended ROM from a third operator or even a “cooked” extended ROM.
Bootloader : The bootloader is the first thing to load once you turn on the device, this does the job of booting up the device hardware and loading various items into memory before the ROM starts in the device. The bootloader is also responsible for enabling the flashing of new ROMs and other components such as the Radio and the Ext_ROM. Two modified bootloaders for the Hermes are HardSPL and SSPL. To enter the bootloader, press and hold the OK and POWER buttons while inserting the stylus into the reset hole on the bottom of the Hermes.
Chef / Cook : Its a term coined by the developer community to refer to people who build custom ROMs ( ie; people who cooks ROM ). Personal favourites are : Jasjamming and Schaps
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from 3Mobile (3Mobile is the ‘carrier’), your phone will only accept 3Mobile ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
Cooked ROM : means that the ROM has been modified with other files
CustomRUU: is an RUU (Rom Upgrade Utility) which has support for all SPL versions including HardSPL and SSPL.
Device Lock : The device lock is a today screen plugin that locks all the buttons (and the touch screen) until you unlock it, it will allow you to answer calls. To use it simply tap the ‘device unlocked’ today item and it will lock the device, to unlock press the left hand soft key and tap the unlock button on screen.
Dopod 838 Pro / i-mate JASJAM / O2 Xda Trion / HTC TyTN : all of these are essentially the same deice
ExtROM: Extended ROM - is the section of the ROM which the distributor of the phone (eg O2, T-Mobile, iMate, etc) store their customization (eg Today theme, ring tones, extra software) data. In WM5, the customization data will be automatically installed after the initial configuration (after every hardreset), just after the security section. In most cases, ExtROM can be unlocked to allow users to store/build their own customizations that will be automatically installed upon every hardreset.
Firmware: This is a piece of software that is stored in a device to make it function. It is, unlike ordinary software, usually semi-permanent and resides in a non-volatile storage area which is unaffected by “hard resetting” a device. The term usually refers to low-level code that controls individual hardware components such as a radio rom.
Flashing : a ROM is the process putting a new ROM on your device or otherwise know as upgrading.
Hard Reset : Switch the device off. Press and hold the Left SOFT KEY and Right SOFT KEY, and at the same time, use the stylus to press the RESET button at the bottom of your device. You will be presented with a menu saying ‘press R to reset, X to exit’. If you press R, your device will be set back to factory default settings. Hard Reset will delete all data you have put on the device: Programs, Settings, Mail, SMS, MMS, etc., so be careful and make a backup before doing this. After a hard reset, you will have a complete clean new install of Windows Mobile on your device. Data on \Storage Card & \Extended_Rom folder will not be deleted
Frequently Used Acronyms in PPC World
HardSPL : This modified bootloader (by Olipro) allows a much safer flashing process to take place since it reduces the chance of permenently bricking your Hermes device. It also removes the need to CID Unlock the device since it ALWAYS reports SuperCID when flashing.
IPL: Initial Program Loader - It boots up SPL. Its the bootloader for PPC, much like the BIOS is the boot loader for your PC. Note: IPL/SPL are highly hardware dependent, flashing the wrong IPL/SPL is much more serious than a flashing the wrong ROM. It may be noted that, sometimes a ROM package also contains the IPL/SPL which will be flashed into your phone. Hence be extra careful what you are flashing. Note: although a ROM may also contains the IPL/SPL
OEM : Original Equipment Manufacturer - is a company that supplied equipment to other companies to resell or incorporate into another product using the reseller’s brand name.
OS: Operating System - the platform software for your phone, much like the Windows Xp/Vista for your PC. Upgrading the OS is like, in PC terms upgrading from Windows XP to Windows Vista. Os for PPC are WM2002, WM 2003, WM2003SE, WM5, WM6
PIE : Pocket Internet Explorer - is the default browser that comes with the Windows Mobile Operating System.
PPC : Pocket PC - is a hardware specification for a Personal digital assistant that runs the Microsoft Windows Mobile operating system.
Program memory: The non-persistent memory part of WM5, which is used for all the temporary memory requirements, much like the RAM of your PC. A soft-reset or flat battery will erase everything from the program memory. You can’t adjust the ratio of Storage memory and Program memory in WM5 like WinCE2003.
Radio: commonly used in the form `upgrading the Radio/GSM` - in the field of ROM upgrading. The `Radio` is essentially a ROM that controls the phone function part (as oppose to PDA function part) of your phone. Upgrading this `Radio` software may have effect on your phone reception quality, battery life (optimized phone function), signal strength, etc.
RIL: Radio Interface Layer -
ROM: Read Only Memory - commonly used in the form of `ROM upgrade`. The ROM is the firmware/software, which controls everything on your phone. ROM itself usually comes in a package, with IPL/SPL, OS, Radio, and ExtRom. However, in most cases, `upgrading a ROM` usually means just the OS and the ExtRom, as these are the obvious/visible part of an ROM upgrade.
RTM : Release to Manufacturing or Ready to Market.
RUU: ROM Upgrade Utility - Its the s/w used on your PC to do a ROM upgrade for your PPC
SIM: Subscriber Identity Module - commonly used in the form `SIM unlock`. Some phones are locked to the specific telco from which you purchase your phone, eg you can’t use a locked 3Mobile phone with a Vodaphone SIM/smart card. To use SIM card from other telco, you need to SIM unlock your phone. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.SIM Unlock: Use any carrier’s SIM in the device.
SIP : Software Input Panel - for devices that does not have a hardware keyboard the SIP is used to enter data on to the PPC eg: the software keyboard, Symbol Pad, Block Recoganizer, etc . Note : SIP can also stand for Session Initiation Protocol , check the wikipedia entry SIP as a voice over IP protocol.
Smartphone : Pre WM6 class, Smartphone is defined as a mobile phone which offers advanced capabilities like that of a PC. It will not have a touchscreen as compared to a Pocket PC. With the introduction of WM6 all mobile phone devices running Windows Mobile are no classed as Windows Mobile powered Smartphones
Soft Reset : Put your stylus in the hole in the lower left corner. Soft Reset will reboot your device just like when you reboot your PC. No data will be lost, under normal circumstances.
SPL: Secondary Program Loader - Loads the actual OS.
SSPL : is a modified bootloader (by Des) which is loaded into RAM when run, this allows us to overwrite any aspect of the ROM, Radio or Bootloader far easier than using mtty.
Storage memory: The persistent memory part of WM5, where all the files and documents are kept, much like the hard disk of your PC. Data in the storage memory is unaffected by soft-reset or a flat battery. You can’t adjust the ratio of Storage memory and Program memory in WM5 like WinCE2003.
SuperCID : by CID unlocking your device the value of the CID is changed to SuperCID . This allows the flashing of ANY ROM to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
Touch Cube : usually simply referred to as the Cube. It is a 3d navigation interface created by HTC that uses their TouchFlo technology. The interface was introduced with the HTC Touch and has since been used in several other devices. It has also been ported to devices that pre-date the Touch.
TouchFlo : This is the HTC version of the flick-to-scroll technology often associated with the iPhone. This is not to be confused with the Touch Cube which is another HTC technology. It was 1st seen in HTC Touch.
TouchFlo 3D : this was code named ” Manilla ” and is another HTC technology , its an extension on to the today screen to give the user a finger friendly approach to using the PPC. It was 1st seen with the Touch Diamond.
UI : User Interface - some notable examples would be TouchFlo, PointUI
USSD : Unstructured Supplementary Service Data - is a capability of all GSM phones. It is generally associated with real-time or instant messaging type phone services. There is no store-and-forward capability that is typical of ‘normal’ short messages. Response times for interactive USSD based services are generally quicker than those used for SMS. Its used to send text between a mobile phone and an application program in the network eg: *123# for balance etc.
USIM : Universal Subscriber Identity Module - is an SIM for UMTS mobile telephony running on 3G mobile network.
WindowsCE / WinCE : aka Windows Embedded CE since version 6.0 Microsoft has stated that the ‘CE’ is not an intentional initialism, but many people believe CE stands for ‘Consumer Electronics’ or ‘Compact Edition’;The first version, was known during development under the codename “Pegasus”.
WM: Windows Mobile - the OS of the PPC
WM Classic : Windows Mobile Classic - the OS for PPC device without a phone.
WM Professional : Windows Mobile Professional - the OS for Phone enabled device with a touchscreen (formerly Phone Edition).
WM Standard : Windows Mobile Standard - the OS for Phone enabled device without a touchscreen (formerly Smartphone).
WWE Edition: World Wide English Edition - Its usually appended along with new ROM releases , to show that its a ROM that will have English as the default Language
WDA : Wireless Digital Assistant - This is the term that Hewlett Packard coined with their new 928 WDA Pocket PC 2002 Phone Edition which integrates a cell phone with a Pocket PC.
XDA : Extended Digital Assistant - This the term that O2 coined with their new Pocket PC 2002 Phone Edition which integrates a cell phone with a Pocket PC.
XIP : Execute in Place - The execution of a program stored in ROM or flash that is run directly from the location where it is stored. The execution does not require the program to be copied into ram before execution. This reduces the amount of ram that an application requires since it does not all have to load into RAM.
oh thanks dude
nice help^^
Nice explanation !
thanks