[REF] The Definitive Guide to Changing Pagepool on 2.00 & 2.03 ROMS

[shaks1979]

After having done some research in changing the pagepool on the new 2.0x based diamond roms I have made some interesting discoveries.
The new roms have another 4Mb missing e.g.

2.0x ROMs with 12Mb pagepool have 107.02Mb Program Memory, 8Mb Roms have 111.02Mb, 0Mb Roms have 119.02Mb & if you see 113.02Mb then pagepool is 6Mb

In Comparison
1.93 ROMS with 12Mb pagepool have 111.02Mb Program Memory, 8Mb Roms have 115.02Mb, 0Mb Roms have 123.02Mb & if you see 117.02Mb then pagepool is 6Mb

So this means all new 2.0x Roms are actually set to 12Mb Pagepool and not 16Mb as previously thought.
The best way to definitely be sure what your pagepool is is to run devhealth.exe on your device. This will create the following file on your internal storage mem_1.txt. This file will detail how your physical memory is shared out into pagepool and other areas. 2.00Roms show up in devhealth as having 120.12Mb of total physical memory (including pagepool) and previous roms have 124.12Mb total memory.

Devhealth.exe is available at the following link:
http://forum.xda-developers.com/showthread.php?t=416334

Most of the time there is not much point in editing the pagepool on these new roms as they are already 12Mb and lowering that I feel they do not run as well.

If you would still like to change the pagepool there are two methods. the easiest is to use pagepool changer however it does not work without modifying the rom first with a hex editor as the pagepool appears to be set in two places and one can override the other.


Now how do we change the pagepool on these new roms?

Method 1 Using Pagepool Editor

Pagepool Edit 2.21 will not work on the rom properly unless a hex key is changed in the rom image file or your rom has been pagepool patched by the chef.

1. In a hex editor search for the following key 03 25 A0 E3 03 15 A0 E3 00 20 83 E5
2. If this key exists, replace 20 83 E5 with 00 A0 E1 This disables this key and lets pagepool changer work.
If the key in step 1 does not exist and you are using a cooked rom then search for the following 03 25 A0 E3 03 15 A0 E3 00 00 A0 E1. If this exists then the pagepool changer should work without any hex edits as the chef has already made the required change.
3. Save the image file.
4. The rom will now not use this key to change the pagepool and it can now be set using the key changed by pagepool editor. If you don't run pagepool editor the rom is now set to 6Mb.
5. Any changes made through the pagepool changer will now be carried out correctly and will reflect in program memory and devhealth.exe

Method 2 Using hex edits only

This method will probably not work if the rom has already had the above key changed by the chef. If this is the case use the pagepool changer.

1. Search for the following Hex key in a hex editor 389FE554089FE5. This is slightly different to the previous key.
2. You need to change the two numbers after it to the numbers shown further down. The first numbers are 02 25
3. Search for the string again (it appears twice). Again change the two numbers after it which will currently be 03 25
4. Save the image file then flash

0Mb Pagepool: 00 25
8Mb Pagepool: 02 25
12Mb Pagepool: 0C 26 (No point using this as it makes no difference already 12Mb)
16Mb Pagepool: 10 26

Method 3 Using ervius's Visual kitchen
Use the following kitchen to change the pagepool:
http://forum.xda-developers.com/showthread.php?t=469420
Thanks ervius

P.S Credits to everybody who found the edits for the previous roms. I wouldn't have found these without them.

[Pumpiron579]

This is excellant Thanks:)

[band27]

Yes, great job. Definitely an interesting discovery between the 1.93 vs. 2.00 roms.

So ultimately 12pp and higher is the optimal choice?

Gone are the days of the 0 pp with these newer Roms?

[shaks1979]

Yes, great job. Definitely an interesting discovery between the 1.93 vs. 2.00 roms.

So ultimately 12pp and higher is the optimal choice?

Gone are the days of the 0 pp with these newer Roms?

I know 12pp works well however 0Mb seemed to be absolutely fine whilst I tested for a short while. 8Mb seemed a little slow however I was really testing to ensure everything worked properly not for speed so I'll leave that to you guys to test which performs better. Personally I'm more than happy with the default 12mb. In my own cooked rom thread I have 0Mb,8Mb and 12Mb to test so you can make your own choices.

