Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,736,660 Members 54,154 Now Online
XDA Developers Android and Mobile Development Forum

[TUT] Sous-Chef's Guide to Aruppenthal's XIP Porting Kitchen 5.3

Tip us?
 
hilaireg
Old
(Last edited by hilaireg; 29th September 2009 at 03:24 AM.)
#1  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default [TUT] Sous-Chef's Guide to Aruppenthal's XIP Porting Kitchen 5.3

Version: 15/06/2009


Intro

Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that will benefit others and to show my appreciation to the folks that make XDA the great community that it is. Hopefully, this guide will help you work your way up the ranks to Chef … let’s begin!

So here you are; in the heat of the kitchen, adding your favourite ROM ingredients ... pinch of this, sprinkle of that. Like all good chefs, you decide to take a taste of your preparation before serving to others – so you try it ... wait! you say, something is not right; you're positive you added the ingredients but it's not right. You carefully review all of the portions; seem right; so you decide to look at the ingredients and you realize … you need to change suppliers.

This guide is intended to help you learn how to port the Execute-In-Place (XIP) region from a new (donor) device for use in your kitchen; it will walk you through the process of extracting the contents of an Official ROM, obtaining the new (donor) device XIP, and porting the new (donor) device XIP into your kitchen.


Obtaining Execute-In-Place (XIP) Files

The Execute-In-Place (XIP) region is an area where an application can execute code directly from ROM rather than loading it from RAM. It is possible to use the xip.bin contents from a newer version of a ROM from a different device or a newer operating system. This is typically done by chefs who are looking for the most recent versions of system files from a specific device or version of an operating system.

The process of porting the Execute-In-Place (XIP) requires that you have a reduced copy of your current os.nb.payload from which the xip.bin will be extracted.

Additionally, the process requires that you obtain the newer xip.bin (extracted from the reduced os.nb.payload) and the corresponding .\SYS folder from the desired device .NBH package. Although it is possible to obtain a pre-extracted xip.bin and corresponding .\SYS folder, it is always preferable to perform the extraction activities yourself when possible – this ensures that you have a complete .\SYS folder, the reduced os.nb.payload file, and the extracted xip.bin to work with.


Outro

The sections are intended to be followed in sequence as the last section should provide you with a final product that can be used in your kitchen – so you may want to read this guide once over before going through the motions … who am I kidding? You’re going to follow along aren’t you?

The guide does not cover the steps required to inject the changes from a new .\SYS folder to your existing kitchen .\SYS folder or the comparison (verification) of the boot.rgu and supporting .RGU files typically found in the new (donor) device.

Now for the disclaimer bit; I take no responsibility and will not be held liable for any problems you encounter with your device before and after following this guide … flashing a ROM is done at your own risk. If you spot mistakes or inaccuracies in the guide however, please let me know so that I may correct them. Now, read on if you still feel it necessary to change suppliers

Oh, one last thing ... special thanks to the following folks for sharing their knowledge with the rest of us ... thank you!

Aruppenthal
Ameet
Bepe
Calkulin
Cmonex
Da_G
Ervius
Olipro

If I missed someone, it's purely accidental – send me a note and I will add your name to the list.
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 11th January 2010 at 06:11 AM.)
#2  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default [TUT] Sous-Chef's Guide to Aruppenthal's XIP Porting Kitchen 5.3 ... continued

Preparing Your Facility

Before you can begin to port an Execute-In-Place (XIP) region, you need to equip your facility with some Kitchen utensils. Your Kitchen is going to require a good Unicode & UTF-8 text editor; I personally use ConTEXT & Notepad. Another handy utensil to have is a hexadecimal file/binary editor; I use XVI32. Some other utensils that you're going to require are: cmonex AutoPatcher and om-by Page Pool Changer/Resizer. You will also need an archive extraction utensil; I use IZArc, WinRAR, and WinZIP. You’ll also need a good Hexadecimal calculator; I use Windows Calculator (Scientific Mode).

It's also a good idea to ensure that your Kitchen remains "pest" free; common pest control services include AVG, McAfee, and Symantec anti-Virus. You may need to temporarily disable your Anti-Virus Rootkit scanner while performing binary editing and porting activities.

To assist you in your apprenticeship, I have included a link to Aruppenthal’s XIP Porting Kitchen that I used to prepare this guide – the kitchen also includes a .DOC and .PDF format of this guide. The procedures were tested against a GSM Raphael device. I can’t confirm that these procedures will work on CDMA device ROM’s. Additionally, some device XIP’s may not be compatible with the Raphael device.


