Quote:
Originally Posted by no2chem
If you're interested in messing with the XIP section, check in and around XDA-Developers - if you're cooking your own roms, you've probably done this much already. You should know how to hexedit - and probably know some assembly. x86/CISC type assembly should be enough to get you by, but arm assembler knoweldge would be helpful. (note: ARM is 4-byte word aligned, 32 bit! - LITTLE ENDIAN!)
some background - if the DLL is XIP, CE guarantees it will run at a certain load address, so theres no point in putting the base relocation table in the dll when the image is built. When you extract the XIP sections, the files just contain the actual code - the DLL expects to be run from a certain location. You need to recreate this table and such so the DLL gets loaded at the right addresses (or loads stuff from the right addresses!)
Theres a document that describes this somewhere - i think i can find it for you if you're still interested. Oh yeah, IDA pro is a disassembler.
|
ive gathered most of this on my own but its nice to have someone confirm. i pretty much meet all the requirements except assembler knowledge. i noticed in an older thread where verizonguy mentioned he had taught himself to update the module locations via hex, and it appears he has successfully ported aku 0.7 to the apache - which its my understanding is not as close a match to the kaiser as our titans.
im still interested and im looking for ida pro. if anyone else is working on this, it would be nice to have a few people together on this project. i've seen others "run aku 0.7" on the titan, but it was in 0.2.3 xip, which really doesnt interest me. im far more interested in core os modification than in throwing OEMs at a rom. im pretty well done with my clean rom, and im focusing all my time on the xip now. any reading material you can link me would be helpful, but ive been scouring xda til my eyes hurt lately.
thanks again for the insight