View Single Post
  #15 (permalink)  
Old 01-20-2009, 06:42 PM
FormerPalmOS's Avatar
FormerPalmOS
Regular 'Geeker
Offline
Threadstarter
Location: Far far away...
 
Join Date: Nov 2008
Posts: 359
Reputation: 1355
FormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on repFormerPalmOS is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: New XIP for 21109 sys with working encryption

Quote:
Originally Posted by Juggalo_X View Post
it is a good idea to remove this from the xip. u know what would have been 789643298576329486523984% easier?

use those dlls in a OEMXIP Package rather then reinventing the wheel in putting them back into the xip. they are taken out to save space. that way if u need it u add it to the OEM XIP package... if you dont then you dont.

oh yah. patch the PP string in the payload, and no cert patch it. if your going to do the xip might as well patch it correctly so users can take full advantage of it.
You've built many more ROMs than me - so some additional explanation here would help. Here's my understanding - correct me where I'm wrong. My two goals for this XIP were to a) re-enable file filter cache and b) re-enable storage card encryption. For some reason (don't know - just going by MS suggestion), mencfilt.dll must load on every FAT file system or it won't work. I confirmed this by trial and (many) errors. That means it has to load in the XIP - can't load after boot. Same with cachefilt - it should be applied to the root filesystem and should therefore also be loaded in the XIP. The XIP modules must be individually located within the XIP address space, with a specific order for one particular module. The addresses for the module code, constants and data must all be allocated so there are no overlaps. Once complete, the whole thing is turned into one image and stored in the XIP section of the NAND. At boot this is copied into RAM and executed. It proceeds to load the actual OS.

So I don't know what an OEMXIP is - unless you are referring to the OEM modules which are device-specific (I extracted these from the verizon Stock ROM XIP dump) and are combined with the new 21109 MS modules which are not device-specific - the sum of the two is the device-specific XIP. But regardless of where the mencfilt.dll and cachefilt.dll are placed (OEM or MS) the module memory allocation process and XIP image building, etc. must still be done.

Now if there is an easier way to do this (can't imagine a much harder way), then I'm all ears!

On the no cert patch and pagepool patch - the pagepool patch as-is would enable the pagepool changer to work (probably) - I didn't try it that way, preferred my way (though at 4am maybe not for any good reason). No idea what the no cert patch is for - I didn't do it and haven't run into anything I can't do as a result. What is the patch, what does it do? (Yes I know I could search the threads but as it stands I don't have a need for this and will therefore not take the time to do so until said need arises).

Thank you.
__________________
ROM: WM6.5 nk.exe (Da_G), sys 23518 (Da_G), VZW OEM pack (scrosler)
Apps: Manila 2.1 (yozgatag), Leo dialer (pyrorob)
Reply With Quote