CDMA Touch Pro XIPs 20764 20771 20954 21015 21018 21028 21032 21109 - Page 20

fr4nk1yn · #**191** (**permalink**) 02-28-2009, 08:56 PM

Quote:

Originally Posted by FormerPalmOS

SQM = Supplier Quality Metrics. Think of it as big brother watching over how your phone performs, collecting data then sending it home periodically... 'nuff said.

Can't Customer Satifaction be turnrd off or does it still call home?

FormerPalmOS · #**192** (**permalink**) 03-01-2009, 01:04 PM

It can be turned off - but if you don't want it, why have it installed in the first place? Takes up space and slows things down (even if only by a tiny amount but those tiny amounts can add up). custsat.dll has to be there (dependency) but no2chem basically stripped it to just expose the minimum functions other programs depend on, but it doesn't actually do anything.

fr4nk1yn · #**193** (**permalink**) 03-02-2009, 11:12 PM

Had a few scary moments after trying flash a 20771 ROM.
I did something wrong with the XIP and had no red letters on the "Touch Pro" boot screen.
Used the 20764 XIP and it boots.
Can somebody port? Or point me to a tutorial that's not totally over my head o:

jucytec · #**194** (**permalink**) 03-02-2009, 11:37 PM

Quote:

Originally Posted by fr4nk1yn

Had a few scary moments after trying flash a 20771 ROM.
I did something wrong with the XIP and had no red letters on the "Touch Pro" boot screen.
Used the 20764 XIP and it boots.
Can somebody port? Or point me to a tutorial that's not totally over my head o:

I don't see a point of you flashing to 20771... you are already running the best by running 21018. Former would agree and all those who ran 21018 would...

As far as XIPs go, if you got the entire SYS pack, chances are you also got the XIP with it... if not, you should be able to google for one... but.. if you are attempting what Former's been doing...

It's definitely beyond me...

FormerPalmOS · #**195** (**permalink**) 03-02-2009, 11:53 PM

Any particular reason you want to try 20771? I'm 100% sold on 21018 right now - not looking back. Would take a really helluva good reason to look at a different SYS version. So, you got a helluva good reason?

fr4nk1yn · #**196** (**permalink**) 03-02-2009, 11:57 PM

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

FormerPalmOS · #**197** (**permalink**) 03-03-2009, 01:03 AM

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.

FormerPalmOS · #**198** (**permalink**) 03-03-2009, 01:05 AM

BTW - been running 21018 + 21018 since the 25th and haven't even reset the device (and it hasn't done it on its own - my boot count remains at three - all done during initial set-up). Still fast. No memory leak (sitting at 71% used with my somewhat heavy HTC bloatware load). No complaints.

DigitalAttic · #**199** (**permalink**) 03-03-2009, 01:45 AM

Quote:

Originally Posted by FormerPalmOS

BTW - been running 21018 + 21018 since the 25th and haven't even reset the device (and it hasn't done it on its own - my boot count remains at three - all done during initial set-up). Still fast. No memory leak (sitting at 71% used with my somewhat heavy HTC bloatware load). No complaints.

Agreed, 21018 is the best build I've used to date, and I've been through a few. I have seen some memory leak in the few days I'm on in, but I can't qualify what causes it, and since I use Memaid too, it really isn't an issue for me. I start with about 54MB-- TF3D loaded-- and wind up at about 46MB after a days use. I have not loaded anything outside HTC apps and some stock VZN apps.

The only move for me from the build I have now would be if it gets optimized somehow or when 6.5 is released. Right now my next project is to finalize customization and see how well it ports over to 6.5 Beta, else, I'm just gonna start enjoying "using" my phone for awhile

CFN - DA

**silence12782** · #**200** (**permalink**) 03-03-2009, 01:52 AM

Quote:

Originally Posted by FormerPalmOS

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.

I found a xipkitchen at ppckictchen. Looks good althoe I havent tried it...