XIP Porting Kitchen, 7 MB (mirror)


For the purpose of this guide, I will assume that you have added the C:\XDA\ folder, sub-folder, and files to your anti-virus exclusion list. You will additionally require the Generic Simple Kitchen from the Sous-Chef's Guide to Da_G's Simple ROM Kitchen tutorial (http://forum.xda-developers.com/showthread.php?t=490787) and the XIP Porting Kitchen used in this guide – extracted to the following folder.

C:\XDA\MY_XIP_KITCHEN




The guide is divided into the following sections:


Extracting the RUU_SIGNED.NBH Contents .............. 3
Reducing the .PAYLOAD File .......................... 4
Extracting the Donor XIP.BIN Contents ............... 5
Extracting the Base XIP.BIN Contents ................ 6
Extracting the Donor MSXIPKernel .................... 7
Validating the XIP_OUT.BIN File ..................... 8
Table 1.1: Good ............................... 9
Table 1.2: Fail ............................... 10
Table 1.3: Overlap ............................ 11
Table 1.4: Gap ................................ 12
Preparing the New OS.NB.PAYLOAD File ................ 13
Reducing the Update Loader (ULDR) ............. 14
No Update Loader (ULDR) Reduction ............. 15
Unlocking and Sizing the Paging Pool ................ 16
Disabling Certificate Checking ...................... 17



I will attempt to provide an overview, the list of tools required, and the process to follow in each section. As you become more comfortable (and familiar) with the activities, you will find that you can consolidate (or skip) certain outlined steps. Incidentally, you'll probably want to keep these web links open in case you need to lookup some of the terms or concepts in the guide.

Acronyms
http://wiki.xda-developers.com/index...ename=Acronyms

Glossary
http://wiki.xda-developers.com/index...ename=Glossary

Development Resources for Windows Mobile
http://forum.xda-developers.com/showthread.php?t=445396

Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 16th June 2009 at 04:11 PM.)
#3  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default Extracting the RUU_SIGNED.NBH Contents

An .NBH is a signed group of modules or packages; they are typically comprised of .NB files. An .NBH can contain any combination of .NB files. An .NB file is a block of code that can be a Radio ROM, Operating System packages (XIP and IMGFS), Startup Splash Screen (or SPL).

Upon completion of the extraction process, we will be working with is the OS.NB file; it contains the ULDR, XIP, and IMGFS (OEM, SYS). To extract the contents of an .NBH file, copy the .NBH file to the .\BaseROM folder of a new (clean, unused) kitchen.

You will need to extract the Generic Simple Kitchen to two different folders; one folder for the .NBH file currently in use in your current (base) kitchen, and one folder for the new (donor) device .NBH file.

C:\XDA\BASE_NBH_KITCHEN

C:\XDA\DONOR_NBH_KITCHEN




Procedure

The following procedure initiates the ROM Extraction (NBH, IMGFS, and XIP) activity via a script that is included in the Generic Simple Kitchen. You will need to repeat this procedure for each .NBH file. The extraction process can take a significant amount of time to complete.
  1. Copy the RUU_SIGNED.NBH file to the .\BaseROM\ folder.

  2. Navigate to the folder.
  3. Launch RaphaelKitchen.cmd.
  4. Select E, press ENTER.
  5. Select A, press ENTER.
  6. At the Done! message, allow the process to resume – do not close command prompt!
  7. At the Now Start Cooking Your ROM! Press Any Key To Continue message, press ENTER.
  8. Select X, press ENTER.


References

Tutorial: Sous-Chef's Guide to Da_G's Simple ROM Kitchen 5.3
http://forum.xda-developers.com/showthread.php?t=490787
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 16th June 2009 at 04:12 PM.)
#4  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default Reducing the .PAYLOAD File

At this point, we need to remove the contents of the IMGFS (OEM, SYS) from the .PAYLOAD file in preparation for our changes to the ULDR and XIP. Removing the IMGFS (OEM, SYS) contents from the .PAYLOAD file will reduce the size of the .PAYLOAD file making it easier to work with.

To reduce the .PAYLOAD file, we essentially need to cook a new version of the .PAYLOAD file with an empty IMGFS partition – one which only contains the .VM and .ROM folder contents. For the purposes of this guide, we will use the Ervius Payload Reducer script to perform this process.

You will need to reduce the os.nb.payload for each extracted .NBH file; once for the .NBH contents currently in use in your (base) kitchen, and once for the new (donor) device .NBH file.


