Quote:
Originally Posted by fr4nk1yn
I never got 21018 running were I was happy. I didn't change my sig.
I dropped back to 21015, BUT 20771 is good, Real good.
It's as responsive as 21015 for sure.
I did get a xip.bin, but.. OK yeah I have no clue.
So I DL the ROM and use the kitchen to create the ROM folder, Calcu's v1.3 Kitchen.
It would not boot. Probably since it's a AT&T GSM ROM(?).
Here's the files: http://www.mediafire.com/?sharekey=8...62002116cc4280 |
Simplest way to do it is as follows:
1) Extract xip.bin from your donor ROM (whatever has the SYS version you want to use). Use xipport.exe to dump this (creates an OUT directory) then click make packages.
2) Extract xip.bin rom your stock ROM on your device (key - must be your device). Repeate above steps with xipport.exe.
You will now have two sets of OUT directories, each with a FILES and MODULES directory. Inside there will be a bunch of sub-directories. You need the complete contents of two: OEMXIPKernel and MSXIPKernel. The rest you can scrap.
Make a new directory called OUT that contains a FILES and MODULES sub-directory. Copy the OEMXIPKernel directory from each from your STOCK device to this new OUT directory. Copy the MSXIPKernel directory from the FILES and MODULES directory from the DONOR XIP to your new OUT directory.
Start xipport.exe again and click undo, then write maps. Look at map.txt. If you see a bunch of !!!!! - then you get to re-locate modules. Have fun. If you don't see any !!! then you have a bootable XIP, though not necessarily optimized. Click realloc P, then build XIP.bin. Lastly, insert that xip.bin back into your os.nb.payload and cook away.
Note - the above is a highly abridged version of how to do it. There is a much more lengthy tutorial at XDA - but it's 100+ pages.