[band27]

Ok, fair enough...........;)

& thank u again for unavailing this to us...

[christis]

Nice work. Also, your ROM is fantastic. Thanks for both.

[mondilv]

Are you sure, that it works to 2.03?

[shaks1979]

Are you sure, that it works to 2.03?

I've not fully tested however I will test tonight. It looked the same when I looked at it and I may have assumed it's the same! My bad.

[shaks1979]

Are you sure, that it works to 2.03?

Tested both methods with 0Mb Dynamic PP on my 2.03 ROMS and they worked perfect. Devhealth shows a 0mb pp & total program memory is now 119.06 which confirms this has definitely worked.

[mondilv]

Try to ulrd & more reduced container.

[RideTheTube]

i have tried method 1 with pagepoolchanger... i have found all the values and changed them but after recook its still the same...

[shaks1979]

i have tried method 1 with pagepoolchanger... i have found all the values and changed them but after recook its still the same...

No idea what went wrong. It works 100% for me everytime. Not that there is any need to change PP on this rom I would say.

[ctrlaltdel]

Hi Shaks1979,

I am trying to change the pagepool on a cook ROM (CT's 6.4lite) and both method failed.

I try change the HEX using method 1 and pagepool changer cannot patch the nbh file.

I change using method 2, but i can only locate one HEX value and the two number after this is 03 25 instead of 02 25.

is that this cook ROM file have problem?

thanks.

After having done some research in changing the pagepool on the new 2.0x based diamond roms I have made some interesting discoveries.
The new roms have another 4Mb missing e.g.

2.0x ROMs with 12Mb pagepool have 107.02Mb Program Memory, 8Mb Roms have 111.02Mb, 0Mb Roms have 119.02Mb & if you see 113.02Mb then pagepool is 6Mb

In Comparison
1.93 ROMS with 12Mb pagepool have 111.02Mb Program Memory, 8Mb Roms have 115.02Mb, 0Mb Roms have 123.02Mb & if you see 117.02Mb then pagepool is 6Mb

So this means all new 2.0x Roms are actually set to 12Mb Pagepool and not 16Mb as previously thought.
The best way to definitely be sure what your pagepool is is to run devhealth.exe on your device. This will create the following file on your internal storage mem_1.txt. This file will detail how your physical memory is shared out into pagepool and other areas. 2.00Roms show up in devhealth as having 120.12Mb of total physical memory (including pagepool) and previous roms have 124.12Mb total memory.

Devhealth.exe is available at the following link:
http://forum.xda-developers.com/showthread.php?t=416334

Most of the time there is not much point in editing the pagepool on these new roms as they are already 12Mb and lowering that I feel they do not run as well.

If you would still like to change the pagepool there are two methods. the easiest is to use pagepool changer however it does not work without modifying the rom first with a hex editor as the pagepool appears to be set in two places and one can override the other.


Now how do we change the pagepool on these new roms?

Method 1 Using Pagepool Editor

Pagepool Edit 2.21 will not work on the rom properly unless a hex key is changed in the rom image file.

1. In a hex editor search for the following key 03 25 A0 E3 03 15 A0 E3 00 20 83 E5
2. If this key exists, replace 20 83 E5 with 00 A0 E1 This disables this key and lets pagepool changer work.
If the key in step 1 does not exist and you are using a cooked rom then search for the following 03 25 A0 E3 03 15 A0 E3 00 00 A0 E1. If this exists then the pagepool changer should work without any hex edits as the chef has already made the required change.
3. Save the image file.
4. The rom will now not use this key to change the pagepool and it can now be set using the key changed by pagepool editor. If you don't run pagepool editor the rom is now set to 6Mb.
5. Any changes made through the pagepool changer will now be carried out correctly and will reflect in program memory and devhealth.exe

Method 2 Using hex edits only

This method will probably not work if the rom has already had the above key changed by the chef. If this is the case use the pagepool changer.

1. Search for the following Hex key in a hex editor 389FE554089FE5. This is slightly different to the previous key.
2. You need to change the two numbers after it to the numbers shown further down. The first numbers are 02 25
3. Search for the string again (it appears twice). Again change the two numbers after it which will currently be 03 25
4. Save the image file then flash

0Mb Pagepool: 00 25
8Mb Pagepool: 02 25
12Mb Pagepool: 0C 26 (No point using this as it makes no difference already 12Mb)
16Mb Pagepool: 10 26

P.S Credits to everybody who found the edits for the previous roms. I wouldn't have found these without them.

[ervius]

After having done some research in changing the pagepool on the new 2.0x based diamond roms I have made some interesting discoveries.
The new roms have another 4Mb missing e.g.

2.0x ROMs with 12Mb pagepool have 107.02Mb Program Memory, 8Mb Roms have 111.02Mb, 0Mb Roms have 119.02Mb & if you see 113.02Mb then pagepool is 6Mb

In Comparison
1.93 ROMS with 12Mb pagepool have 111.02Mb Program Memory, 8Mb Roms have 115.02Mb, 0Mb Roms have 123.02Mb & if you see 117.02Mb then pagepool is 6Mb

So this means all new 2.0x Roms are actually set to 12Mb Pagepool and not 16Mb as previously thought.
The best way to definitely be sure what your pagepool is is to run devhealth.exe on your device. This will create the following file on your internal storage mem_1.txt. This file will detail how your physical memory is shared out into pagepool and other areas. 2.00Roms show up in devhealth as having 120.12Mb of total physical memory (including pagepool) and previous roms have 124.12Mb total memory.

Devhealth.exe is available at the following link:
http://forum.xda-developers.com/showthread.php?t=416334

Most of the time there is not much point in editing the pagepool on these new roms as they are already 12Mb and lowering that I feel they do not run as well.

If you would still like to change the pagepool there are two methods. the easiest is to use pagepool changer however it does not work without modifying the rom first with a hex editor as the pagepool appears to be set in two places and one can override the other.


Now how do we change the pagepool on these new roms?

Method 1 Using Pagepool Editor

Pagepool Edit 2.21 will not work on the rom properly unless a hex key is changed in the rom image file.

1. In a hex editor search for the following key 03 25 A0 E3 03 15 A0 E3 00 20 83 E5
2. If this key exists, replace 20 83 E5 with 00 A0 E1 This disables this key and lets pagepool changer work.
If the key in step 1 does not exist and you are using a cooked rom then search for the following 03 25 A0 E3 03 15 A0 E3 00 00 A0 E1. If this exists then the pagepool changer should work without any hex edits as the chef has already made the required change.
3. Save the image file.
4. The rom will now not use this key to change the pagepool and it can now be set using the key changed by pagepool editor. If you don't run pagepool editor the rom is now set to 6Mb.
5. Any changes made through the pagepool changer will now be carried out correctly and will reflect in program memory and devhealth.exe

Method 2 Using hex edits only

This method will probably not work if the rom has already had the above key changed by the chef. If this is the case use the pagepool changer.

1. Search for the following Hex key in a hex editor 389FE554089FE5. This is slightly different to the previous key.
2. You need to change the two numbers after it to the numbers shown further down. The first numbers are 02 25
3. Search for the string again (it appears twice). Again change the two numbers after it which will currently be 03 25
4. Save the image file then flash

0Mb Pagepool: 00 25
8Mb Pagepool: 02 25
12Mb Pagepool: 0C 26 (No point using this as it makes no difference already 12Mb)
16Mb Pagepool: 10 26

P.S Credits to everybody who found the edits for the previous roms. I wouldn't have found these without them.

you forgot point 3:
my visualkitchen, that changes pp values on xip\ correctly on 2.x roms.....

[shaks1979]

you forgot point 3:
my visualkitchen, that changes pp values on xip\ correctly on 2.x roms.....

Sorry ervius. Don't believe your kitchen was released when I originally wrote this document. Can you send the link and I will add the info on?

[ervius]

Sorry ervius. Don't believe your kitchen was released when I originally wrote this document. Can you send the link and I will add the info on?

no problem!!! ;)
I only saw that with xipporterex or all visualkitchen all is done automatically ;)
btw the link for visualkitchen is:
http://forum.xda-developers.com/showthread.php?t=469420