Procedure

The following procedure initiates the .PAYLOAD file reduction activity via a script that is included in the Generic Simple Kitchen. The reduced os.nb.payload file will be required when we update the xip.bin file.
  1. Copy the os.nb.payload file from the kitchen .\Temp\ folder to the kitchen .\Tools\ReducePayload\ folder.

  2. Navigate to the .\Tools\ReducePayload\ folder.
  3. Launch reduce_payload.bat.
  4. At the OS.NB.PAYLOAD Successfully Reduced. Press Any Key To Continue ... message, press ENTER.

References

Tutorial: Sous-Chef's Guide to Da_G's Simple ROM Kitchen 5.3
http://forum.xda-developers.com/showthread.php?t=490787

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)
http://forum.xda-developers.com/showthread.php?t=438676
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 16th June 2009 at 04:31 PM.)
#5  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default Extracting the Donor XIP.BIN Contents

Now that we have two reduced os.nb.payload files; one for the current (base) kitchen and one for the new (donor) device, we must now extract the xip.bin from the reduced os.nb.payload file of the new (donor) device.

We don’t need to extract the xip.bin from the current (base) kitchen os.nb.payload file at this time.


Tools Required

The following tools are required for the xip.bin file extraction activities.

XIPPorterEx



Procedure

The following procedure will extract the contents of the xip.bin from the os.nb.payload file.
  1. Copy the os.nb.payload file from the C:\XDA\DONOR_NBH_Kitchen\Tools\ReducePayload\ folder to the C:\XDA\DONOR_NBH_Kitchen\Tools\XIPPorterEx\MyTools \os_nb.payload\ folder.

  2. Navigate to the C:\XDA\DONOR_NBH_Kitchen\Tools\XIPPorterEx\ folder.
  3. Launch XIPPORTEREX.EXE.
  4. Click the (Extract From .Payload) button.
  5. At the XIP.BIN Successful Extraction From OS.NB.PAYLOAD message, click OK.
  6. At the XIP.BIN Successful Written Into: "\xip.bin_old" Folder message, click OK.
  7. Exit XIPPORTEREX.EXE.

  8. Copy the extracted xip.bin file from the C:\XDA\DONOR_NBH_Kitchen\Tools\XIPPorterEx\MyTools \xip.bin_old\ folder to the C:\XDA\My_XIP_kitchen\MyTools\xip.bin_new\ folder.


References

Kernel Overview
http://msdn.microsoft.com/en-us/library/aa909237.aspx
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 16th June 2009 at 04:30 PM.)
#6  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default Extracting the Base XIP.BIN Contents

At this point, we have extracted the xip.bin from the new (donor) device os.nb.payload file and copied it to the XIP Porting Kitchen.
We must now extract the xip.bin from the reduced os.nb.payload for the current (base) kitchen.


Tools Required

The following tools are required for the xip.bin file extraction activities.

XIPPorterEx



Procedure

The following procedure will extract the contents of the xip.bin from the current (base) kitchen os.nb.payload file.
  1. Copy the os.nb.payload file from the C:\XDA\BASE_NBH_Kitchen\Tools\ReducePayload\ folder to the C:\XDA\BASE_NBH_Kitchen\Tools\XIPPorterEx\MyTools\ os_nb.payload\ folder.

  2. Navigate to the C:\XDA\BASE_NBH_Kitchen\Tools\XIPPorterEx\ folder.
  3. Launch XIPPORTEREX.EXE.
  4. Click the (Extract From .Payload) button.
  5. At the XIP.BIN Successful Extraction From OS.NB.PAYLOAD message, click OK.
  6. At the XIP.BIN Successful Written Into: "\xip.bin_old" Folder message, click OK.
  7. Exit XIPPORTEREX.EXE.

  8. Copy the extracted xip.bin file from the C:\XDA\DONOR_NBH_Kitchen\Tools\XIPPorterEx\MyTools \xip.bin_old\ folder to the C:\XDA\My_XIP_kitchen\MyTools\xip.bin_new\ folder.


References

Kernel Overview
http://msdn.microsoft.com/en-us/library/aa909237.aspx
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 16th June 2009 at 04:38 PM.)
#7  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default Extracting the Donor MSXIPKernel

The Execute-In-Place (XIP) region is comprised of two significant regions – the MSXIPKernel, and the OEMXIPKernel. The OEMXIPKernel typically contains system drivers that are specific to your device. On very rare occasions, these drivers can be changed for newer ones.

