Paul's guide to... changing the HTC Touch / T-Mobile Wing PagePool size
Started by
PaulOBrien
, Jun 22 2007 10:13 AM
#241
Posted 06 April 2008 - 11:53 PM
hey paul im stuck on step 3...on the pagepool changing i dont know how to open a command prompt in the pagepool folder/directory i make therefore i cant get passed that step if you could please help me i would appreciated thank you
#242
Posted 07 April 2008 - 08:50 AM
#243
Posted 07 April 2008 - 07:33 PM
Quote
- Ensure device is connected to PC and Activesync'd / WMDC'd
- Open a command prompt at your new directory
- Type 'pdocread -l' (minus the quotes of course)
- Open a command prompt at your new directory
- Type 'pdocread -l' (minus the quotes of course)
how do i do the second step..? I dint understand what you meant by open a command prompt at your new directory?...
#244
Posted 09 April 2008 - 03:04 AM
Flashed my Wing, right?
Went from 2.2MB (with just WM6 running) to 15.4 after startup.
I rebooted once, now it's at 11.3 after startup.
Whats the deal?
Went from 2.2MB (with just WM6 running) to 15.4 after startup.
I rebooted once, now it's at 11.3 after startup.
Whats the deal?
#245
Posted 22 April 2008 - 06:52 PM
Thank you for this, I went from 10MB available to 18MB available by decreasing page pool to 6MB from the t-mobile wing default.
#246
Posted 22 April 2008 - 10:08 PM
I went from 1.3Mb to 347.2 Mb 
He who asks a question looks foolish for 5 minutes. He who doesn't ask a question remains foolish forever.
#247
Posted 23 April 2008 - 01:26 PM
kinoons, on Jun 24 2007, 06:48, said:
Sofar I have ran the ROM unlocker and downloaded the pdocread file. When I run "pdocread -l" I get the following for my part 2
"50.63M <0x32a0000> Part02"
When I type "pdocread 0 0x32a0000 part02.dump" I get this response
copy TFFSToFile(0x0, 0x32a0000, part02.dump)
ERROR: ITReadDisk : Read 00000000 bytes - A device attached to the system is not functioning
And I don't get a part02.dump file. Any ideas? thanks!
Kinoons
"50.63M <0x32a0000> Part02"
When I type "pdocread 0 0x32a0000 part02.dump" I get this response
copy TFFSToFile(0x0, 0x32a0000, part02.dump)
ERROR: ITReadDisk : Read 00000000 bytes - A device attached to the system is not functioning
And I don't get a part02.dump file. Any ideas? thanks!
Kinoons
Hello, I got an HTC S730 which gave a different file size but the same problem
Regards
#248
Posted 29 April 2008 - 08:19 AM
worked great went from 5mb to 17
thanks man
-steve_x
thanks man
-steve_x
#249
Posted 13 May 2008 - 12:27 AM
Worked for so far. No problems... Thanks. TMobile had no clue when I told them I had a memory problem..
Now I don't have to return my device.
Now I don't have to return my device.
#250
Posted 21 May 2008 - 03:45 PM
damn. Double post.
Edited by zeflash, 21 May 2008 - 03:46 PM.
#251
Posted 21 May 2008 - 03:45 PM
I was wondering if someone with knowledge could tell me what's going on with this ROM:
http://forum.xda-dev...ad.php?t=392637
the ultra clean edition.
I downloaded it, flashed it and the pagepool on my Touch (Elf) is 8 MB. Yet when I look at the hexa value, it says 00 00 20 00. And changing this value didn't modify the pagepool.
How can I change the pagepool for this ROM?
http://forum.xda-dev...ad.php?t=392637
the ultra clean edition.
I downloaded it, flashed it and the pagepool on my Touch (Elf) is 8 MB. Yet when I look at the hexa value, it says 00 00 20 00. And changing this value didn't modify the pagepool.
How can I change the pagepool for this ROM?
#252
Posted 23 May 2008 - 08:50 AM
Hi,
I started trying to optimise my pagepools size following the instructions in your post. However I noticed the setting on my HTC Touch P3450 (Dutch KPN) is set to 00 00 20 00 instead of 00 00 80 00 for the default 8 MB for a Touch. Does this mean mine has 2MB?
The reason I wanted to change the pagepool size was because with almost any application I installed I had messages on my Touch saying "Not enough memory".
Your post looked like the solution to my problem but these findings make me confused.
Can it be that having an apparent default setting of 2 MB in my device can cause the same memory issues as with the default 8MB and that 4MB might be a better optimised alternative?
Thanks.
I started trying to optimise my pagepools size following the instructions in your post. However I noticed the setting on my HTC Touch P3450 (Dutch KPN) is set to 00 00 20 00 instead of 00 00 80 00 for the default 8 MB for a Touch. Does this mean mine has 2MB?
The reason I wanted to change the pagepool size was because with almost any application I installed I had messages on my Touch saying "Not enough memory".
Your post looked like the solution to my problem but these findings make me confused.
Can it be that having an apparent default setting of 2 MB in my device can cause the same memory issues as with the default 8MB and that 4MB might be a better optimised alternative?
Thanks.
Paul (MVP), on Jun 22 2007, 10:13, said:
[teaser]Welcome to another edition of 'Paul's Guide to...'
Today's guide is aimed at owners of the HTC Touch and the T-Mobile Wing, as they are 2 devices that seem to have particular problems with device memory, but the same techniques can probably be applied to other devices (untested by myself).
HTC Touch and T-Mobile Wing owners will know that these two devices suffer somewhat from low memory problems. Users need to be careful with what they have running at any one time, particularly if launching memory hungry applications such as the Camera.
Deep in the depths of the operating system of your device, there is something called the 'PagePool'. Without going into too much detail (and as I understand it!), the PagePool is a special area of memory reserved for loading apps into from ROM. This PagePool is a lot faster than ROM, so when things are executed from this 'cache' instead, the performance of a device will be quicker. On the flipside, if you have a 8MB pagepool (HTC Touch) and you're using, say, 4MB of the pagepool, then 4MB of space is wasted that could be program memory. Similarly if you have a 12MB pagepool (!) (T-Mobile Wing) in this instance you would we wasting 8MB of space!
The key is striking the balance...
On both my Touch and my Wing, i've been experimenting with the PagePool, and have personally settled on 4MB. I've tried 2MB (bad), 4MB, 6MB and 8MB, and I think I can happily use 4MB without noticing a performance decrease. I'm tempted to try 6MB out for a bit longer, particularly on the Wing (which has a generally better state of affairs than the Touch it seems), but this guide will let you choose your own.
Sadly, these PagePool settings are in an area that cannot be easily changed, hence this is a ROM guide.[/teaser]
Firstly, a disclaimer.
This guide involves downloading, editing and flashing of your device ROM.
This is dangerous, very dangerous. In a worst case scenario using these techniques, your device will become unusable, with a corrupted 'OS area'. While your bootloader will (should) still be accessible, your device will be a paperweight until such time as a RUU (Rom Update Utility) becomes available for your device with the shipping ROM. We won't be able to help you, and your operator / manufacturers won't either. It's quite possible your warranty will be invalidated by editing your ROM.
If you follow this guide, you take full responsibility for what could happen. I have of course successfully been through this guide myself, but be aware that I TAKE NO RESPONSIBILITY SHOULD SOMETHING GO WRONG.
You've read the disclaimer and you want to have a play, now what do you need to do? Here's the guide... enjoy
Step 1: Install the permissions CAB to your device
In order to be able to do the read / write operations on your ROM, the security on your device needs to be set up in a certain way. Download this CAB file, and run it on your device.
ITSUTILS...peration.CAB
Step 2: Create a directory and download itsutils
Now we need to create a working directory. I suggest creating a directory called 'pagepool' on your desktop. When you've done this, download this ZIP file, and extract it to the new directory.
http://nah6.com/~its...in-20070323.zip (Kudos to Willem Jan Hengeveld (aka itsme) for this excellent toolkit!)
Step 3: Extract the ROM from your device
We're now going to extract the ROM from your device. This is a completely safe operation, so don't panic yet
Take the following steps...
- Ensure device is connected to PC and Activesync'd / WMDC'd
- Open a command prompt at your new directory
- Type 'pdocread -l' (minus the quotes of course)
You will then be presented with something that looks like this:
- Type 'pdocread 0 0x40d2000 Part02.dump' substituting 0x40d2000 with the appropriate value from your 'pdocread -l' output
You will see something like 'CopyTFFSToFile(0x0, 0x40d2000, Part02.dump)' appear, and after a wait of a few minutes (it is dumping a lot of data!), you'll be returned to the command prompt. During the operation you can open Windows Explorer to your working directory and see the file growing.
Step 4: Use a hex editor to modify the pagepool size
To edit your Part02.dump ROM image, you'll need to use a Hex Editor. The instructions below assume use of the excellent, free HxD application.
After installing and launching HxD, do the following...
- Open your new 'Part02.dump' file
- Click 'Search'
- Enter 'NKKD8'
- Press F3 to find the second instance
- Click 'Search' again
- Change 'Data Type' to 'Hex Values'
- Enter 'FF FF FF FF FF FF FF FF 9B 4F FF FF 64 B0 00 00' and hit search
You will then be presented with the search results as shown below.