bye bye!!!

[shaks1979]

no problem!!! ;)
I only saw that with xipporterex or all visualkitchen all is done automatically ;)
btw the link for visualkitchen is:
http://forum.xda-developers.com/showthread.php?t=469420

bye bye!!!

Info added to first post

[efeene]

Thanks shaks1979
If I understand disable hex key return PP to 6Mb. But if I search hex 38 9F E5 54 08 9F E5 I have the same 02 25 and 03 25 values that as you list they correspond to 8 PP

[kang.t7]

So, Let me get this Straight.

0MB Page Pool means that its Dynamic? So Windows Will Pick Whatever Size is Required? Whether it be 6 or 8 or 12mb etc;?

Wouldn't this be the most effective choice?

[band27]

So, Let me get this Straight.

0MB Page Pool means that its Dynamic? So Windows Will Pick Whatever Size is Required? Whether it be 6 or 8 or 12mb etc;?

Wouldn't this be the most effective choice?

That is my understanding of it yes. What you should also know, from my observations is, with PP set at "0", that this eats more memory than its worth.

Not sure if others have experience this as well so I steer clear of the dynamic setup.

[kang.t7]

That is my understanding of it yes. What you should also know, from my observations is, with PP set at "0", that this eats more memory than its worth.

Not sure if others have experience this as well so I steer clear of the dynamic setup.