The MSXIPKernel however, usually contains drivers that are specific to the version of Windows Mobile that you are using – in our case, Windows Mobile 6.1. There are many different methods for porting the MSXIPKernel drivers; each method may yield different build numbers. For example, some chefs use the 723*.DSM for the build number, others use the COREDLL.DLL module to obtain the latest build numbers.

For the purpose of this guide however, we will leave the OEMXIPKernel drivers as-is and use a simpler method of porting the MSXIPKernel drivers from a new (donor) device for use in your kitchen – and not concern ourselves with the build number.

Once the MSXIPKernel is extracted from the new (donor) device xip.bin, the OEMXIPKernel will be extracted from the current (base) kitchen. Both contents will be merged into a new xip.bin file. Additionally, the certificate store verification will have been disabled.


Tools Required

The following tools are required for the new (donor) device MSXIPKernel extraction activities.

XIPPorterEx



Procedure

The following procedure will extract the contents of the MSXIPKernel from the xip.bin of the new (donor) device, the OEMXIPKernel from the current (base) kitchen, and merge them into a new xip_out.bin file.
  1. Navigate to the C:\XDA\My_XIP_Kitchen\ folder.
  2. Launch XIPPORTEREX.EXE.
  3. Clear the following check boxes:

    Execute PP Patcher
    Delete CACHEFILT.DLL
    Delete MENCFILT.DLL
    Delete ENCFILT.DLL
    Change PP To MB
    Don't Copy Xip Dsm
    DEBUG Save Temp .BIN Files


  4. Select the following check boxes:

    Execute Cert Patcher
    Port Only MSXipkernel
    Create OEM Package From Unused Xip Modules/Files


  5. Click the PORT IT! button.
  6. At the Cert Patcher: Successfully Nocert Patched! message, click OK.
  7. At the ALL DONE! Now Write New XIP.BIN Into Payload message, click OK.
  8. Exit XIPPORTEREX.EXE.


References

Kernel Overview
http://msdn.microsoft.com/en-us/library/aa909237.aspx
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 16th June 2009 at 04:44 PM.)
#8  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default Validating the XIP_OUT.BIN File

At this stage, we have a new xip.bin – currently named xip_out.bin. To ensure that the porting process occurred correctly, we will perform a quick validation of the xip_out.bin file.

If all is well, we will proceed to inject this new xip_out.bin file into our current (base) kitchen os.nb.payload file. In cases where the validation reveals problems, you will need to perform advanced XIP porting procedures – which are beyond the scope of this guide.


Tools Required

The following tools are required for the xip_out.bin validation activities.

XIPPort
Text Editor



Procedure

The following procedure will extract the contents of the newly formed xip_out.bin for validation purposes.
  1. Copy the xip_out.bin file from the C:\XDA\My_XIP_kitchen\MyTools\XIP_new_ported\ folder to the C:\XDA\My_XIP_kitchen\MyTools\ folder.

  2. Rename C:\XDA\My_XIP_kitchen\MyTools\xip_out.bin to C:\XDA\My_XIP_kitchen\MyTools\xip.bin.

  3. Navigate to the C:\XDA\My_XIP_Kitchen\MyTools\ folder.
  4. Launch XIPPORT.EXE.
  5. Click the Dump XIP.BIN button.
  6. Click the Write Maps button.
  7. Exit XIPPORT.EXE.
  8. Launch a text editor.
  9. Select File, Open.
  10. Navigate to the C:\XDA\My_XIP_Kitchen\MyTools\OUT\ folder.
  11. Select the MAP.TXT file.
  12. Compare the beginning (top) portion of the file to against the following tables.


References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)
http://forum.xda-developers.com/showthread.php?t=438676
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 16th June 2009 at 04:54 PM.)
#9  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default Table 1.1: Validating the XIP_OUT.BIN File

The example below is of a favourable output, no overlaps or gaps.

Code:
00000000 - 01f801fc L01f801fc NUL