After 8 more values, you'll see your pagepool setting. In the screenshot aobve, it is set to '00 00 40 00', which means 4MB. The possible values are as follows:
4MB = 00 00 40 00
6MB = 00 00 60 00
8MB = 00 00 80 00 (HTC Touch default)
12MB = 00 00 C0 00 (HTC Wing Default)
(for reference, on both my Touch and my Wing the offset location is 37B558... you can go straight to this location be selecting 'Search -> Goto').
So, to change your pagepool size...
- After locating your current pagepool value, update it to one of those shown above by selecting the value and overtyping
- Select File -> Save As, and enter a new name (e.g. Part02.4MB.dump)
- Exit the hex editor
You have now edited your ROM dump, and are ready to flash it back to the device!
Step 5: Flashing your edited dump back to the device
So this is where it gets dangerous. If you've done something wrong with your dump, then nasty things could (probably will) happen. If the flashing process goes wrong, then nasty things could happen. One final warning - you undertake this step at your own risk! Ready to continue? OK then...
- Ensure device is connected to PC and Activesync'd / WMDC'd
- Put the device in flight mode. This is for safety reasons... receiving a call during the flash would probably be bad
- Open a command prompt to your working directory (or use the one you already have open)
- Type 'pdocwrite Part02.4MB.dump' (or whichever name you used in the step above)
You will see something like 'CopyFileToTFFS(part02.4mb.dump:0, 0, 040d2000)' appear, and after a wait of a few minutes (it is writing a lot of data!), you'll be returned to the command prompt. DO NOT USE THE DEVICE DURING THIS OPERATION!
Step 6: Soft reset, cross fingers
Has that command finished (i.e. you have control again at the command prompt)? Then you're done! Simply press the soft reset pin on your device, and when it comes back up, you should see you the amount of program memory in the Settings -> Memory applet has changed. Good job! You can breathe easy again
P
Today's guide is aimed at owners of the HTC Touch and the T-Mobile Wing, as they are 2 devices that seem to have particular problems with device memory, but the same techniques can probably be applied to other devices (untested by myself).
HTC Touch and T-Mobile Wing owners will know that these two devices suffer somewhat from low memory problems. Users need to be careful with what they have running at any one time, particularly if launching memory hungry applications such as the Camera.
Deep in the depths of the operating system of your device, there is something called the 'PagePool'. Without going into too much detail (and as I understand it!), the PagePool is a special area of memory reserved for loading apps into from ROM. This PagePool is a lot faster than ROM, so when things are executed from this 'cache' instead, the performance of a device will be quicker. On the flipside, if you have a 8MB pagepool (HTC Touch) and you're using, say, 4MB of the pagepool, then 4MB of space is wasted that could be program memory. Similarly if you have a 12MB pagepool (!) (T-Mobile Wing) in this instance you would we wasting 8MB of space!
The key is striking the balance...
On both my Touch and my Wing, i've been experimenting with the PagePool, and have personally settled on 4MB. I've tried 2MB (bad), 4MB, 6MB and 8MB, and I think I can happily use 4MB without noticing a performance decrease. I'm tempted to try 6MB out for a bit longer, particularly on the Wing (which has a generally better state of affairs than the Touch it seems), but this guide will let you choose your own.
Sadly, these PagePool settings are in an area that cannot be easily changed, hence this is a ROM guide.[/teaser]
Firstly, a disclaimer.
This guide involves downloading, editing and flashing of your device ROM.
This is dangerous, very dangerous. In a worst case scenario using these techniques, your device will become unusable, with a corrupted 'OS area'. While your bootloader will (should) still be accessible, your device will be a paperweight until such time as a RUU (Rom Update Utility) becomes available for your device with the shipping ROM. We won't be able to help you, and your operator / manufacturers won't either. It's quite possible your warranty will be invalidated by editing your ROM.
If you follow this guide, you take full responsibility for what could happen. I have of course successfully been through this guide myself, but be aware that I TAKE NO RESPONSIBILITY SHOULD SOMETHING GO WRONG.
You've read the disclaimer and you want to have a play, now what do you need to do? Here's the guide... enjoy
Step 1: Install the permissions CAB to your device
In order to be able to do the read / write operations on your ROM, the security on your device needs to be set up in a certain way. Download this CAB file, and run it on your device.
Step 2: Create a directory and download itsutils
Now we need to create a working directory. I suggest creating a directory called 'pagepool' on your desktop. When you've done this, download this ZIP file, and extract it to the new directory.
http://nah6.com/~its...in-20070323.zip (Kudos to Willem Jan Hengeveld (aka itsme) for this excellent toolkit!)
Step 3: Extract the ROM from your device
We're now going to extract the ROM from your device. This is a completely safe operation, so don't panic yet
- Ensure device is connected to PC and Activesync'd / WMDC'd
- Open a command prompt at your new directory
- Type 'pdocread -l' (minus the quotes of course)
You will then be presented with something that looks like this:
70.95M (0x46f2000) TrueFFS<BR> | 3.06M (0x30fc00) Part00<BR> | 3.06M (0x310000) Part01<BR> | 64.82M (0x40d2000) Part02We want to read the Part02 area (the bottom line above), so...
- Type 'pdocread 0 0x40d2000 Part02.dump' substituting 0x40d2000 with the appropriate value from your 'pdocread -l' output
You will see something like 'CopyTFFSToFile(0x0, 0x40d2000, Part02.dump)' appear, and after a wait of a few minutes (it is dumping a lot of data!), you'll be returned to the command prompt. During the operation you can open Windows Explorer to your working directory and see the file growing.
Step 4: Use a hex editor to modify the pagepool size
To edit your Part02.dump ROM image, you'll need to use a Hex Editor. The instructions below assume use of the excellent, free HxD application.
After installing and launching HxD, do the following...
- Open your new 'Part02.dump' file
- Click 'Search'
- Enter 'NKKD8'
- Press F3 to find the second instance
- Click 'Search' again
- Change 'Data Type' to 'Hex Values'
- Enter 'FF FF FF FF FF FF FF FF 9B 4F FF FF 64 B0 00 00' and hit search
You will then be presented with the search results as shown below.

