I tried as a test to take a cooked windows.nb file and using the hex editor search for the hex strings A0 03 00 10 8E 05 03 00 00 0A. I found them twice in the file and made the adjustment to the previous two bytes on the two sets (10 16 from 03 15 for a 16mb page pool).
Checking the memory status it seemed to work this way. Also as a check I dumped the rom and reconstructed it with the kitchen. I then opened the nk.exe file and checked. Its value had been changed to the appropriate string.
I also noted that if I use that windows.nb file when building future versions of my rom it retains the 16mb (10 16 values) settings.
Can anyone verify this? It seems one step easier than the original method.
Also if anyone else has already posted this finding, congrats and sorry for the potential repost.
PS. I also tried changing the bites directly in a .nbh file and it seemed to work the same, I havent tried repeating this step to verify though.
Has anyone else done it this way? (Do all of you do it this way and I'm just behind?)
This would mean one can change the pagepool in a cooked rom file without having to extract it first.
Well if i had to muster a guess.
For my test I was using my Rogers 1.83 rom.
I took a look at alex's recent 3.51 rom att rom as a lark.
Though the strings that dutty mentioned could not be found. I searched for some hex values that preceded it. I found to patterns that may work though I may be wrong but i dont think so.
search for the pattern, you will find it twice in the rom the same as the other pattern for the 1.83 rom.
03 E5 A0 03 00 E0 84 05 03 00 00
This co-incides to the other pattern.
I found this btw by searching for this string which is consistently before both patterns.
E1 02 38 83 E1 01 3C 8A E1 80 00
The start of the ram pattern was 3 bytes after that.
On the original roms the bytes to change we defaulted as 03 15. This one seems to be 03 E5.
So perhaps changing to two sets to
10 E6 (the first two bytes) may yield a 16 meg page pool. I will try it later.
Changing the page pool value affects the phones performance as noted in the beginning of this thread.
What page pool sizes to use have been covered in the first posts and tests have been performed on different sizes throughout the thread.
Based on what Dutty has found I assume the second byte enables or disables a manually set page pool.
The first byte is the actual page pool size in Hex.
10 = 16 meg page pool.
12 = 18 meg page pool.
18 = 24 meg page pool (again this is covered by Dutty)
The ATT 3.51 rom has a different hex string to search for as noted in my comments above.
As mentioned you can edit your cooked file directly which saves some steps.
If you want to change your ATT 3.51 rom to a 24 meg page pool for example. Do the following.
You can use a hex editor on the ruu_signed.nbh file or the window.nb (or whatever your os.nb file is) directly to change the page pool size.
1) Open up the RUU_Signed.nbh with hex editor.
2) search for A0 03 00 E0 84 05 03 00 00 and move back 2 bytes.
3) The values should 03 E5 if the rom is still set to dynamic.
4) Change E5 TO E6 if not already.
5) change the first byte before the E5 to the desired page pool size (03 is is intial size) to 16. Its in hex.
6) Search again repeating steps 2 to 5.
7) save changes
I am just not explaining well. I worked out the system that should be universal to both roms. I gave a quick 7 step method for the att 3.51 only rom above to make it easier.
Let me show you how it works on your example.
Attachment 83813 (Click on it to expand picture, not sure why my attachment is so small)
The string inside the black frame box is the one that is found in most roms including the att 3.51 (E1 02 38 83 E1 01 3C 83 E1 80 00 ). and you can see that 3 bytes over are the values 10 E6. This indicates that the rom is already set to manual pagepool (because of the E6) and is set to 16 meg page pool (
because 10 = 16 meg page pool in hex 1F = 31 in hex, 20 = 32 etc)
Change that 10 value to whatever size you wish. remember its hex so 0E = 14 in decimal.
Note that the string in the black box can only be used to find the initial set. When you search for the second set use the string you highlighted and then change the previous 2 bytes. In your example again it is 10 E6 just left of your black highlight. make your first change then search again for the string you have highlighted (A0 03 00 E0 84 05 03 00 00 ) and two bytes previous will be 10 E6 again. Make same change there and save it.
|Thread Tools||Search this Thread|