If its dynamic Shouldn't windows increase /decrease the PP size at Will?

I wonder if "Free up Ram" utility like Oxios hibernate can reduce the page pool size while freeing up ram if that size is not required.

[imatrix]

If its dynamic Shouldn't windows increase /decrease the PP size at Will?

That what it should be, however Windows does not have good reputation in memory management. I, the same as band27, stay clear of 0mb pp.

[band27]

If its dynamic Shouldn't windows increase /decrease the PP size at Will?

I wonder if "Free up Ram" utility like Oxios hibernate can reduce the page pool size while freeing up ram if that size is not required.

In theory, yes, however I've done enough experiments to realize that it's high maintaince to always have to use Oxios to reduce Ram. It has a natural tendency to stay high. Try and you'll see that it's not the way to go....:p

That what it should be, however Windows does not have good reputation in memory management. I, the same as band27, stay clear of 0mb pp.

Thanks for backing this up imatrix...;)

[losdrivare]

I want to change the pagepool of udK Topaz R7 to 12 mb, but none of the methods seem applicable.

Using method 1: neither string 03 25 A0 E3 03 15 A0 E3 00 20 83 E5 nor string 03 25 A0 E3 03 15 A0 E3 00 00 A0 E1 can be found in the .nbh with my hex editor.

Using method 2: string 38 9F E5 54 08 9F E5 is found only once, not twice as it should according to the guide.

Can anyone shed some light about how to change the pagepool on this ROM?

[shaks1979]

I want to change the pagepool of udK Topaz R7 to 12 mb, but none of the methods seem applicable.

Using method 1: neither string 03 25 A0 E3 03 15 A0 E3 00 20 83 E5 nor string 03 25 A0 E3 03 15 A0 E3 00 00 A0 E1 can be found in the .nbh with my hex editor.

Using method 2: string 38 9F E5 54 08 9F E5 is found only once, not twice as it should according to the guide.

Can anyone shed some light about how to change the pagepool on this ROM?

The rom is already PP patched which is why you cannot find the string in method 1. Method 2 is only found once because the rom is ULDR Removed.

To change the PP all you need to do is run Pagepool Changer against the nbh file and select PP required. No hex editing required at all. Method 2 will never work as method 1 has already been done.

[losdrivare]

The rom is already PP patched which is why you cannot find the string in method 1. Method 2 is only found once because the rom is ULDR Removed.

To change the PP all you need to do is run Pagepool Changer against the nbh file and select PP required. No hex editing required at all. Method 2 will never work as method 1 has already been done.

Thanks for your answer! :) Using method 1, I was under the impression that I should either find the string in point 1 and change it OR find the string in the red text in point 2 to confirm that the pagepool changer would work right away because the ROM had already been patched. I was confused that there was no third alternative where you could find neither of the strings. Thanks for clearing this up! :)

[jent.le]

fantastic about your ROM !！！I'll try it later ！Thanks for your contribution ！

[vrajresh]

I am install max manila rom but program memory very low. so how to increase program memory