Quote:
Originally Posted by omahajs
Exactly the reason for my post. Anyone? I've got a long weekend to look into this more and would appreciate a non-technical and helpful response.
Thank you.
Originally Posted by omahajs View Post
Quick question for you experts out there as I'm still learning. As these new sys files come out I don't see an OEMXipkernel to go into the touchpro folder in Calks VK.
I've seen posts where people just say to copy this folder from an older version and rename the folder. This works, but then I usually get different version numbers when I do a system/about - like CE OS 23506/ (Build 28002). Is the OEMXipkernel the CE OS, or the build and does it really matter other than a visual inconsistency? Is this folder generally the same for most 6.5.x builds and how to get the version/build numbers matched up if I just copy from an older build folder?
|
The scenario you describe above would happen only if you used an older MSXIPKernel, not an older OEMXIPKernel.
OEMXIP is independent of the build, it's device specific and the original OEMXIP dumped from a stock ROM can/should be used over and over for each successive build.
MSXIP is build specific and changes from build to build, and is usually included in builds posted by build hacks like me
Sometimes you will find an xip.bin in the build package with no MSXIPKernel. This xip.bin can be dumped and used to create the MSXIPKernel for the build in question using tools like XIPPort and XIDump.
This xip.bin IS NOT the same as the xip.bin you find in the ROM\device folder, so don't mix the two or bad things will happen... hehe.
Also, most "non-booting" ROM flashes are due to bad XIPs, either OEM or MS or both. The XIP is a level above the SPL layer, but is still in some sense like a high-level BIOS, whereas the SPL is closer to what can be viewed as a traditional BIOS. This is why our phones need an SPL unlocker to flash. The stock SPL is analogous to a "password protected" computer BIOS, and no low-level changes can be made to a computer with PWP-BIOS unless you know the password, even though OS updates can be done. For our phones however, OS updating is a low-level function as it requires a flash (well not absolutely, but OEMs don't use the OTA update sub-system yet universally) so hence the SPL must be unlocked.
Hope this helps clear things up for you.