After 8 more values, you'll see your pagepool setting. In the screenshot aobve, it is set to '00 00 40 00', which means 4MB. The possible values are as follows:
4MB = 00 00 40 00
6MB = 00 00 60 00
8MB = 00 00 80 00 (HTC Touch default)
12MB = 00 00 C0 00 (HTC Wing Default)
(for reference, on both my Touch and my Wing the offset location is 37B558... you can go straight to this location be selecting 'Search -> Goto').
So, to change your pagepool size...
- After locating your current pagepool value, update it to one of those shown above by selecting the value and overtyping
- Select File -> Save As, and enter a new name (e.g. Part02.4MB.dump)
- Exit the hex editor
You have now edited your ROM dump, and are ready to flash it back to the device!
Step 5: Flashing your edited dump back to the device
So this is where it gets dangerous. If you've done something wrong with your dump, then nasty things could (probably will) happen. If the flashing process goes wrong, then nasty things could happen. One final warning - you undertake this step at your own risk! Ready to continue? OK then...
- Ensure device is connected to PC and Activesync'd / WMDC'd
- Put the device in flight mode. This is for safety reasons... receiving a call during the flash would probably be bad
- Open a command prompt to your working directory (or use the one you already have open)
- Type 'pdocwrite Part02.4MB.dump' (or whichever name you used in the step above)
You will see something like 'CopyFileToTFFS(part02.4mb.dump:0, 0, 040d2000)' appear, and after a wait of a few minutes (it is writing a lot of data!), you'll be returned to the command prompt. DO NOT USE THE DEVICE DURING THIS OPERATION!
Step 6: Soft reset, cross fingers
Has that command finished (i.e. you have control again at the command prompt)? Then you're done! Simply press the soft reset pin on your device, and when it comes back up, you should see you the amount of program memory in the Settings -> Memory applet has changed. Good job! You can breathe easy again
P
#253
Posted 02 June 2008 - 07:43 PM
rope, on Jun 26 2007, 02:23, said:
There is a (official Touch ROM) RUU available at pdamobiz:
RUU_Elf_DOPODASIA_WWE_1.11.707.1B_4.1.13.42_02.93.90_Ship.exe
I think this would help to get the Touch back to life if you damaged it with a wrong flash.
RUU_Elf_DOPODASIA_WWE_1.11.707.1B_4.1.13.42_02.93.90_Ship.exe
I think this would help to get the Touch back to life if you damaged it with a wrong flash.
Can you provide the instruction on how to restore the ORIGINAL flash (RUU) ???
Thanks.
#254
Posted 03 June 2008 - 12:28 PM
Worked excellent the first and second time. I flashed mine last year when I got it and it worked great, used Win XP to do it. Then I noticed T-Mobile had a phone flash upgrade availeble recently on thier website, so I flashed mine to upgrade, and it put my page pool back to not letting my camera work again. So, I used my Vista computer now and did the whole thing just like the last and again it worked perfectly. Just wished they made it with 128 ROM and 256 RAM to begin with and we would not be having this problem. Oh well, just about wore out my touchscreen on this Wing, so I hope they have a version of the AT&T Tilt coming to T-Mobile soon and Want my 3G too, Tmob had better get its butt movin!
Anyone reccommend some good tweaking tools, all I know is that battery status one that you can even overclock with as well.
Shaggy
Anyone reccommend some good tweaking tools, all I know is that battery status one that you can even overclock with as well.
Shaggy
Daily Driver: HTC Sensation 4G running LeeDroiD Sensational 4.x.x on T-Mobile USA
Weekend Driver: TripNiCE - IceCream Sandwich 4.0.1
Weekend Driver: TripNiCE - IceCream Sandwich 4.0.1
#255
Posted 06 July 2008 - 08:25 PM
Shagman68, on Jun 3 2008, 13:28, said:
Worked excellent the first and second time. I flashed mine last year when I got it and it worked great, used Win XP to do it. Then I noticed T-Mobile had a phone flash upgrade availeble recently on thier website, so I flashed mine to upgrade, and it put my page pool back to not letting my camera work again. So, I used my Vista computer now and did the whole thing just like the last and again it worked perfectly. Just wished they made it with 128 ROM and 256 RAM to begin with and we would not be having this problem. Oh well, just about wore out my touchscreen on this Wing, so I hope they have a version of the AT&T Tilt coming to T-Mobile soon and Want my 3G too, Tmob had better get its butt movin!
Anyone reccommend some good tweaking tools, all I know is that battery status one that you can even overclock with as well.
Shaggy
Anyone reccommend some good tweaking tools, all I know is that battery status one that you can even overclock with as well.
Shaggy
Isn't it easier to use this easy to use Pagepool size changer. It uses the same tools as mentioned in this thread. Just start the pagepool batchfile you wat, 4,6,8 of 12mb. Backup your own PP first!
Archos 43IT, Nokia n5800
#256
Posted 04 August 2008 - 11:12 AM
Weird, you have a different readout!
P
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.
#257
Posted 07 August 2008 - 05:32 PM
#258
Posted 19 August 2008 - 05:18 AM
I'm still stuck on #1.
I'm trying to download the attch* ""
where is the link to this download
I'm trying to download the attch* ""
where is the link to this download
#259
Posted 19 August 2008 - 06:20 AM
Just_Chillin, on Aug 19 2008, 06:18, said:
I'm still stuck on #1.
I'm trying to download the attch* "
ITSUTILS...peration.CAB"
where is the link to this download
I'm trying to download the attch* "
where is the link to this download
He who asks a question looks foolish for 5 minutes. He who doesn't ask a question remains foolish forever.
#260
Posted 19 August 2008 - 07:26 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users







Sign In
Create Account

Back to top