01f801fc - 01f801fc L00000000 Start: first DLL address
01f801fc - 01fc8000 L00047e04 NUL
01fc8000 - 01fca000 L00002000 initialized data of region_1 wce_rex.DLL
01fca000 - 01fcb000 L00001000 initialized data of region_1 smem.dll
01fcb000 - 01fcc000 L00001000 initialized data of region_1 MMMAP.dll
01fcc000 - 01fcd000 L00001000 initialized data of region_1 GxDMA.dll
01fcd000 - 01fd4000 L00007000 initialized data of region_1 FLASHDRV.DLL
01fd4000 - 01fd5000 L00001000 initialized data of region_3 FLASHDRV.DLL
01fd5000 - 01fed000 L00018000 initialized data of region_2 DDI.dll
01fed000 - 01fee000 L00001000 initialized data of region_1 ceddk.dll
01fee000 - 01fef000 L00001000 initialized data of region_1 cecompr.dll
01fef000 - 01ff0000 L00001000 initialized data of region_1 regenum.dll
01ff0000 - 01ff1000 L00001000 initialized data of region_1 pm.dll
01ff1000 - 01ff2000 L00001000 initialized data of region_1 mspart.dll
01ff2000 - 01ff3000 L00001000 initialized data of region_1 mencfilt.dll
01ff3000 - 01ff4000 L00001000 initialized data of region_1 imgfs.dll
01ff4000 - 01ff5000 L00001000 initialized data of region_1 fsreplxfilt.dll
01ff5000 - 01ff6000 L00001000 initialized data of region_1 fsdmgr.dll
01ff6000 - 01ff7000 L00001000 initialized data of region_1 fatutil.dll
01ff7000 - 01ff8000 L00001000 initialized data of region_1 fatfsd.dll
01ff8000 - 01ff9000 L00001000 initialized data of region_1 diskcache.dll
01ff9000 - 01ffa000 L00001000 initialized data of region_1 devmgr.dll
01ffa000 - 01ffc000 L00002000 initialized data of region_1 crypt32.dll
01ffc000 - 01ffd000 L00001000 initialized data of region_1 coredll.dll
01ffd000 - 01ffe000 L00001000 initialized data of region_1 certmod.dll
01ffe000 - 01fff000 L00001000 initialized data of region_1 cachefilt.dll
01fff000 - 02000000 L00001000 initialized data of region_1 busenum.dll
02000000 - 02000000 L00000000 End: last DLL address

...
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375
 
hilaireg
Old
(Last edited by hilaireg; 18th June 2009 at 01:32 PM.)
#10  
hilaireg's Avatar
Moderator Emeritus - OP
Thanks Meter 222
Posts: 2,945
Join Date: Jan 2009
Default Table 1.2: Validating the XIP_OUT.BIN File

The example below indicates possible problems with the imageinfo.bin or imageinfo.txt files found in the C:\XDA\My_XIP_Kitchen\MyTools\SYS\.VM\ and/or C:\XDA\My_XIP_Kitchen\MyTools\SYS\.ROM\ folders of the XIP Porting Kitchen.

Code:
00000000 - 01f801fc L01f801fc NUL

01f801fc - 01f801fc L00000000 Start: first DLL address
01f801fc - 01fc8000 L00047e04 NUL
02000000 - 02000000 L00000000 End: last DLL address

...

The following procedure may resolve the issue.
  1. Remove the following files

    C:\XDA\My_XIP_Kitchen\MyTools\xip.bin
    C:\XDA\My_XIP_Kitchen\MyTools\XIP_new_ported\xip_o ut.bin


  2. Remove the contents in the following folders – do not remove the folder:

    C:\XDA\My_XIP_Kitchen\MyTools\OEMXIP_Package\*.*
    C:\XDA\My_XIP_Kitchen\MyTools\Dump\*.*
    C:\XDA\My_XIP_Kitchen\MyTools\OUT\*.*
    C:\XDA\My_XIP_Kitchen\MyTools\SYS\Dump\*.*


  3. Copy the contents of C:\XDA\My_XIP_Kitchen\Templates\SYS\ folder (sub-folder and files) to the C:\XDA\My_XIP_Kitchen\MyTools\ folder.
  4. Repeat the donor MSXIPKernel extraction and validation procedures.


If the problem presists, you will need to perform advanced XIP porting procedures – which are beyond the scope of this guide.


References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)
http://forum.xda-developers.com/showthread.php?t=438676
Device 1 & 2: HTC Rhodium (aka TouchPRO2/Tilt2)
Device 3 & 4: Apple N89 (aka iPhone 4)



Donations | Forum Rules | Admins/Mods | WIKI | Chef Central | KB555375

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Get Your Cargo to its Destination in 4×4 Military Operations Reborn

Racing games have evolved quite a bit since the days of Pole … more

Automate Your Device with Sfen

Changing the profile of yourdevice manually is now long forgotten. Since the advent of Android automation … more

Galaxy Photo Screen Lock Displays a Photo Slideshow on Your Lock Screen

Being the most often looked at part of our devices UI, the lock … more